{
	"id": "a7584754-b5b2-4ee2-a3fc-c220a669dd5c",
	"created_at": "2026-04-06T02:10:40.460735Z",
	"updated_at": "2026-04-10T03:20:22.260478Z",
	"deleted_at": null,
	"sha1_hash": "46f19d067413dd82a2c8cacb93a54673f70ccfd6",
	"title": "Cisco IOS Configuration Fundamentals Command Reference - C commands [Support]",
	"llm_title": "",
	"authors": "",
	"file_creation_date": "0001-01-01T00:00:00Z",
	"file_modification_date": "0001-01-01T00:00:00Z",
	"file_size": 429669,
	"plain_text": "Cisco IOS Configuration Fundamentals Command Reference - C\r\ncommands [Support]\r\nPublished: 2025-12-16 · Archived: 2026-04-06 02:05:12 UTC\r\nC commands\r\nC commands\r\ncd\r\nTo change the default directory or file system, use the cd command in user EXEC or privileged EXEC mode.\r\ncd [filesystem:] [directory]\r\nSyntax Description\r\nfilesystem : (Optional) The URL or alias of the directory or file systems followed by a colon.\r\ndirectory (Optional) Name of the directory.\r\nCommand Default\r\nThe initial default file system is flash: . For platforms that do not have a physical device named flash: , the\r\nkeyword flash: is aliased to the default Flash device.\r\nFor the Supervisor Engine, the initial default file system is disk0 :\r\nIf you do not specify a directory on a file system, the default is the root directory on that file system.\r\nCommand Modes\r\nUser EXEC\r\nPrivileged EXEC\r\nCommand History\r\nRelease Modification\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 1 of 101\n\nRelease Modification\r\n11.0 This command was introduced.\r\n12.2(14)SX\r\nThis command was integrated into Cisco IOS Release 12.2(14)SX, and support was\r\nintroduced on the Supervisor Engine 720.\r\n12.2(17d)SXB Support was added for the Supervisor Engine 2.\r\n12.2(33)SRA This command was integrated into Cisco IOS Release 12.2(33)SRA.\r\nUsage Guidelines\r\nThe valid values for filesystem : are as follows:\r\nFor systems that are configured with a Supervisor Engine 2, valid values are bootflash: , const_nvram: ,\r\ndisk0: , flash: , nvram: , slot0: , sup-slot0: , and sup-bootflash:\r\nFor systems that are configured with a Supervisor Engine 720, valid values are disk0: and disk1:\r\nFor all EXEC commands that have an optional filesystem argument, the system uses the file system specified by\r\nthe cd command when you omit the optional filesystem argument. For example, the dir command, which displays\r\na list of files on a file system, contains an optional filesystem argument. When you omit this argument, the system\r\nlists the files on the file system specified by the cd command.\r\nIf you do not specify a directory on a file system, the default is the root directory on that file system.\r\nExamples\r\nIn the following example, the cd command is used to set the default file system to the Flash memory card inserted\r\nin slot 0:\r\nRouter# pwd\r\n \r\nbootflash:/\r\nRouter# cd slot0:\r\n \r\nRouter#\r\npwd\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 2 of 101\n\nslot0:/\r\nExamples\r\nThis example sets the default file system to the Flash PC card that is inserted in disk 0:\r\nRouter# cd disk0:\r\nRouter#\r\npwd\r\ndisk0:/\r\nRelated Commands\r\nCommand Description\r\ncopy Copies any file from a source to a destination.\r\ndelete Deletes a file on a Flash memory device.\r\ndir Displays a list of files on a file system.\r\nmkdir disk0: Creates a new directory in a Flash file system.\r\npwd Displays the current setting of the cd command.\r\nshow file systems Lists available file systems and their alias prefix names.\r\nundelete Recovers a file marked “deleted” on a Class A or Class B Flash file system.\r\nclear archive log config\r\nTo purge the configuration logging database entries, use the clear archive log config command in privileged\r\nEXEC mode.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 3 of 101\n\nclear archive log config [force | persistent]\r\nSyntax Description\r\nforce (Optional) Eliminates the confirm step before the contents of the archive log are cleared.\r\npersistent (Optional) Purges the configuration logging persistent-command database entries.\r\nCommand Default\r\nIf this command is not used, the database entries accumulate in the archive log.\r\nCommand Modes\r\nPrivileged EXEC (#)\r\nCommand History\r\nRelease Modification\r\n12.2(33)SRA This command was introduced.\r\n12.4(11)T This command was integrated into Cisco IOS Release 12.4(11)T.\r\n12.2(33)SXH This command was integrated into Cisco IOS Release 12.2(33)SXH.\r\n12.2(33)SB This command was integrated into Cisco IOS Release 12.2(33)SB.\r\nUsage Guidelines\r\nWhen the clear archive log config command is entered, only the entries in the configuration logging database file\r\nare deleted. The file itself is not deleted; it will be used in the future to log new entries as they occur.\r\nExamples\r\nThe following example clears the database entries that have been saved to the config log without asking you to\r\nconfirm the action before the entries are cleared:\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 4 of 101\n\nRouter# clear archive log config force\r\nRelated Commands\r\nCommand Description\r\nshow archive log config all persistent Displays the persisted commands in configlet format.\r\nclear catalyst6000 traffic-meter\r\nTo clear the traffic meter counters, use the clear catalyst6000 traffic-meter command in privileged EXEC mode.\r\nclear catalyst6000 traffic-meter\r\nSyntax Description\r\nThis command has no arguments or keywords.\r\nCommand Default\r\nThis command has no default settings.\r\nCommand Modes\r\nPrivileged EXEC\r\nCommand History\r\nRelease Modification\r\n12.2(17a)SX Support for this command was introduced on the Supervisor Engine 720.\r\n12.2(17d)SXB\r\nSupport for this command on the Supervisor Engine 2 was extended to Release\r\n12.2(17d)SXB.\r\n12.2(33)SRA This command was integrated into Cisco IOS Release 12.2(33)SRA.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 5 of 101\n\nExamples\r\nThis example shows how to clear the traffic meter counters:\r\nRouter# clear catalyst6000 traffic-meter\r\nRouter#\r\nclear configuration lock\r\nTo clear the lock on the running configuration file, use the clear configuration lock command in privileged EXEC\r\nmode.\r\nclear configuration lock\r\nSyntax Description\r\nThis command has no arguments or keywords.\r\nCommand Modes\r\nPrivileged EXEC\r\nCommand History\r\nRelease Modification\r\n12.2(25)S This command was introduced.\r\n12.3(14)T\r\nThis command was enhanced to allow the exclusive configuration lock to be cleared during\r\nerratic or abnormal behavior.\r\n12.0(31)S This command was integrated into Cisco IOS Release 12.0(31)S.\r\n12.2(28)SB This command was integrated into Cisco IOS Release 12.2(28)SB.\r\n12.2(33)SRA This command was integrated into Cisco IOS Release 12.2(33)SRA.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 6 of 101\n\nRelease Modification\r\n12.2(33)SXH This command was integrated into Cisco IOS Release 12.2(31)SXH.\r\nExamples\r\nThe following is sample output from the clear configuration lock command when the running configuration file is\r\nnot locked by the configure replace command:\r\nRouter# clear configuration lock\r\n \r\nParser Config not locked.\r\nThe following is sample output from the clear configuration lock command when the running configuration file is\r\nlocked by the configure replace command:\r\nRouter# clear configuration lock\r\n \r\nProcess \u003c3\u003e is holding the EXCLUSIVE lock !\r\nDo you want to clear the lock?[confirm] y\r\nThe following example shows how to use the clear configuration lock command to display the owner or process\r\nID of the lock and prompt the user for confirmation:\r\nRouter# clear configuration lock\r\nProcess \u003c46\u003e is holding the EXCLUSIVE lock.\r\nDo you want to clear the lock?[confirm] y\r\nAfter the lock is cleared, a message will be sent to the terminal if the owner of the lock is a TTY user:\r\nRouter(config)# The configuration lock was cleared by user \u003csteve\u003e from terminal \u003c5\u003e\r\nRelated Commands\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 7 of 101\n\nCommand Description\r\nconfiguration mode\r\nexclusive\r\nEnables single-user (exclusive) access functionality for the Cisco IOS CLI.\r\ndebug configuration\r\nlock\r\nEnables debugging of the Cisco IOS configuration lock.\r\nshow configuration lock\r\nDisplays information about the lock status of the running configuration file during\r\na configuration replace operation.\r\nclear diagnostic event-log\r\nTo clear the diagnostic event logs for a specific module or event type, use the clear diagnostic event-log command\r\nin privileged EXEC mode.\r\nclear diagnostic event-log {event-type {error | info | warning} | module {num | slot subslot | all}}\r\nSyntax Description\r\nevent-type error Specifies clearing error events.\r\nevent-type info Specifies clearing informative events.\r\nevent-type warning Specifies clearing warning events.\r\nmodule num | slot subslot Specifies clearing events for a specific module.\r\nmodule all Specifies clearing all linecards.\r\nCommand Default\r\nThis command has no default settings.\r\nCommand Modes\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 8 of 101\n\nPrivileged EXEC (#)\r\nCommand History\r\nRelease Modification\r\n12.2(33)SXH This command was introduced on the Supervisor Engine 720.\r\nUsage Guidelines\r\nThe clear diagnostic event-log command clears all the events for all the modules.\r\nThe clear diagnostic event-log module num command clears events only for a specific module.\r\nThe clear diagnostic event-log event-type command clears only specific event types such as error, informative, or\r\nwarning events.\r\nExamples\r\nThis example shows how to clear error event logs:\r\nRouter# clear diagnostic event-log event-type error\r\nThis example shows how to clear event logs on module 3:\r\nRouter# clear diagnostic event-log module 3\r\n \r\nThis example shows how to clear error event logs on all the modules:\r\nRouter# clear diagnostic event-log module all\r\nRelated Commands\r\nCommand Description\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 9 of 101\n\nCommand Description\r\nshow diagnostic events Displays the diagnostic event log\r\nclear ip http client cache\r\nTo remove information from the HTTP client cache, use the clear ip http client cache command in privileged\r\nEXEC mode.\r\nclear ip http client cache {all | session session-name | url complete-url}\r\nSyntax Description\r\ncache all Removes all HTTP client cache entries.\r\ncache session\r\nsession-name\r\nRemoves HTTP client cache entries of the HTTP client application session specified by\r\nthe session-name argument.\r\ncache url\r\ncomplete-url\r\nRemoves the HTTP client cache entry whose location is specified by the complete-url\r\nargument, a Cisco IOS File System (IFS) Uniform Resource Locator (URL), and that\r\nconsists of HTML files used by an HTTP server.\r\nCommand Default\r\nNone\r\nCommand Modes\r\nPrivileged EXEC\r\nCommand History\r\nRelease Modification\r\n12.2(31)SB2 This command was introduced.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 10 of 101\n\nUsage Guidelines\r\nUse this command to clear entries from the HTTP client cache pool: all the entries, all the entries owned by a\r\nspecific session, or only the entry associated with a specific request from an HTTP server.\r\nExamples\r\nThe following example clears all entries in the HTTP client cache:\r\nRouter# clear ip http client cache all\r\nThe following example removes HTTP client cache entries that belong to the HTTP Client File System (CFS)\r\napplication:\r\nRouter# clear ip http client cache session HTTP CFS\r\nThe following example removes HTTP client cache entries at the location http://myrouter.cisco.com/flash:/:\r\nRouter# clear ip http client cache url http://myrouter.cisco.com/flash:/\r\nRelated Commands\r\nCommand Description\r\nip http path Specifies the base path used to locate files for use by the HTTP server.\r\nshow ip http client Displays a report about the HTTP client.\r\nclear logging\r\nTo clear messages from the logging buffer, use the clear logging command in privileged EXEC mode.\r\nclear logging [persistent [url filesystem:/directory]]\r\nSyntax Description\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 11 of 101\n\npersistent (Optional) Deletes persistent logging files.\r\nurl (Optional) Specifies the URL for storing logging messages.\r\nfilesystem: The file system followed by a colon.\r\n/directory The directory on the filesystem. The slash is required.\r\nCommand Modes\r\nPrivileged EXEC (#)\r\nCommand History\r\nRelease Modification\r\n11.2 This command was introduced.\r\n12.2(33)SRA This command was integrated into Cisco IOS Release 12.2(33)SRA.\r\nCisco IOS XE\r\nRelease 2.4\r\nThis command was modified. The persistent and url keywords, and the\r\nfilesystem:/directory arguments were added.\r\nUsage Guidelines\r\nThe clear logging persistent command is used to remove stored audit records. This action can be performed by the\r\naudit administrator only. The clear logging persistent command clears only log files stored in the directory but\r\ndoes not remove the directory itself. If no log URL is not specified for logging, this command clears files from the\r\nlocation as specified in the logging persistent command.\r\nExamples\r\nIn the following example, the logging buffer is cleared:\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 12 of 101\n\nRouter# clear logging\r\nClear logging buffer [confirm]\r\nThe following example shows how to clear persistent logging files:\r\nRouter# clear logging persistent\r\nDelete persistent logging files from bootflash:/audit_log ? [confirm]\r\nRouter# dir bootflash:/audit_log\r\nDirectory of bootflash:/audit_log/\r\nNo files in directory\r\nThe following example shows how to clear persistent logging files from a specific directory:\r\nRouter# clear logging persistent url harddisk:/log-persistant\r\n Delete persistent logging files from harddisk:/log-persistent ? [confirm]\r\nRouter# dir harddisk:/log-persistant\r\nDirectory of harddisk:////log-persistent/\r\nNo files in directory\r\nRelated Commands\r\nCommand Description\r\nlogging buffered Logs messages to an internal buffer.\r\nlogging persistent Enables the storage of logging messages on the router’s ATA disk.\r\nshow logging Displays the state of logging (syslog).\r\nclear logging system\r\nTo clear event records stored in the System Event Archive (SEA) log file sea_log.dat, use the clear logging system\r\ncommand in user EXEC mode.\r\nclear logging system [disk name]\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 13 of 101\n\nSyntax Description\r\ndisk name (Optional) Stores the system event log in the specified disk.\r\nCommand Default\r\nThis command has no default settings.\r\nCommand Modes\r\nUser EXEC (\u003e)\r\nCommand History\r\nRelease Modification\r\n12.2(33)SXH This command was introduced.\r\n12.2(33)SCC\r\nThis command was introduced for the Cisco uBR10012 router in the Cisco IOS Software\r\nRelease 12.2(33)SCC.\r\nUsage Guidelines\r\nSEA is supported on switches that have a Supervisor Engine 32 or Supervisor Engine 720 with a compact flash\r\nadapter and a Compact Flash card (WS-CF-UPG= for Supervisor Engine 720).\r\nCisco Universal Broadband Router 10012\r\nThe SEA feature is used to address debug trace and system console constraints. SEA is a logging feature that\r\nallows the modules in the system to report major and critical events to the route processor (RP). The events\r\noccurring on the line card or jacket card are also sent to the RP using Inter-Process Communication (IPC)\r\ncapability. Use the clear logging system command to clear the event records stored in the SEA log file.\r\nNote\r\nTo store the system event logs, the SEA requires either the PCMCIA ATA disk or Compact Flash Disk\r\nin compact flash adapter for PRE2.\r\nExamples\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 14 of 101\n\nThis example shows how to clear the SEA:\r\nRouter# clear logging system\r\nClear logging system operation will take a while.\r\nDo you want to continue? [no]: yes\r\nRouter#\r\nRelated Commands\r\ncopy logging system Copies the archived system events to another location.\r\nlogging system Enables or disables the SEA logging system.\r\nshow logging system Displays the SEA logging system disk.\r\nclear logging xml\r\nTo clear the contents of the XML system message logging (syslog) buffer, use the clear logging xml command in\r\nUser EXEC or Priviledged EXEC mode..\r\nclear logging xml\r\nSyntax Description\r\nThis command has no arguments or keywords.\r\nCommand Default\r\nNo default behavior or values.\r\nCommand Modes\r\nUser EXEC Privileged EXEC\r\nCommand History\r\nRelease Modification\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 15 of 101\n\nRelease Modification\r\n12.2(15)T This command was introduced.\r\n12.2(28)SB This command was integrated into Cisco IOS Release 12.2(28)SB.\r\n12.2(33)SRE This command was integrated into Cisco IOS Release 12.2(33)SRE .\r\nUsage Guidelines\r\nThis command clears the contents of the XML-formatted logging buffer, but does not clear the contents of the\r\nstandard logging buffer. The system will prompt you to confirm the action before clearing the buffer.\r\nExamples\r\nIn the following example, the XML-specific buffer is cleared:\r\nRouter# clear logging xml\r\nClear XML logging buffer [confirm]?y\r\nRelated Commands\r\nCommand Description\r\nlogging buffered\r\nxml\r\nEnables system message logging (syslog) to the XML-specific buffer in XML format.\r\nshow logging xml\r\nDisplays the state of XML-formatted system message logging, followed by the contents\r\nof the XML-specific buffer.\r\nclear memory low-water-mark\r\nTo clear the low-water-mark memory, use the clear memory low-water-mark command in privileged EXEC mode.\r\nclear memory low-water-mark\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 16 of 101\n\nSyntax Description\r\nThis command has no arguments or keywords.\r\nCommand Modes\r\nPrivileged EXEC (#)\r\nCommand History\r\nRelease Modification\r\n15.0(1)M\r\nThis command was introduced into a release earlier than Cisco IOS Release\r\n15.0(1)M.\r\n12.2(33)SRB\r\nThis command was integrated into a release earlier than Cisco IOS Release\r\n12.2(33)SRB.\r\n12.2(33)SXI\r\nThis command was integrated into a release earlier than Cisco IOS Release\r\n12.2(33)SXI.\r\nCisco IOS XE Release\r\n2.1\r\nThis command was implemented on the Cisco ASR 1000 Series Aggregation\r\nServices Routers.\r\nUsage Guidelines\r\nThis command clears all processor threshold values and the input/output memory threshold values, if any.\r\nExamples\r\nThe following example shows how to clear the low-water-mark memory:\r\nRouter# clear memory low-water-mark\r\nRelated Commands\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 17 of 101\n\nCommand Description\r\nmemory free low-watermarkConfigures a router to issue system logging message notifications when available\r\nmemory falls below a specified threshold.\r\nclear mls statistics\r\nTo reset the Multilayer Switching (MLS) statistics counters, use the clear mls statistics command in privileged\r\nEXEC mode.\r\nclear mls statistics [module num]\r\nSyntax Description\r\nmodule num (Optional) Specifies the module number.\r\nCommand Default\r\nThis command has no default settings.\r\nCommand Modes\r\nPrivileged EXEC\r\nCommand History\r\nRelease Modification\r\n12.(17d)SXB1 This command was introduced on the Supervisor Engine 720 and the Supervisor Engine 2.\r\n12.2(17d)SXB5 The module num keyword and argumen t pair were added.\r\n12.2(33)SRA This command was integrated into Cisco IOS Release 12.2(33)SRA.\r\nUsage Guidelines\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 18 of 101\n\nThis command replaces the clear mls stats command, which was introduced on the Supervisor Engine 720 in\r\nCisco IOS Release 12.2(17a)SX, and on the Supervisor Engine 2 in Cisco IOS Release 12.2(17d)SXB.\r\nExamples\r\nThis example shows how to reset the MLS statistics counters for all modules:\r\nRouter#\r\nclear mls statistics\r\nRouter#\r\nThis example shows how to reset the MLS statistics counters for a specific module:\r\nRouter#\r\nclear mls statistics module 5\r\nRouter#\r\nRelated Commands\r\nCommand Description\r\nshow mls statistics Displays the MLS statistics for the IP, IPX, multicast, Layer 2 protocol, and QoS.\r\nclear parser cache\r\nTo clear the parse cache entries and hit/miss statistics stored for the Parser Cache feature, use the clear parser\r\ncache command in privileged EXEC mode.\r\nclear parser cache\r\nSyntax Description\r\nThis command has no arguments or keywords.\r\nCommand Default\r\nNo default behavior or values.\r\nCommand Modes\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 19 of 101\n\nPrivileged EXEC\r\nCommand History\r\nRelease Modification\r\n12.1(5)T This command was introduced.\r\n12.2(33)SRA This command was integrated into Cisco IOS Release 12.2(33)SRA.\r\nUsage Guidelines\r\nThe Parser Cache feature optimizes the parsing (translation and execution) of Cisco IOS software configuration\r\ncommand lines by remembering how to parse recently encountered command lines, decreasing the time required\r\nto process large configuration files.\r\nThe clear parser cache command will free the system memory used by the Parser Cache feature and will erase the\r\nhit/miss statistics stored for the output of the show parser statistics EXEC command. This command is only\r\neffective when the Parser Cache feature is enabled.\r\nExamples\r\nThe following example shows the clearing of the parser cache:\r\nRouter# show parser statistics\r\nLast configuration file parsed:Number of Commands:1484, Time:820 ms\r\nParser cache:enabled, 1460 hits, 26 misses\r\nRouter# clear parser cache\r\nRouter# show parser statistics\r\nLast configuration file parsed:Number of Commands:1484, Time:820 ms\r\nParser cache:enabled, 0 hits, 1 misses\r\nRelated Commands\r\nCommand Description\r\nparser cache Enables or disables the Parser Cache feature.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 20 of 101\n\nCommand Description\r\nshow parser\r\nstatistics\r\nDisplays statistics about the last configuration file parsed and the status of the Parser\r\nCache feature.\r\nclear parser statistics\r\nTo clear the parser performance statistics, use the clear parser statistics command in privileged EXEC mode.\r\nclear parser statistics\r\nSyntax Description\r\nThis command has no arguments or keywords.\r\nCommand Default\r\nNo default behavior or values.\r\nCommand Modes\r\nPrivileged EXEC\r\nCommand History\r\nRelease Modification\r\n15.0S This command was introduced.\r\nUsage Guidelines\r\nThe clear parser statistics command will free the system memory used for recording parser performance statistics\r\nstored for the output of the show parser statistics EXEC command..\r\nExamples\r\nThe following example shows the clearing parser statistics:\r\nRouter# show parser statistics\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 21 of 101\n\nLast configuration file parsed: Number of Commands: 1, Time: 31 ms\r\nParser cache: enabled, 129 hits, 46 misses\r\nActive startup time: 0\r\nStandby startup time: 186\r\nCopy to running-config time:0\r\nBulksync time:0\r\nTop 10 slowest command:\r\n Function Time (ms) Command\r\n 0xE71F90 7 shutdown\r\n 0x1235280 11 no ip address\r\n 0x1235280 11 no ip address\r\n 0x1235280 11 no ip address\r\n 0x1235280 11 no ip address\r\n 0x1235280 12 no ip address\r\n 0x1235280 12 no ip address\r\n 0x1235280 12 no ip address\r\n 0x1235280 12 no ip address\r\n 0xD6C940 6170 show run\r\nParser last bootup cache hits:\r\n Bootup hits:125\r\n Bootup misses:43\r\n Bootup clear parser cache:0\r\nRouter# clear parser statistics\r\nfunc=E01730, duration=0 cmd= clear parser statistics\r\nRouter# show parser statistics\r\nLast configuration file parsed: Number of Commands: 0, Time: 0 ms\r\nParser cache: enabled, 130 hits, 47 misses\r\nActive startup time: 0\r\nStandby startup time: 0\r\nCopy to running-config time:0\r\nBulksync time:0\r\nTop 10 slowest command:\r\n Function Time (ms) Command\r\nParser last bootup cache hits:\r\n Bootup hits:0\r\n Bootup misses:0\r\n Bootup clear parser cache:0\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 22 of 101\n\nRelated Commands\r\nCommand Description\r\nparser cache Enables or disables the Parser Cache feature.\r\nshow parser\r\nstatistics\r\nDisplays statistics about the last configuration file parsed and the status of the Parser\r\nCache feature.\r\nclear platform netint\r\nTo clear the interrupt-throttling counters for the platform, use the clear platform netint command in privileged\r\nEXEC mode.\r\nclear platform netint\r\nSyntax Description\r\nThis command has no arguments or keywords.\r\nCommand Default\r\nThis command has no default settings.\r\nCommand Modes\r\nPrivileged EXEC\r\nCommand History\r\nRelease Modification\r\n12.2(17b)SXA Support for this command was introduced on the Supervisor Engine 720.\r\n12.2(17d)SXB\r\nSupport for this command on the Supervisor Engine 2 was extended to Release\r\n12.2(17d)SXB.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 23 of 101\n\nRelease Modification\r\n12.2(33)SRA This command was integrated into Cisco IOS Release 12.2(33)SRA.\r\nExamples\r\nThis example shows how to clear the interrupt-throttling counters for the platform:\r\nRouter#\r\nclear platform netint\r\nRouter#\r\nRelated Commands\r\nCommand Description\r\nshow platform netint Displays the platform network-interrupt information.\r\nclear processes interrupt mask\r\nTo clear interrupt mask details for all processes in the interrupt mask buffer, use the clear processes interrupt mask\r\ndetail command in privileged EXEC mode.\r\nclear processes interrupt mask detail\r\nSyntax Description\r\nThis command has no arguments or keywords.\r\nCommand Modes\r\nPrivileged EXEC\r\nCommand History\r\nRelease Modification\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 24 of 101\n\nRelease Modification\r\n12.4(2)T\r\nThis command was introduced as part of the Process Interrupt Mask Profiler Enhancement\r\nfeature.\r\nUsage Guidelines\r\nSee the documentation of the scheduler interrupt mask commands (listed in the Related Commands table) for\r\nfurther details on process interrupt mask profiling.\r\nExamples\r\nThe following example demonstrates how to the clear interrupt mask statistics from system memory for all\r\nprocesses:\r\nRouter# clear processes interrupt mask detail\r\nRelated Commands\r\nCommand Description\r\nscheduler interrupt mask\r\nprofile\r\nStarts interrupt mask profiling for all processes running on the system\r\nscheduler interrupt mask size\r\nConfigures the maximum number of entries that can exist in the interrupt\r\nmask buffer.\r\nscheduler interrupt mask time\r\nConfigures the maximum time that a process can run with interrupts\r\nmasked.\r\nshow process interrupt mask\r\nbuffer\r\nDisplays the information stored in the interrupt mask buffer.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 25 of 101\n\nCommand Description\r\nshow processes interrupt mask\r\ndetail\r\nDisplays interrupt masked details for the specified processes or all\r\nprocesses in the system.\r\nclear scp accounting\r\nTo clear the Switch-Module Configuration Protocol (SCP) accounting information, use the clear scp accounting\r\ncommand in privileged EXEC mode.\r\nclear scp accounting\r\nSyntax Description\r\nThis command has no arguments or keywords.\r\nCommand Modes\r\nPrivileged EXEC (#)\r\nCommand History\r\nRelease Modification\r\n15.0(1)M This command was introduced into a release earlier than Cisco IOS Release 15.0(1)M.\r\n12.2(33)SXI This command was integrated into a release earlier than Cisco IOS Release 12.2(33)SXI.\r\nExamples\r\nThe following example shows how to clear the SCP accounting information:\r\nRouter# clear scp accounting\r\nRelated Commands\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 26 of 101\n\nCommand Description\r\nshow scp Displays SCP information.\r\nclear tcp\r\nTo clear a TCP connection, use the clear tcp command in privileged EXEC mode.\r\nclear tcp {line line-number | local hostname port remote hostname port | tcb address}\r\nSyntax Description\r\nline line-number Line number of the TCP connection to clear.\r\nlocal hostname port remote\r\nhostname port\r\nHost name of the local router and port and host name of the remote router and\r\nport of the TCP connection to clear.\r\ntcb address\r\nTransmission Control Block (TCB) address of the TCP connection to clear.\r\nThe TCB address is an internal identifier for the endpoint.\r\nCommand Modes\r\nPrivileged EXEC\r\nCommand History\r\nRelease Modification\r\n11.1 This command was introduced.\r\n12.2(33)SRA This command was integrated into Cisco IOS Release 12.2(33)SRA.\r\nUsage Guidelines\r\nThe clear tcp command is particularly useful for clearing hung TCP connections.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 27 of 101\n\nThe clear tcp line line-number command terminates the TCP connection on the specified tty line. Additionally, all\r\nTCP sessions initiated from that tty line are terminated.\r\nThe clear tcp local hostname port remote hostname port command terminates the specific TCP connection\r\nidentified by the host name and port pair of the local and remote router.\r\nThe clear tcp tcb address command terminates the specific TCP connection identified by the TCB address.\r\nExamples\r\nThe following example clears a TCP connection using its tty line number. The show tcp command displays the\r\nline number (tty2) that is used in the clear tcp command.\r\nRouter# show tcp\r\n \r\n tty2, virtual tty from host router20.cisco.com\r\n Connection state is ESTAB, I/O status: 1, unread input bytes: 0\r\n Local host: 171.69.233.7, Local port: 23\r\n Foreign host: 171.69.61.75, Foreign port: 1058\r\n \r\n Enqueued packets for retransmit: 0, input: 0, saved: 0\r\n \r\n Event Timers (current time is 0x36144):\r\n Timer Starts Wakeups Next\r\n Retrans 4 0 0x0\r\n TimeWait 0 0 0x0\r\n AckHold 7 4 0x0\r\n SendWnd 0 0 0x0\r\n KeepAlive 0 0 0x0\r\n GiveUp 0 0 0x0\r\n PmtuAger 0 0 0x0\r\n \r\n iss: 4151109680 snduna: 4151109752 sndnxt: 4151109752 sndwnd: 24576\r\n irs: 1249472001 rcvnxt: 1249472032 rcvwnd: 4258 delrcvwnd: 30\r\n \r\n SRTT: 710 ms, RTTO: 4442 ms, RTV: 1511 ms, KRTT: 0 ms\r\n minRTT: 0 ms, maxRTT: 300 ms, ACK hold: 300 ms\r\n \r\nRouter# clear tcp line 2\r\n [confirm]\r\n [OK]\r\nThe following example clears a TCP connection by specifying its local router host name and port and its remote\r\nrouter host name and port. The show tcp brief command displays the local (Local Address) and remote (Foreign\r\nAddress) host names and ports to use in the clear tcp command.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 28 of 101\n\nRouter# show tcp brief\r\nTCB Local Address Foreign Address (state)\r\n 60A34E9C router1.cisco.com.23 router20.cisco.1055 ESTAB\r\n \r\nRouter# clear tcp local router1 23 remote router20 1055\r\n [confirm]\r\n [OK]\r\nThe following example clears a TCP connection using its TCB address. The show tcp brief command displays the\r\nTCB address to use in the clear tcp command.\r\nRouter# show tcp brief\r\n TCB Local Address Foreign Address (state)\r\n 60B75E48 router1.cisco.com.23 router20.cisco.1054 ESTAB\r\n \r\nRouter# clear tcp tcb 60B75E48\r\n [confirm]\r\n [OK]\r\nRelated Commands\r\nCommand Description\r\nshow tcp Displays the status of TCP connections.\r\nshow tcp brief Displays a concise description of TCP connection endpoints.\r\nclear vlan counters\r\nTo clear the software-cached counter values to start from zero again for a specified VLAN or all existing VLANs,\r\nuse the clear vlan counters command in privileged EXEC mode.\r\nclear vlan [vlan-id] counters\r\nSyntax Description\r\nvlan-id (Optional) The ID of a specific VLAN. Range: 1 to 4094.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 29 of 101\n\nCommand Default\r\nThis command has no default settings.\r\nCommand Modes\r\nPrivileged EXEC (#)\r\nCommand History\r\nRelease Modification\r\n12.2(14)SX Support for this command was introduced on the Supervisor Engine 720.\r\n12.2(17d)SXB\r\nSupport for this command on the Supervisor Engine 2 was extended to Release\r\n12.2(17d)SXB.\r\n12.2(33)SRA This command was integrated into Cisco IOS Release 12.2(33)SRA.\r\nUsage Guidelines\r\nIf you do not specify a vlan-id ; the software-cached counter values for all existing VLANs are cleared.\r\nExamples\r\nThis example shows how to clear the software-cached counter values for a specific VLAN:\r\nRouter# clear vlan 10 counters\r\nClear \"show vlan\" counters on this vlan [confirm]y\r\nRouter#\r\nRelated Commands\r\nCommand Description\r\nshow vlan counters Displays the software-cached counter values.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 30 of 101\n\nclock\r\nTo configure the port clocking mode for the 1000BASE-T transceivers, use the clock command in interface\r\nconfiguration mode. To return to the default settings,use the no form of this command.\r\nclock {auto | active [prefer] | passive [prefer]}\r\nno clock\r\nSyntax Description\r\nauto Enables the automatic-clock configuration.\r\nactive Enables the active operation.\r\nprefer (Optional) Negotiates the specified mode with the far end of the link.\r\npassive Enables the passive operation.\r\nCommand Default\r\nauto\r\nCommand Modes\r\nInterface configuration\r\nCommand History\r\nRelease Modification\r\n12.2(17a)SX Support for this command was introduced on the Supervisor Engine 720.\r\n12.2(33)SRA This command was integrated into Cisco IOS Release 12.2(33)SRA.\r\nUsage Guidelines\r\nThis command is supported on the 1000BASE-T transceivers only.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 31 of 101\n\nIf the clock mode of the near end of a link does not match the clock mode of the far end, the line protocol does not\r\ncome up.\r\nThe active and passive clock status is determined during the auto negotiation process before the transmission link\r\nis established.\r\nThe clock command supports the following configurations:\r\nauto --Auto negotiates with the far end of the link but preference is given to the active-clock switch.\r\nactive --Uses a local clock to determine transmitter-operation timing.\r\npassive --Recovers the clock from the received signal and uses the recovered clock to determine\r\ntransmitter-operation timing.\r\nactive prefer --Auto negotiates with the far end of the link but preference is given to the active-clock\r\nswitch.\r\npassive prefer --Auto negotiates with the far end of the link but preference is given to the passive-clock\r\nswitch.\r\nEnter the show running-config interface command to display the current clock mode.\r\nEnter the show interfaces command to display the clock mode that is negotiated by the firmware.\r\nExamples\r\nThis example shows how to enable the active-clock operation:\r\nRouter(config-if)# clock active\r\nRouter(config-if)#\r\nRelated Commands\r\nCommand Description\r\nshow interfaces Displays traffic that is seen by a specific interface.\r\nshow running-config interface Displays the status and configuration of the module or Layer 2 VLAN.\r\nclock initialize nvram\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 32 of 101\n\nTo restart the system clock from the last known system clock value, use the clock initialize nvram command in\r\nglobal configuration mode. To disable the restart of the system clock from the last known system clock value, use\r\nthe no form of this command.\r\nclock initialize nvram\r\nno clock initialize nvram\r\nSyntax Description\r\nThis command has no arguments or keywords.\r\nCommand Default\r\nBy default, the system clock is set to restart from the last known system clock value for platforms that have no\r\nhardware calendar.\r\nCommand Modes\r\nGlobal configuration (config)\r\nCommand History\r\nRelease Modification\r\n12.3(4)T This command was introduced.\r\nUsage Guidelines\r\nFor platforms that have hardware calendars, the clock initialize nvram command is not available. When the no\r\nform of the command is configured, the system clock gets initialized to default standard values. The default values\r\ncan be either 1MAR1993 or 1MAR2002.\r\nExamples\r\nThe following example shows how to set the system clock to restart from the last known system clock value:\r\nRouter(config)# clock initialize nvram\r\nconfig-register\r\nTo change the configuration register settings, use the config-register command in global configuration mode.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 33 of 101\n\nconfig-register value\r\nSyntax Description\r\nvalue\r\nHexadecimal or decimal value that represents the 16-bit configuration register value that you want to\r\nuse the next time the router is restarted. The value range is from 0x0 to 0xFFFF (0 to 65535 in\r\ndecimal).\r\nCommand Default\r\nRefer to the documentation for your platform for the default configuration register value. For many newer\r\nplatforms, the default is 0x2102, which causes the router to boot from Flash memory and the Break key to be\r\nignored.\r\nCommand Modes\r\nGlobal configuration\r\nCommand History\r\nRelease Modification\r\n10.0 This command was introduced.\r\n12.2(33)SRA This command was integrated into Cisco IOS Release 12.2(33)SRA.\r\n12.2(31)SB2 This command was integrated into Cisco IOS Release 12.2(31)SB2.\r\n12.2(33)SXH This command was integrated into Cisco IOS Release 12.2(31)SXH.\r\nUsage Guidelines\r\nThis command applies only to platforms that use a software configuration register.\r\nThe lowest four bits of the configuration register (bits 3, 2, 1, and 0) form the boot field. The boot field determines\r\nif the router boots manually, from ROM, or from Flash or the network.\r\nTo change the boot field value and leave all other bits set to their default values, follow these guidelines:\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 34 of 101\n\nIf you set the configuration register boot field value to 0x0, you must boot the operating system manually\r\nwith the boot command.\r\nIf you set the configuration register boot field value to 0x1, the router boots using the default ROM\r\nsoftware.\r\nIf you set the configuration register boot field to any value from 0x2 to 0xF, the router uses the boot field\r\nvalue to form a default boot filename for booting from a network server.\r\nFor more information about the configuration register bit settings and default filenames, refer to the appropriate\r\nrouter hardware installation guide.\r\nNote\r\nIn a virtual switch application, If you have configured your config-register with a value that would\r\nskip file parsing during the bootup process, your change to either a standalone or virtual switch will\r\nnot take place until you reconfigure your config-register. The config-register must be allowed to parse\r\nfiles in order to ensure the conversion from either a standalone or virtual switch.\r\nExamples\r\nIn the following example, the configuration register is set to boot the system image from Flash memory:\r\nconfig-register 0x2102\r\nRelated Commands\r\nCommand Description\r\nboot system Specifies the system image that the router loads at startup.\r\nconfreg Changes the configuration register settings while in ROM monitor mode.\r\no Lists the value of the boot field (bits 0 to 3) in the configuration register.\r\nshow\r\nversion\r\nDisplays the configuration of the system hardware, the software version, the names and\r\nsources of configuration files, and the boot images.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 35 of 101\n\nconfigure check syntax\r\nTo check the syntax configuration, use the configure check syntax command in privileged EXEC mode.\r\nconfigure check syntax [source-location]\r\nSyntax Description\r\nsource-location (Optional) Location or the address of the source to be checked.\r\nCommand Default\r\nThe syntax configuration is not checked.\r\nCommand Modes\r\nPrivileged EXEC (#)\r\nCommand History\r\nRelease Modification\r\n15.0(1)M This command was introduced in a release earlier than Cisco IOS Release 15.0(1)M.\r\n12.2(33)SRB This command was integrated into a release earlier than Cisco IOS Release 12.2(33)SRB.\r\nExamples\r\nThe following example shows how to check the syntax configuration using the configure check syntax command:\r\nRouter# configure check syntax revrcsf:\r\nRelated Commands\r\nCommand Description\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 36 of 101\n\nCommand Description\r\nconfigure\r\nrevert\r\nCancels the timed rollback and triggers the rollback immediately, or resets the parameters\r\nfor the timed rollback.\r\nconfiguration mode exclusive\r\nNote\r\nEffective with Cisco IOS XE Release 3.1S, the configuration mode exclusive command is replaced\r\nby the parser command serializer command. See the parser command serializer command for more\r\ninformation.\r\nTo enable single-user (exclusive) access functionality for the Cisco CLI, use the configuration mode exclusive\r\ncommand in global configuration mode. To disable the single-user access (configuration locking) feature, use the\r\nno form of this command.\r\nconfiguration mode exclusive {auto | manual} [expire seconds] [lock-show] [interleave] [terminate] [config-wait seconds] [retry-wait seconds]\r\nno configuration mode exclusive\r\nSyntax Description\r\nauto Automatically limits configuration to single-user mode.\r\nmanual Allows you to manually limit the configuration file to single-user mode.\r\nexpire\r\nseconds\r\n(Optional) Specifies the number of seconds in which the configuration lock is released after the\r\nuser stops making configuration changes.\r\nlock-show\r\n(Optional) Gives priority to configuration commands being executed from the exclusive\r\nconfiguration session, and prevents the execution of show commands.\r\ninterleave (Optional) Allows show commands from sessions that are not holding the configuration lock to\r\nbe executed when the user in the session holding the configuration lock is not making\r\nconfiguration changes.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 37 of 101\n\nNote\r\n \r\nIf you entered the lock-show keyword, you should enter this keyword.\r\nterminate\r\n(Optional) Causes the configuration command executed from the exclusive configuration\r\nsession to terminate show and clear commands being executed in other sessions.\r\nconfig-wait\r\nseconds\r\n(Optional) Specifies the amount of time, in seconds, that a configuration command entered by a\r\nuser in single user mode waits for show commands entered by other users to finish being\r\nexecuted. If the show command is still being executed when the timer expires and if the\r\nterminate option is set, the configuration command terminates the show command. If the\r\nconfiguration command completes execution before the specified number of seconds, the show\r\ncommand begins execution.\r\nretry-wait\r\nseconds\r\n(Optional) Specifies the amount of time, in seconds, that show and clear EXEC commands will\r\nwait for a configuration command entered by a user in exclusive configuration mode to\r\ncomplete execution.\r\nIf the configuration command is still being executed when the specified amount of time has\r\npassed, the EXEC commands generate an error message and are terminated.\r\nIf execution of the configuration command is completed before the specified number of\r\nseconds, the EXEC commands are executed.\r\nCommand Default\r\nSingle-user mode is disabled.\r\nCommand Modes\r\nGlobal configuration (config)\r\nCommand History\r\nRelease Modification\r\n12.3(14)T This command was introduced.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 38 of 101\n\nRelease Modification\r\n12.0(31)S\r\nThis command was integrated into Cisco IOS Release 12.0(31)S. The following\r\nkeywords were added: config-wait , expire , interleave, lock-show ,retry-wait, and\r\nterminate . New functionality was added, including Access Session Locking.\r\n12.2(33)SRA This command was integrated into Cisco IOS Release 12.2(33)SRA.\r\n12.2(33)SB This command was integrated into Cisco IOS Release 12.2(33)SB.\r\n12.2(33)SXI\r\nThis command was integrated into a release earlier than Cisco IOS Release\r\n12.2(33)SXI.\r\n15.0(1)S This command was deprecated for Cisco IOS Release 15.0(1)S.\r\nCisco IOS XE\r\nRelease 3.1S\r\nThis command was replaced by the parser command serializer command.\r\nUsage Guidelines\r\nNote\r\nAs of the 15.0 release, the configuration mode exclusive command is no longer available on the S and\r\nT trains.\r\nThe configuration mode exclusive command enables the exclusive configuration lock feature. The exclusive\r\nconfiguration lock allows single-user access to configuration modes using single-user configuration mode. While\r\nthe device configuration is locked, no other users can enter configuration commands.\r\nUsers accessing the device using the state-full, session-based transports (telnet, Secure Shell (SSH) are able to\r\nenter single-user configuration mode. The user enters single-user configuration mode by acquiring the exclusive\r\nconfiguration lock using the configure terminal lock privileged EXEC mode command. The configuration lock is\r\nreleased when the user exits configuration mode by using the end or exit command, or by pressing Ctrl-Z. While a\r\nuser is in single-user configuration mode, no other users can configure the device. Users accessing Command Line\r\nInterface (CLI) options through stateless protocols (that is, the HTTP web-based user interface) cannot access\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 39 of 101\n\nsingle-user configuration mode. (However, an Application Programming Interface (API) allows the stateless\r\ntransports to lock the configuration mode, complete its operations, and release the lock.)\r\nExamples\r\nThe following example shows how to configure the configuration file for single-user autoconfiguration mode by\r\nusing the configuration mode exclusive auto command. Use the configuration terminal command to enter global\r\nconfiguration mode and lock the configuration mode exclusively. After the Cisco configuration mode is locked\r\nexclusively, you can verify this configuration by entering the show configuration lock command.\r\nDevice# configure terminal\r\nEnter configuration commands, one per line. End with CNTL/Z.\r\nDevice(config)# configuration mode exclusive auto\r\nDevice(config)# end\r\nDevice# show running-configuration\r\n | include config\r\nBuilding configuration...\r\nCurrent configuration : 2296 bytes\r\nconfiguration mode exclusive auto \u003c========== auto policy\r\nDevice# configure terminal ?\r\n \u003c======== lock option not displayed when in auto policy\r\nDevice# configure terminal\r\n \u003c======= acquires the lock\r\nThe configuration mode is locked exclusively. The lock is cleared after you exit from configuration mode by\r\nentering the end or exit command.\r\nEnter configuration commands, one per line. End with CNTL/Z.\r\nDevice(config)#\r\nDevice(config)# show configuration lock\r\nParser Configure Lock\r\n---------------------\r\nOwner PID : 3\r\nUser : unknown\r\nTTY : 0\r\nType : EXCLUSIVE\r\nState : LOCKED\r\nClass : EXPOSED\r\nCount : 1\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 40 of 101\n\nPending Requests : 0\r\nUser debug info : configure terminal\r\nSession idle state : TRUE\r\nNo of exec cmds getting executed : 0\r\nNo of exec cmds blocked : 0\r\nConfig wait for show completion : FALSE\r\nRemote ip address : Unknown\r\nLock active time (in Sec) : 6\r\nLock Expiration timer (in Sec) : 593\r\nDevice(config)#\r\nDevice(config)# end\r\n \u003c========= releases the lock\r\nDevice#\r\nDevice# show configuration lock\r\nParser Configure Lock\r\n---------------------\r\nOwner PID : -1\r\nUser : unknown\r\nTTY : -1\r\nType : NO LOCK\r\nState : FREE\r\nClass : unknown\r\nCount : 0\r\nPending Requests : 0\r\nUser debug info :\r\nSession idle state : TRUE\r\nNo of exec cmds getting executed : 0\r\nNo of exec cmds blocked : 0\r\nConfig wait for show completion : FALSE\r\nRemote ip address : Unknown\r\nLock active time (in Sec) : 0\r\nLock Expiration timer (in Sec) : 0\r\nThe following example shows how to enable the exclusive locking feature in manual mode by using the\r\nconfiguration mode exclusive manual command. Once you have configured manual exclusive mode, you can lock\r\nthe configuration mode by using the configure terminal lock command. In this mode, the configure terminal\r\ncommand does not automatically lock the parser configuration mode. The lock is cleared after you exit from\r\nconfiguration mode by entering the end or exit command.\r\nDevice# configure terminal\r\n \r\nConfiguration mode locked exclusively. The lock will be cleared once you exit out of configuration mode using en\r\nEnter configuration commands, one per line. End with CNTL/Z.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 41 of 101\n\nDevice(config)# configuration mode exclusive manual\r\n \r\nDevice(config)# end\r\nDevice#\r\nDevice# show running-configuration\r\n | include configuration\r\nBuilding configuration...\r\nCurrent configuration : 2298 bytes\r\nconfiguration mode exclusive manual \u003c==== 'manual' policy\r\nDevice# show configuration lock\r\nParser Configure Lock\r\n---------------------\r\nOwner PID : -1\r\nUser : unknown\r\nTTY : -1\r\nType : NO LOCK\r\nState : FREE\r\nClass : unknown\r\nCount : 0\r\nPending Requests : 0\r\nUser debug info :\r\nSession idle state : TRUE\r\nNo of exec cmds getting executed : 0\r\nNo of exec cmds blocked : 0\r\nConfig wait for show completion : FALSE\r\nRemote ip address : Unknown\r\nLock active time (in Sec) : 0\r\nLock Expiration timer (in Sec) : 0\r\nDevice#\r\nDevice# configure terminal ?\r\n \r\nlock Lock configuration mode \u003c========= 'lock' option displayed in 'manual' policy\r\nDevice# configure terminal \u003c============ ‘configure terminal’ won't acquire lock automatically\r\nEnter configuration commands, one per line. End with CNTL/Z.\r\nDevice(config)# show configuration lock\r\n \r\nParser Configure Lock\r\n---------------------\r\nOwner PID : -1\r\nUser : unknown\r\nTTY : -1\r\nType : NO LOCK\r\nState : FREE\r\nClass : unknown\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 42 of 101\n\nCount : 0\r\nPending Requests : 0\r\nUser debug info :\r\nSession idle state : TRUE\r\nNo of exec cmds getting executed : 0\r\nNo of exec cmds blocked : 0\r\nConfig wait for show completion : FALSE\r\nRemote ip address : Unknown\r\nLock active time (in Sec) : 0\r\nLock Expiration timer (in Sec) : 0\r\nDevice(config)# end\r\n \r\nDevice# show configuration lock\r\nParser Configure Lock\r\n---------------------\r\nOwner PID : -1\r\nUser : unknown\r\nTTY : -1\r\nType : NO LOCK\r\nState : FREE\r\nClass : unknown\r\nCount : 0\r\nPending Requests : 0\r\nUser debug info :\r\nSession idle state : TRUE\r\nNo of exec cmds getting executed : 0\r\nNo of exec cmds blocked : 0\r\nConfig wait for show completion : FALSE\r\nRemote ip address : Unknown\r\nLock active time (in Sec) : 0\r\nLock Expiration timer (in Sec) : 0\r\nDevice#\r\nDevice# configure\r\n \r\nDevice# configure terminal\r\nDevice# configure terminal ?\r\n \r\nlock Lock configuration mode \u003c======= 'lock' option displayed when in 'manual' policy\r\nDevice# configure terminal lock\r\n \r\nDevice# configure terminal lock\r\n \u003c============ acquires exclusive configuration lock\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 43 of 101\n\nConfiguration mode is locked exclusively. The lock is cleared after you exit from configuration mode by entering\r\nthe end or exit command. Enter configuration commands, one per line. End with CNTL/Z.\r\nDevice(config)# show configuration lock\r\n \r\nParser Configure Lock\r\n---------------------\r\nOwner PID : 3\r\nUser : unknown\r\nTTY : 0\r\nType : EXCLUSIVE\r\nState : LOCKED\r\nClass : EXPOSED\r\nCount : 1\r\nPending Requests : 0\r\nUser debug info : configure terminal lock\r\nSession idle state : TRUE\r\nNo of exec cmds getting executed : 0\r\nNo of exec cmds blocked : 0\r\nConfig wait for show completion : FALSE\r\nRemote ip address : Unknown\r\nLock active time (in Sec) : 5\r\nLock Expiration timer (in Sec) : 594\r\nDevice(config)# end\r\n \u003c================ 'end' releases exclusive configuration lock\r\nDevice# show configuration lock\r\nParser Configure Lock\r\n---------------------\r\nOwner PID : -1\r\nUser : unknown\r\nTTY : -1\r\nType : NO LOCK\r\nState : FREE\r\nClass : unknown\r\nCount : 0\r\nPending Requests : 0\r\nUser debug info :\r\nSession idle state : TRUE\r\nNo of exec cmds getting executed : 0\r\nNo of exec cmds blocked : 0\r\nConfig wait for show completion : FALSE\r\nRemote ip address : Unknown\r\nLock active time (in Sec) : 0\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 44 of 101\n\nLock Expiration timer (in Sec) : 0\r\nDevice#\r\nRelated Commands\r\nCommand Description\r\nconfigure terminal Enters global configuration mode.\r\ndebug configuration\r\nlock\r\nEnables debugging of the Cisco configuration lock.\r\nshow configuration\r\nlock\r\nDisplays information about the lock status of the running configuration file during a\r\nconfiguration replace operation.\r\nconfigure confirm\r\nTo confirm replacement of the current running configuration with a saved Cisco configuration file, use the\r\nconfigure confirm command in privileged EXEC mode.\r\nconfigure confirm\r\nSyntax Description\r\nThis command has no arguments or keywords.\r\nCommand Default\r\nThe replacement of the current running configuration with a saved configuration file is not confirmed.\r\nCommand Modes\r\nPrivileged EXEC (#)\r\nCommand History\r\nRelease Modification\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 45 of 101\n\nRelease Modification\r\n12.3(7)T This command was introduced.\r\n12.2(25)S This command was integrated into Cisco IOS Release 12.2S.\r\n12.2(28)SB This command was integrated into Cisco IOS Release 12.2SB.\r\n12.2(33)SRA This command was integrated into Cisco IOS Release 12.2SR.\r\n12.2(33)SXH This command was integrated into Cisco IOS Release 12.2SX.\r\n12.2(33)SB\r\nThis command was integrated into Cisco IOS Release 12.2(33)SB and\r\nimplemented on the Cisco 10000 series.\r\n12.2(33)SXI This command was integrated into Cisco IOS Release 12.2(33)SXI.\r\nCisco IOS XE Release\r\n3.9S\r\nThis command was integrated into Cisco IOS XE Release 3.9S.\r\nUsage Guidelines\r\nThe configure confirm command is used only if the time seconds keyword and argument of the configure replace\r\ncommand are specified. If the configure confirm command is not entered within the specified time limit, the\r\nconfiguration replace operation is automatically reversed (in other words, the current running configuration file is\r\nrestored to the configuration state that existed prior to entering the configure replace command).\r\nExamples\r\nThe following example shows the use of the configure replace command with the time seconds keyword and\r\nargument. You must enter the configure confirm command within the specified time limit to confirm replacement\r\nof the current running configuration file:\r\nDevice# configure replace nvram:startup-config time 120\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 46 of 101\n\nThis will apply all necessary additions and deletions\r\nto replace the current running configuration with the\r\ncontents of the specified configuration file, which is\r\nassumed to be a complete configuration, not a partial\r\nconfiguration. Enter Y if you are sure you want to proceed. ? [no]: Y\r\nTotal number of passes: 1\r\nRollback Done\r\nDevice# configure confirm\r\nRelated Commands\r\nCommand Description\r\narchive config Saves a copy of the current running configuration to the Cisco configuration archive.\r\nconfigure replace Replaces the current running configuration with a saved Cisco configuration file.\r\nmaximum\r\nSets the maximum number of archive files of the running configuration to be saved in the\r\nCisco configuration archive.\r\npath (config-archive)\r\nSpecifies the location and filename prefix for the files in the Cisco configuration archive.\r\nshow archive Displays information about the files saved in the Cisco configuration archive.\r\ntime-period\r\nSets the time increment for automatically saving an archive file of the current running\r\nconfiguration in the Cisco configuration archive.\r\nconfigure memory\r\nTo configure the system from the system memory, use the configure memory command in privileged EXEC mode.\r\nconfigure memory\r\nSyntax Description\r\nThis command has no arguments or keywords.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 47 of 101\n\nCommand Modes\r\nPrivileged EXEC\r\nCommand History\r\nRelease Modification\r\n10.0 This command was introduced.\r\n12.2(33)SRA This command was integrated into Cisco IOS Release 12.2(33)SRA.\r\nUsage Guidelines\r\nOn all platforms except Class A Flash file system platforms, this command executes the commands located in the\r\nconfiguration file in NVRAM (the “startup configuration file”).\r\nOn Class A Flash file system platforms, if you specify the configure memory command, the router executes the\r\ncommands pointed to by the CONFIG_FILE environment variable. The CONFIG_FILE environment variable\r\nspecifies the location of the configuration file that the router uses to configure itself during initialization. The file\r\ncan be located in NVRAM or any of the Flash file systems supported by the platform.\r\nWhen the CONFIG_FILE environment variable specifies NVRAM, the router executes the NVRAM\r\nconfiguration only if it is an entire configuration, not a distilled version. A distilled configuration is one that does\r\nnot contain access lists.\r\nTo view the contents of the CONFIG_FILE environment variable, use the show bootvar EXEC command. To\r\nmodify the CONFIG_FILE environment variable, use the boot config command and then save your changes by\r\nissuing the copy system:running-config nvram:startup-config command.\r\nExamples\r\nIn the following example, a router is configured from the configuration file in the memory location pointed to by\r\nthe CONFIG_FILE environment variable:\r\nRouter# configure memory\r\nRelated Commands\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 48 of 101\n\nCommand Description\r\nboot config\r\nSpecifies the device and filename of the configuration file from which the router\r\nconfigures itself during initialization (startup).\r\ncopy system:running-config nvram:startup-config\r\nSaves the running configuration as the startup configuration file.\r\nshow bootvar\r\nDisplays the contents of the BOOT environment variable, the name of the\r\nconfiguration file pointed to by the CONFIG_FILE environment variable, the\r\ncontents of the BOOTLDR environment variable, and the configuration register\r\nsetting.\r\nconfigure network\r\nThe configure network command was replaced by the copy {rcp | tftp } running-config command in Cisco IOS\r\nRelease 11.0. To maintain backward compatibility, the configure network command continues to function in Cisco\r\nIOS Release 12.2(11)T for most systems, but support for this command may be removed in a future release.\r\nThe copy {rcp | tftp } running-config command was replaced by the copy {ftp: | rcp: | tftp: }[filename ] system:\r\nrunning-config command in Cisco IOS Release 12.1.\r\nThe copy {ftp: | rcp: | tftp: }[filename ] system: running-config command specifies that a configuration file should\r\nbe copied from a FTP, rcp, or TFTP source to the running configuration. See the description of the copy command\r\nin this chapter for more information.\r\nconfigure overwrite-network\r\nThe configure overwrite-network has been replaced by the copy {ftp-url | rcp-url | tftp-url nvram:startup-config\r\ncommand. See the description of the copy command in the Cisco IOS File System Commands chapter for more\r\ninformation.\r\nconfigure replace\r\nTo replace the current running configuration with a saved Cisco configuration file, use the configure replace\r\ncommand in privileged EXEC mode.\r\nconfigure replace target-url [nolock] list force ignorecase [revert trigger [error] [timer minutes] | time\r\nminutes]\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 49 of 101\n\nSyntax Description\r\ntarget-url\r\nURL (accessible by the Cisco file system) of the saved Cisco configuration file that is to\r\nreplace the current running configuration.\r\nnolock\r\n(Optional) Disables the locking of the running configuration file that prevents other users from\r\nchanging the running configuration during a configuration replace operation.\r\nlist\r\nDisplays a list of the command lines applied by the Cisco software parser during each pass of\r\nthe configuration replace operation. The total number of passes performed is also displayed.\r\nforce\r\nReplaces the current running configuration file with the specified saved Cisco configuration file\r\nwithout prompting you for confirmation.\r\nignorecase Instructs the configuration to ignore the case of the configuration confirmation.\r\nrevert\r\ntrigger\r\n(Optional) Sets the triggers for reverting to the original configuration.\r\n(Optional) error : Reverts to the original configuration upon error.\r\n(Optional) timer minutes : Reverts to the original configuration if the specified time\r\nelapses.\r\ntime\r\nminutes\r\n(Optional) Time (in minutes) within which you must enter the configure confirm command to\r\nconfirm replacement of the current running configuration file. If the configure confirm\r\ncommand is not entered within the specified time limit, the configuration replace operation is\r\nautomatically reversed (in other words, the current running configuration file is restored to the\r\nconfiguration state that existed prior to entering the configure replace command).\r\nCommand Modes\r\nPrivileged EXEC (#)\r\nCommand History\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 50 of 101\n\nRelease Modification\r\n12.3(7)T This command was introduced.\r\n12.2(25)S The nolock keyword was added.\r\n12.2(28)SB This command was integrated into Cisco IOS Release 12.2(28)SB.\r\n12.2(33)SRA This command was integrated into Cisco IOS Release 12.2(33)SRA.\r\n12.2(31)SB2 This command was implemented on the Cisco 10000 series.\r\n12.2(33)SXH This command was integrated into Cisco IOS Release 12.2(33)SXH.\r\n12.2(33)SXI This command was integrated into Cisco IOS Release 12.2(33)SXI.\r\n12.4(20)T The revert and trigger keywords were added.\r\n12.2(33)SRC The ignorecase keyword was added.\r\n12.2(33)SB\r\nThis command was integrated into Cisco IOS Release 12.2(33)SB and\r\nimplemented on the Cisco 10000 series.\r\nCisco IOS XE Release\r\n3.9S\r\nThis command was integrated into Cisco IOS XE Release 3.9S.\r\nUsage Guidelines\r\nWhen you are configuring more than one keyword option, the following rules apply:\r\nThe list keyword must be entered before the force and time keywords.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 51 of 101\n\nThe force keyword must be entered before the time keyword.\r\nIf the current running configuration is replaced with a saved Cisco configuration file that contains commands that\r\nare not accepted by the Cisco software parser, an error message is displayed that lists the commands that were not\r\naccepted. The total number of passes performed in the configuration replace operation is also displayed.\r\nIn Cisco IOS Release 12.2(25)S, a locking feature for the configuration replace operation was introduced. When\r\nthe configure replace command is enabled, the Cisco running configuration file is locked by default for the\r\nduration of the configuration replace operation. This locking mechanism prevents other users from changing the\r\nrunning configuration while the replace operation is taking place, which avoids the replace operation from\r\nterminating unsuccessfully. You can disable the locking of the running configuration by using the configure\r\nreplace nolock command.\r\nThe running configuration lock is automatically cleared at the end of the configuration replace operation. You are\r\nnot expected to clear the lock manually during the replace operation, but as a protection against any unforeseen\r\ncircumstances, you can manually clear the lock by using the clear configuration lock command. You can also\r\ndisplay any locks that are currently applied to the running configuration by using the show configuration lock\r\ncommand.\r\nNote\r\nYou cannot replace the controller configuration of the T1 E1 card by using the configure replace\r\ncommand.\r\nExamples\r\nThe following example shows how to replace the current running configuration with a saved Cisco configuration\r\nfile named disk0:myconfig. Note that the configure replace command interactively prompts you to confirm the\r\noperation.\r\nDevice# configure replace disk0:myconfig\r\nThis will apply all necessary additions and deletions\r\nto replace the current running configuration with the\r\ncontents of the specified configuration file, which is\r\nassumed to be a complete configuration, not a partial\r\nconfiguration. Enter Y if you are sure you want to proceed. ? [no]: Y\r\nTotal number of passes: 1\r\nRollback Done\r\nIn the following example, the list keyword is specified to display the command lines that were applied during the\r\nconfiguration replace operation:\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 52 of 101\n\nDevice# configure replace disk0:myconfig list\r\nThis will apply all necessary additions and deletions\r\nto replace the current running configuration with the\r\ncontents of the specified configuration file, which is\r\nassumed to be a complete configuration, not a partial\r\nconfiguration. Enter Y if you are sure you want to proceed. ? [no]: Y\r\n!Pass 1\r\n!List of Commands:\r\nno snmp-server community public ro\r\nsnmp-server community mystring ro\r\nend\r\nTotal number of passes: 1\r\nRollback Done\r\nExamples\r\nThe following example shows how to revert to the Cisco startup configuration file. This example also shows the\r\nuse of the optional force keyword to override the interactive user prompt.\r\nDevice# configure replace nvram:startup-config force\r\nTotal number of passes: 1\r\nRollback Done\r\nExamples\r\nThe following example shows the use of the configure replace command with the time seconds keyword and\r\nargument. You must enter the configure confirm command within the specified time limit to confirm replacement\r\nof the current running configuration file. If the configure confirm command is not entered within the specified\r\ntime limit, the configuration replace operation is automatically reversed (in other words, the current running\r\nconfiguration file is restored to the configuration state that existed prior to entering the configure replace\r\ncommand).\r\nDevice# configure replace nvram:startup-config time 120\r\nThis will apply all necessary additions and deletions\r\nto replace the current running configuration with the\r\ncontents of the specified configuration file, which is\r\nassumed to be a complete configuration, not a partial\r\nconfiguration. Enter Y if you are sure you want to proceed. ? [no]: Y\r\nTotal number of passes: 1\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 53 of 101\n\nRollback Done\r\nDevice# configure confirm\r\nExamples\r\nThe following example shows how to make changes to the current running configuration and then roll back the\r\nchanges. As a part of the configuration rollback operation, you must save the current running configuration before\r\nmaking changes to the file. In this example, the archive config command is used to save the current running\r\nconfiguration. Note that the generated output of the configure replace command indicates that only one pass was\r\nperformed to complete the rollback operation.\r\nNote\r\nThe path command must be configured before using the archive config command.\r\nYou first save the current running configuration in the configuration archive as follows:\r\nDevice# archive config\r\nYou then enter configuration changes as shown in the following example:\r\nDevice# configure terminal\r\nDevice(config)# user netops2 password rain\r\nDevice(config)# user netops3 password snow\r\nDevice(config)# exit\r\nAfter making changes to the running configuration file, you should roll back these changes and revert to the\r\nconfiguration that was present prior to making changes. The show archive command is used to verify the version\r\nof the configuration that needs to be used as a target file. The configure replace command is then used to revert to\r\nthe target configuration file as shown in the following example:\r\nDevice# show archive\r\nThere are currently 1 archive configurations saved.\r\nThe next archive file will be named disk0:myconfig-2\r\n Archive # Name\r\n 0\r\n 1 disk0:myconfig-1 \u003c- Most Recent\r\n 2\r\n 3\r\n 4\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 54 of 101\n\n5\r\n 6\r\n 7\r\n 8\r\n 9\r\n 10\r\nDevice# configure replace disk0:myconfig-1\r\nTotal number of passes: 1\r\nRollback Done\r\nRelated Commands\r\nCommand Description\r\narchive config Saves a copy of the current running configuration to the Cisco configuration archive.\r\nconfigure\r\nconfirm\r\nConfirms replacement of the current running configuration with a saved Cisco\r\nconfiguration file.\r\nmaximum\r\nSets the maximum number of archive files of the running configuration to be saved in the\r\nCisco configuration archive.\r\npath Specifies the location and filename prefix for the files in the Cisco configuration archive.\r\nshow archive Displays information about the files saved in the Cisco configuration archive.\r\ntime-period\r\nSets the time increment for automatically saving an archive file of the current running\r\nconfiguration in the Cisco configuration archive.\r\nconfigure revert\r\nTo cancel the timed rollback and trigger the rollback immediately, or to reset the parameters for the timed\r\nrollback, use the configure revert command in privileged EXEC mode.\r\nconfigure revert {now | timer {minutes | idle minutes}}\r\nSyntax Description\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 55 of 101\n\nnow Cancels the timed rollback and reverts immediately.\r\ntimer Resets the confirmation timer.\r\nminutes Time in minutes (1-120).\r\nidle minutes Idle time in minutes (1-120) for which to wait before rollback.\r\nCommand Modes\r\nPrivileged EXEC (#)\r\nCommand History\r\nRelease Modification\r\n12.2(33)SRC This command was introduced.\r\n12.2(33)SB\r\nThis command was integrated into Cisco IOS Release 12.2(33)SB and\r\nimplemented on the Cisco 10000 series.\r\n12.4(20)T This command was integrated into Cisco IOS Release 12.4(20)T.\r\n12.2(33)SXI This command was integrated into Cisco IOS Release 12.2(33)SXI.\r\nCisco IOS XE Release\r\n3.9S\r\nThis command was integrated into Cisco IOS XE Release 3.9S.\r\nUsage Guidelines\r\nIn order to use the configure revert command to configure a timed rollback, the Configuration Archive\r\nfunctionality must be enable first. The Configuration Archive APIs are used to store the current configuration\r\nbefore applying any changes or rolling back to the previous configuration.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 56 of 101\n\nIn case of multi-user environments, only the user who enabled the timed rollback functionality will have the\r\npermission to perform the following operations:\r\nConfirm the configuration change\r\nReset the timer\r\nCancel the timer and trigger rollback immediately\r\nExamples\r\nThe following example shows how to cancel the timed rollback and revert to the saved configuration immediately:\r\nDevice(config)# archive\r\nDevice(config-archive)# path disk0:abc\r\nDevice# configure revert now\r\nRelated Commands\r\nCommand Description\r\narchive config Saves a copy of the current running configuration to the Cisco configuration archive.\r\nconfigure replace Replaces the current running configuration with a saved Cisco configuration file.\r\nmaximum\r\nSets the maximum number of archive files of the running configuration to be saved in the\r\nCisco configuration archive.\r\npath (config-archive)\r\nSpecifies the location and filename prefix for the files in the Cisco configuration archive.\r\nshow archive Displays information about the files saved in the Cisco configuration archive.\r\ntime-period\r\nSets the time increment for automatically saving an archive file of the current running\r\nconfiguration in the Cisco configuration archive.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 57 of 101\n\nconfigure terminal\r\nTo enter global configuration mode, use the configure terminal command in privileged EXEC mode.\r\nconfigure terminal\r\nCisco IOS Releases 12.3(14)T and Subsequent Releases:\r\nconfigure terminal [lock]\r\nCisco IOS Releases 12.2(33)SRC and Subsequent Releases:\r\nconfigure terminal [revert {timer minutes | idle minutes}]\r\nSyntax Description\r\nlock\r\n(Optional) Locks the running configuration into exclusive configuration mode for the duration\r\nof your configuration session. This keyword only functions if the configuration mode exclusive\r\ncommand was previously enabled.\r\nrevert\r\n(Optional) Sets the parameters for reverting the configuration if confirmation of the new\r\nconfiguration is not received.\r\ntimer\r\nminutes\r\nTime in minutes (1-120) for which to wait for confirmation.\r\nidle\r\nminutes\r\nIdle time in minutes (1-120) for which to wait for confirmation.\r\nCommand Modes\r\nPrivileged EXEC (#)\r\nCommand History\r\nRelease Modification\r\n10.0 This command was introduced.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 58 of 101\n\nRelease Modification\r\n12.3(14)T The lock keyword option was added.\r\n12.0(31)S This command was integrated into Cisco IOS Release 12.0(31)S.\r\n12.2(33)SRA This command was integrated into Cisco IOS Release 12.2(33)SRA.\r\n12.4(20)T\r\nThe revert keyword option was added, along with the timer parameters of idle and\r\nminutes .\r\n12.2(33)SB\r\nThis command was integrated into Cisco IOS Release 12.2(33)SB and\r\nimplemented on the Cisco 10000 series.\r\n12.2(33)SXI This command was integrated into Cisco IOS Release 12.2(33)SXI.\r\nCisco IOS XE Release\r\n3.9S\r\nThis command was integrated into Cisco IOS XE Release 3.9S.\r\nUsage Guidelines\r\nUse this command to enter global configuration mode. Note that commands in this mode are written to the\r\nrunning configuration file as soon as you enter them (using the Enter key/Carriage Return).\r\nAfter you enter the configure terminal command, the system prompt changes from \u003cdevice-name\u003e# to \u003cdevice-name\u003e(config)# , indicating that the device is in global configuration mode. To leave global configuration mode\r\nand return to privileged EXEC mode, type exit or press Ctrl-Z .\r\nTo view the changes to the configuration you have made, use the more system:running-config command or show\r\nrunning-config command in user EXEC or privileged EXEC mode.\r\nConfiguration Locking\r\nThe first user to enter the configure terminal lock command acquires the configuration lock (exclusive\r\nconfiguration mode).\r\nExamples\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 59 of 101\n\nThe following example shows how to enter global configuration mode and lock the Cisco software in exclusive\r\nmode:\r\nDevice(config)# configure terminal lock\r\nEnter configuration commands, one per line. End with CNTL/Z.\r\nDevice(config)#\r\nRelated Commands\r\nCommand Description\r\nboot config\r\nSpecifies the device and filename of the configuration file from which\r\nthe device configures itself during initialization (startup).\r\nconfiguration mode exclusive Enables locking of the configuration file for single user access.\r\ncopy running-config startup-config\r\nor\r\ncopy system:running-config\r\nnvram:startup-config\r\nSaves the running configuration as the startup configuration file.\r\nshow running-config\r\nor\r\nmore system:running-config\r\nDisplays the currently running configuration.\r\nconfreg\r\nTo change the configuration register settings while in ROM monitor mode, use the confreg command in ROM\r\nmonitor mode.\r\nconfreg [value]\r\nSyntax Description\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 60 of 101\n\nvalue\r\n(Optional) Hexadecimal value that represents the 16-bit configuration register value that you want to\r\nuse the next time the router is restarted. The value range is from 0x0 to 0xFFFF.\r\nCommand Default\r\nRefer to your platform documentation for the default configuration register value.\r\nCommand Modes\r\nROM monitor\r\nCommand History\r\nRelease Modification\r\n10.0 This command was introduced.\r\n12.2(33)SRA This command was integrated into Cisco IOS Release 12.2(33)SRA.\r\nUsage Guidelines\r\nNot all versions in the ROM monitor support this command. Refer to your platform documentation for more\r\ninformation on ROM monitor mode.\r\nIf you use this command without specifying the configuration register value, the router prompts for each bit of the\r\nconfiguration register.\r\nThe lowest four bits of the configuration register (bits 3, 2, 1, and 0) form the boot field. The boot field determines\r\nif the router boots manually, from ROM, or from Flash or the network.\r\nTo change the boot field value and leave all other bits set to their default values, follow these guidelines:\r\nIf you set the configuration register boot field value to 0x0, you must boot the operating system manually\r\nwith the boot command.\r\nIf you set the configuration register boot field value to 0x1, the router boots using the default ROM\r\nsoftware.\r\nIf you set the configuration register boot field to any value from 0x2 to 0xF, the router uses the boot field\r\nvalue to form a default boot filename for booting from a network server.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 61 of 101\n\nFor more information about the configuration register bit settings and default filenames, refer to the appropriate\r\nrouter hardware installation guide.\r\nExamples\r\nIn the following example, the configuration register is set to boot the system image from Flash memory:\r\nconfreg 0x210F\r\nIn the following example, no configuration value is entered, so the system prompts for each bit in the register:\r\nrommon 7 \u003e confreg\r\n \r\n Configuration Summary\r\nenabled are:\r\nconsole baud: 9600\r\nboot: the ROM Monitor\r\n \r\ndo you wish to change the configuration? y/n [n]: y\r\nenable \"diagnostic mode\"? y/n [n]: y\r\nenable \"use net in IP bcast address\"? y/n [n]:\r\nenable \"load rom after netboot fails\"? y/n [n]:\r\nenable \"use all zero broadcast\"? y/n [n]:\r\nenable \"break/abort has effect\"? y/n [n]:\r\nenable \"ignore system config info\"? y/n [n]:\r\nchange console baud rate? y/n [n]: y\r\nenter rate: 0 = 9600, 1 = 4800, 2 = 1200, 3 = 2400 [0]: 0\r\nchange the boot characteristics? y/n [n]: y\r\nenter to boot:\r\n 0 = ROM Monitor\r\n 1 = the boot helper image\r\n 2-15 = boot system\r\n [0]: 0\r\n \r\n Configuration Summary\r\nenabled are:\r\ndiagnostic mode\r\nconsole baud: 9600\r\nboot: the ROM Monitor\r\n \r\ndo you wish to change the configuration? y/n [n]:\r\nYou must reset or power cycle for new config to take effect.\r\nrommon 8\u003e\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 62 of 101\n\ncontinue (ROM monitor)\r\nTo return to EXEC mode from ROM monitor mode, use the continue command in ROM monitor mode.\r\ncontinue\r\nSyntax Description\r\nThis command has no arguments or keywords.\r\nCommand Default\r\nNo default behavior or values.\r\nCommand Modes\r\nROM monitor\r\nCommand History\r\nRelease Modification\r\n11.0 This command was introduced.\r\n12.2(33)SRA This command was integrated into Cisco IOS Release 12.2(33)SRA.\r\nUsage Guidelines\r\nUse this command to return to EXEC mode from ROM monitor mode, to use the system image instead of\r\nreloading. On older platforms, the angle bracket (\u003c \u003e) indicates that the router is in ROM monitor mode. On\r\nnewer platforms, rommon number\u003e is the default ROM monitor prompt. Typically, the router is in ROM monitor\r\nmode when you manually load a system image or perform diagnostic tests. Otherwise, the router will most likely\r\nnever be in this mode.\r\nCaution\r\nWhile in ROM monitor mode, the Cisco IOS system software is suspended until you issue either a\r\nreset or the continue command.\r\nExamples\r\nIn the following example, the continue command switches the router from ROM monitor to EXEC mode:\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 63 of 101\n\n\u003e continue\r\nRouter#\r\nRelated Commands\r\nCommand Description\r\nboot Boots the router manually.\r\ncopy\r\nTo copy any file from a source to a destination, use the copy command in privileged EXEC or diagnostic mode.\r\nPlease note that the copy command does not yet support the handling of wildcards in order to specify multiple\r\nfiles as part of source-url.\r\ncopy [/erase] [/ verify | /noverify] source-url destination-url\r\nSyntax Description\r\n/erase\r\n(Optional) Erases the destination file system before copying.\r\nNote\r\n \r\nThis option is typically provided on platforms with limited memory to allow for\r\nan easy way to clear local flash memory space.\r\n/verify\r\n(Optional) Verifies the digital signature of the destination file. If verification fails, the file is\r\ndeleted from the destination file system. This option applies to Cisco IOS software image\r\nfiles only.\r\n/noverify\r\n(Optional) If the file being copied is an image file, this keyword disables the automatic image\r\nverification that occurs after an image is copied.\r\nNote\r\n \r\nThis keyword is often issued if the file verify auto command is enabled, which\r\nautomatically verifies the digital signature of all images that are copied.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 64 of 101\n\nsource-url\r\nThe location URL (or alias) of the source file or directory to be copied. The source can be\r\neither local or remote, depending upon whether the file is being downloaded or uploaded.\r\ndestination-urlThe destination URL (or alias) of the copied file or directory. The destination can be either\r\nlocal or remote, depending upon whether the file is being downloaded or uploaded.\r\nThe exact format of the source and destination URLs varies according to the file or directory location. You may\r\nenter either an alias keyword for a particular file or a filename that follows the standard Cisco IOS file system\r\nsyntax (filesystem :[/filepath ][/filename ]).\r\nThe table below shows two keyword shortcuts to URLs.\r\nTable 1. Common Keyword Aliases to URLs\r\nKeyword Source or Destination\r\nrunning-config\r\n(Optional) Keyword alias for the system:running-config URL. The system:running-config\r\nkeyword represents the current running configuration file. This keyword does not work in more\r\nand show file EXEC command syntaxes.\r\nstartup-config\r\n(Optional) Keyword alias for the nvram:startup-config URL. The nvram:startup-config keyword\r\nrepresents the configuration file used during initialization (startup). This file is contained in\r\nNVRAM for all platforms except the Cisco 7000 family, which uses the CONFIG_FILE\r\nenvironment variable to specify the startup configuration. The Cisco 4500 series cannot use the\r\ncopy running-config startup-config command. This keyword does not work in more and show\r\nfile EXEC command syntaxes.\r\nThe following tables list URL prefix keywords by file system type. The available file systems will vary by\r\nplatform. If you do not specify a URL prefix keyword, the router looks for a file in the current directory.\r\nThe table below lists URL prefix keywords for Special (opaque) file systems.\r\nTable 2. URL Prefix Keywords for Special File Systems\r\nKeyword Source or Destination\r\ncns: Source URL for Cisco Networking Services files.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 65 of 101\n\nKeyword Source or Destination\r\nflh: Source URL for flash load helper log files.\r\nlogging Source URL which copies messages from the logging buffer to a file.\r\nmodem: Destination URL for loading modem firmware on to supported networking devices.\r\nnull: Null destination for copies or files. You can copy a remote file to null to determine its size.\r\nnvram: Router NVRAM. You can copy the startup configuration to NVRAM or from NVRAM.\r\nobfl: Source or destination URL for Onboard Failure Logging files.\r\nstby-nvram:Router NVRAM on the standby hardware. You can copy the startup configuration to NVRAM\r\nor from NVRAM.\r\nstby-obfl: Source or destination URL for Onboard Failure Logging files on the standby hardware.\r\nsystem: Source or destination URL for system memory, which includes the running configuration.\r\ntar: Source URL for the archive file system.\r\ntmpsys: Source or destination URL for the temporary system files.\r\nxmodem: Source or destination for a file from a network machine that uses the Xmodem protocol.\r\nymodem: Source or destination for a file from a network machine that uses the Ymodem protocol.\r\nThe table belows lists URL prefix keywords for remote file systems.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 66 of 101\n\nTable 3. URL Prefix Keywords for Remote File Systems\r\nKeyword Source or Destination\r\nftp:\r\nSource or destination URL for FTP network server. The syntax for this alias is as follows:ftp:\r\n[[[//username [:password]@]location]/directory]/filename.\r\nhttp://\r\nSource or destination URL for an HTTP server (also called a web server). The syntax for this\r\nalias is as follows: http:// [[username :password ]@]{hostname | host-ip }[/ filepath ]/ filename\r\nhttps://\r\nSource or destination URL for a Secure HTTP (HTTPS) server. HTTPS uses Secure Socket\r\nLayer (SSL) encryption. The syntax for this alias is as follows:https:// [[username :password ]@]\r\n{hostname | host-ip }[/ filepath ]/ filename\r\nrcp:\r\nSource or destination URL for a remote copy protocol (rcp) network server. The syntax for this\r\nalias is as follows:rcp: [[[//username@ ] location]/directory]/filename\r\nscp:\r\nSource or destination URL for a network server that supports Secure Shell (SSH) and accepts\r\ncopies of files using the secure copy protocol (scp). The syntax for this alias is as follows:scp://\r\nusername @location [/directory ][/filename ]\r\ntftp:\r\nSource or destination URL for a TFTP network server. The syntax for this alias is as follows:tftp:\r\n[[//location]/directory]/filename.\r\nThe table below lists URL prefix keywords for local writable storage file systems.\r\nTable 4. URL Prefix Keywords for Local Writable Storage File Systems\r\nAlias Source or Destination\r\nbootflash: Source or destination URL for boot flash memory.\r\ndisk0: and\r\ndisk1:\r\nSource or destination URL of disk-based media.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 67 of 101\n\nAlias Source or Destination\r\nflash:\r\nSource or destination URL for flash memory. This alias is available on all platforms. For\r\nplatforms that lack a flash: device, note that flash: is aliased to slot0:, allowing you to refer\r\nto the main flash memory storage area on all platforms.\r\nharddisk: Source or destination URL of the active harddisk file system.\r\nslavebootflash:\r\nSource or destination URL for internal flash memory on the secondary RSP card of a\r\nrouter configured for HSA.\r\nslaveram: NVRAM on a secondary RSP card of a router configured for HSA.\r\nslaveslot0:\r\nSource or destination URL of the first Personal Computer Memory Card International\r\nAssociation (PCMCIA) card on a secondary RSP card of a router configured for HSA.\r\nslaveslot1:\r\nSource or destination URL of the second PCMCIA slot on a secondary RSP card of a\r\nrouter configured for HSA.\r\nslot0: Source or destination URL of the first PCMCIA flash memory card.\r\nslot1: Source or destination URL of the second PCMCIA flash memory card.\r\nstby-bootflash: Source or destination URL for boot flash memory in standby RP.\r\nstby-harddisk: Source or destination URL for the standby harddisk.\r\nstby-usb [ 0-1 ]\r\n:\r\nSource or destination URL for the Universal Serial Bus (USB) flash drive that has been\r\nplugged into the router and is located on the standby RP.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 68 of 101\n\nAlias Source or Destination\r\nusb [ 0-1 ] :\r\nSource or destination URL for the Universal Serial Bus (USB) flash drive that has been\r\nplugged into the router and is located on the active RP.\r\nusbflash 0 9 :\r\nSource or destination URL for the Universal Serial Bus (USB) flash drive that has been\r\nplugged into the router.\r\nusbtoken [0 9 ]\r\n:\r\nSource or destination URL for the USB eToken that has been plugged into the router.\r\nCommand Modes\r\nPrivileged EXEC (#)\r\nDiagnostic (diag)\r\nCommand History\r\nRelease Modification\r\n11.3T This command was introduced.\r\n12.3(2)T\r\nThe http:// and https:// keywords were added as supported remote source\r\nlocations (file system URL prefixes) for files.\r\nThis command was enhanced to support copying files to servers that support\r\nSSH and the scp.\r\n12.2(14)S This command was integrated into Cisco IOS Release 12.2(14)S.\r\n12.2(18)S The /verify and /noverify keywords were added.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 69 of 101\n\nRelease Modification\r\n12.0(26)S\r\nThe /verify and /noverify keywords were integrated into Cisco IOS Release\r\n12.0(26)S.\r\n12.3(4)T\r\nThe /verify and /noverify keywords were integrated into Cisco IOS Release\r\n12.3(4)T.\r\n12.3(7)T The http:// and https:// keywords were enhanced to support file uploads.\r\n12.3(14)T The usbflash 0 9 : and usbtoken 0 9 : keywords were added to support USB storage.\r\n12.2(28)SB This command was integrated into Cisco IOS Release 12.2(28)SB.\r\n12.2(25)SG This command was integrated into Cisco IOS Release 12.2(25)SG.\r\n12.4(11)T This command was integrated into the Cisco 7200VXR NPE-G2 platform.\r\n12.2(33)SXH This command was integrated into Cisco IOS Release 12.2(33)SXH.\r\nCisco IOS XE\r\nRelease 2.1\r\nThe Cisco ASR1000 series routers became available, and introduced the copy\r\ncommand in diagnostic mode.\r\nCisco IOS XE\r\nRelease 3.9S\r\nThe command was integrated into Cisco IOS XE Release 3.9S.\r\nUsage Guidelines\r\nThe fundamental function of the copy command is to allow you to copy a file (such as a system image or\r\nconfiguration file) from one location to another location. The source and destination for the file is specified using\r\na Cisco IOS File System URL, which allows you to specify any supported local or remote file location. The file\r\nsystem being used (such as a local memory source, or a remote server) dictates the syntax used in the command.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 70 of 101\n\nNote\r\nThe copy command copies only one file at a time. The command does not allow you to copy multiple\r\nfiles.\r\nYou can enter on the command line all necessary source- and destination-URL information and the username and\r\npassword to use, or you can enter the copy command and have the router prompt you for any missing information.\r\nFor local file systems, two commonly used aliases exist for the system:running-config and nvram:startup-config\r\nfiles; these aliases are running-config and startup-config , respectively.\r\nAny software that supports RFC1738 does not allow user name, path, or filename with pattern %xy, where (where\r\nx and y are any two hexa values 0-f, 0-F)\r\nTimesaver\r\nAliases are used to reduce the amount of typing you need to perform. For example, it is easier\r\nto type copy run start (the abbreviated form of the copy running-config startup-config\r\ncommand) than it is to type copy system:r nvram:s (the abbreviated form of the copy\r\nsystem:running-config nvram:startup-config command). These aliases also allow you to\r\ncontinue using some of the common commands used in previous versions of Cisco IOS\r\nsoftware.\r\nNote\r\nWhen authorization is turned on for the copy (filesystem:[/filepath][/filename]) running-config\r\ncommand, only the copy command is authorized. The individual commands available in the copied\r\nfile are not authorized.\r\nThe entire copying process may take several minutes and differs from protocol to protocol and from network to\r\nnetwork.\r\nThe colon is required after the file system URL prefix keywords (such as flash ). In some cases, file system\r\nprefixes that did not require colons in earlier software releases are allowed for backwards compatibility, but use of\r\nthe colon is recommended.\r\nIn the URL syntax for ftp: , http: , https: , rcp: , scp: and tftp: , the location is either an IP address or a host name.\r\nThe filename is specified relative to the directory used for file transfers.\r\nThe following sections contain usage guidelines for the following topics:\r\nUnderstanding Invalid Combinations of Source and Destination\r\nSome invalid combinations of source and destination exist. Specifically, you cannot copy:\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 71 of 101\n\nFrom a running configuration to a running configuration\r\nFrom a startup configuration to a startup configuration\r\nFrom a device to the same device (for example, the copy flash: flash: command is invalid)\r\nUnderstanding Character Descriptions\r\nThe table below describes the characters that you may see during processing of the copy command.\r\nTable 5. copy Character Descriptions\r\nCharacter Description\r\n!\r\nFor network transfers, an exclamation point indicates that the copy process is taking place.\r\nEach exclamation point indicates the successful transfer of ten packets (512 bytes each).\r\n.\r\nFor network transfers, a period indicates that the copy process timed out. Many periods in a row\r\ntypically mean that the copy process may fail.\r\nO\r\nFor network transfers, an uppercase O indicates that a packet was received out of order and the\r\ncopy process may fail.\r\ne For flash erasures, a lowercase e indicates that a device is being erased.\r\nE An uppercase E indicates an error. The copy process may fail.\r\nV A series of uppercase Vs indicates the progress during the verification of the image checksum.\r\nUnderstanding Partitions\r\nYou cannot copy an image or configuration file to a flash partition from which you are currently running. For\r\nexample, if partition 1 is running the current system image, copy the configuration file or image to partition 2.\r\nOtherwise, the copy operation will fail.\r\nYou can identify the available flash partitions by entering the show file system EXEC command.\r\nUsing rcp\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 72 of 101\n\nThe rcp requires a client to send a remote username upon each rcp request to a server. When you copy a\r\nconfiguration file or image between the router and a server using rcp, the Cisco IOS software sends the first valid\r\nusername it encounters in the following sequence:\r\n1. The remote username specified in the copy command, if a username is specified.\r\n2. The username set by the ip rcmd remote-username global configuration command, if the command is\r\nconfigured.\r\n3. The remote username associated with the current tty (terminal) process. For example, if the user is\r\nconnected to the router through Telnet and was authenticated through the username command, the router\r\nsoftware sends the Telnet username as the remote username.\r\n4. The router host name.\r\nFor the rcp copy request to process, an account must be defined on the network server for the remote username. If\r\nthe network administrator of the destination server did not establish an account for the remote username, this\r\ncommand will not run. If the server has a directory structure, the configuration file or image is written to or copied\r\nfrom the directory associated with the remote username on the server. For example, if the system image resides in\r\nthe home directory of a user on the server, specify that username as the remote username.\r\nIf you are writing to the server, the rcp server must be properly configured to accept the rcp write request from the\r\nuser on the router. For UNIX systems, add an entry to the .rhosts file for the remote user on the rcp server.\r\nSuppose the router contains the following configuration lines:\r\nhostname Rtr1\r\nip rcmd remote-username User0\r\nIf the router IP address translates to Router1.company.com, then the .rhosts file for User0 on the rcp server should\r\ncontain the following line:\r\nRouter1.company.com Rtr1\r\nRefer to the documentation for your rcp server for more details.\r\nIf you are using a personal computer as a file server, the computer must support the remote shell protocol (rsh).\r\nUsing FTP\r\nThe FTP protocol requires a client to send a username and password with each FTP request to a remote FTP\r\nserver. Use the ip ftp username and ip ftp password global configuration commands to specify a default username\r\nand password for all copy operations to or from an FTP server. Include the username in the copy command syntax\r\nif you want to specify a username for that copy operation only.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 73 of 101\n\nWhen you copy a file from the router to a server using FTP, the Cisco IOS software sends the first valid username\r\nthat it encounters in the following sequence:\r\n1. The username specified in the copy command, if a username is specified.\r\n2. The username set by the ip ftp username command, if the command is configured.\r\n3. Anonymous.\r\nThe router sends the first valid password in the following list:\r\n1. The password specified in the copy command, if a password is specified.\r\n2. The password set by the ip ftp password command, if the command is configured.\r\n3. The router forms a password username @routername .domain . The variable username is the username\r\nassociated with the current session, routername is the configured host name, and domain is the domain of\r\nthe router.\r\nThe username and password must be associated with an account on the FTP server. If you are writing to the server,\r\nthe FTP server must be properly configured to accept the FTP write request from the user on the router.\r\nNote\r\nThe Syslog message will display 'xxxx' in place of the password entered in the syntax of the copy\r\n{ftp: } command.\r\nIf the server has a directory structure, the configuration file or image is written to or copied from the directory\r\nassociated with the username on the server. For example, if the system image resides in the home directory of a\r\nuser on the server, specify that username as the remote username.\r\nRefer to the documentation for your FTP server for details on setting up the server.\r\nUsing HTTP or HTTPS\r\nCopying a file to or from a remote HTTP or HTTPS server, to or from a local file system, is performed using the\r\nembedded Secure HTTP client that is integrated in Cisco IOS software. The HTTP client is enabled by default.\r\nDownloading files from a remote HTTP or HTTPS server is performed using the HTTP client integrated in Cisco\r\nIOS software.\r\nIf a username and password are not specified in the copy command syntax, the system uses the default HTTP\r\nclient username and password, if configured.\r\nWhen you copy a file from a remote HTTP or HTTPS server, the Cisco IOS software sends the first valid\r\nusername that it encounters in the following sequence:\r\n1. The username specified in the copy command, if a username is specified.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 74 of 101\n\n2. The username set by the ip http client username command, if the command is configured.\r\n3. Anonymous.\r\nThe router sends the first valid password in the following list:\r\n1. The password specified in the copy command, if a password is specified.\r\n2. The password set by the ip http client password command, if the command is configured.\r\n3. The router forms the password username @routername .domain . The variable username is the username\r\nassociated with the current session, routername is the configured host name, and domain is the domain of\r\nthe router.\r\nStoring Images on Servers\r\nUse the copy flash: destination-url command (for example, copy flash: tftp: ) to copy a system image or boot\r\nimage from flash memory to a network server. You can use the copy of the image as a backup copy. Also, you can\r\nalso use the image backup file to verify that the image in flash memory is the same as that in the original file.\r\nCopying from a Server to Flash Memory\r\nUse the copy destination-url flash: command (for example, copy tftp: flash: ) to copy an image from a server to\r\nflash memory.\r\nOn Class B file system platforms, the system provides an option to erase existing flash memory before writing\r\nonto it.\r\nNote\r\nVerify the image in flash memory before booting the image.\r\nVerifying Images\r\nWhen copying a new image to your router, you should confirm that the image was not corrupted during the copy\r\nprocess. You can verify the integrity of the image in any of the following ways:\r\nDepending on the destination file system type, a checksum for the image file may be displayed when the\r\ncopy command completes. You can verify this checksum by comparing it to the checksum value provided\r\nfor your image file on Cisco.com.\r\nCaution\r\nIf the checksum values do not match, do not reboot the router. Instead, reissue the copy command\r\nand compare the checksums again. If the checksum is repeatedly wrong, copy the original image\r\nback into flash memory before you reboot the router from flash memory. If you have a corrupted\r\nimage in flash memory and try to boot from flash memory, the router will start the system image\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 75 of 101\n\ncontained in ROM (assuming booting from a network server is not configured). If ROM does not\r\ncontain a fully functional system image, the router might not function and will need to be\r\nreconfigured through a direct console port connection.\r\nUse the /verify keyword.\r\nEnable automatic image verification by default by issuing the file verify auto command. This command\r\nwill automatically check the integrity of each file that is copied via the copy command (without specifying\r\nthe /verify option) to the router unless the /noverify keyword is specified.\r\nUse the UNIX 'diff' command. This method can also be applied to file types other than Cisco IOS images.\r\nIf you suspect that a file is corrupted, copy the suspect file and the original file to a UNIX server. (The file\r\nnames may need to be modified if you try to save the files in the same directory.) Then run the UNIX 'diff'\r\ncommand on the two files. If there is no difference, then the file has not been corrupted.\r\nCopying a Configuration File from a Server to the Running Configuration\r\nUse the copy {ftp: | rcp: | scp: | tftp: running-config command to load a configuration file from a network server to\r\nthe running configuration of the router. (Note that running-config is the alias for the system:running-config\r\nkeyword.) The configuration will be added to the running configuration as if the commands were typed in the\r\ncommand-line interface (CLI). Thus, the resulting configuration file will be a combination of the previous running\r\nconfiguration and the loaded configuration file, with the loaded configuration file having precedence.\r\nYou can copy either a host configuration file or a network configuration file. Accept the default value of host to\r\ncopy and load a host configuration file containing commands that apply to one network server in particular. Enter\r\nnetwork to copy and load a network configuration file containing commands that apply to all network servers on a\r\nnetwork.\r\nCopying a Configuration File from a Server to the Startup Configuration\r\nUse the copy {ftp: | rcp: | scp: | tftp: } nvram:startup-config command to copy a configuration file from a network\r\nserver to the router startup configuration. These commands replace the startup configuration file with the copied\r\nconfiguration file.\r\nStoring the Running or Startup Configuration on a Server\r\nUse the copy system:running-config {ftp: | rcp: | scp: | tftp: } command to copy the current configuration file to a\r\nnetwork server using FTP, rcp, scp, or TFTP. Use the copy nvram:startup-config {ftp: | rcp: | scp: | tftp: }\r\ncommand to copy the startup configuration file to a network server.\r\nThe configuration file copy can serve as a backup copy.\r\nSaving the Running Configuration to the Startup Configuration\r\nUse the copy system:running-config nvram:startup-config command to copy the running configuration to the\r\nstartup configuration.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 76 of 101\n\nNote\r\nSome specific commands might not get saved to NVRAM. You will need to enter these commands\r\nagain if you reboot the machine. These commands are noted in the documentation. We recommend\r\nthat you keep a listing of these settings so you can quickly reconfigure your router after rebooting.\r\nIf you issue the copy system:running-config nvram:startup-config command from a bootstrap system image, a\r\nwarning will instruct you to indicate whether you want your previous NVRAM configuration to be overwritten\r\nand configuration commands to be lost. This warning does not appear if NVRAM contains an invalid\r\nconfiguration or if the previous configuration in NVRAM was generated by a bootstrap system image.\r\nOn all platforms except Class A file system platforms, the copy system:running-config nvram:startup-config\r\ncommand copies the currently running configuration to NVRAM.\r\nOn the Class A flash file system platforms, the copy system:running-config nvram:startup-config command copies\r\nthe currently running configuration to the location specified by the CONFIG_FILE environment variable. This\r\nvariable specifies the device and configuration file used for initialization. When the CONFIG_FILE environment\r\nvariable points to NVRAM or when this variable does not exist (such as at first-time startup), the software writes\r\nthe current configuration to NVRAM. If the current configuration is too large for NVRAM, the software displays\r\na message and stops executing the command.\r\nWhen the CONFIG_FILE environment variable specifies a valid device other than nvram: (that is, flash: ,\r\nbootflash: , slot0: , or slot1: ), the software writes the current configuration to the specified device and filename,\r\nand stores a distilled version of the configuration in NVRAM. A distilled version is one that does not contain\r\naccess list information. If NVRAM already contains a copy of a complete configuration, the router prompts you to\r\nconfirm the copy.\r\nUsing CONFIG_FILE, BOOT, and BOOTLDR Environment Variables\r\nFor the Class A flash file system platforms, specifications are as follows:\r\nThe CONFIG_FILE environment variable specifies the configuration file used during router initialization.\r\nThe BOOT environment variable specifies a list of bootable images on various devices.\r\nThe BOOTLDR environment variable specifies the flash device and filename containing the rxboot image\r\nthat ROM uses for booting.\r\nCisco 3600 routers do not use a dedicated boot helper image (rxboot), which many other routers use to help\r\nwith the boot process. Instead, the BOOTLDR ROM monitor environment variable identifies the flash\r\nmemory device and filename that are used as the boot helper; the default is the first system image in flash\r\nmemory.\r\nTo view the contents of environment variables, use the show bootvar EXEC command. To modify the\r\nCONFIG_FILE environment variable, use the boot config global configuration command. To modify the\r\nBOOTLDR environment variable, use the boot bootldr global configuration command. To modify the BOOT\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 77 of 101\n\nenvironment variable, use the boot system global configuration command. To save your modifications, use the\r\ncopy system:running-config nvram:startup-config command.\r\nWhen the destination of a copy command is specified by the CONFIG_FILE or BOOTLDR environment variable,\r\nthe router prompts you for confirmation before proceeding with the copy. When the destination is the only valid\r\nimage in the BOOT environment variable, the router also prompts you for confirmation before proceeding with\r\nthe copy.\r\nUsing the Copy Command with the Dual RSP Feature\r\nThe Dual RSP feature allows you to install two Route Switch Processor (RSP) cards in a single router on the\r\nCisco 7507 and Cisco 7513 platforms.\r\nOn a Cisco 7507 or Cisco 7513 router configured for Dual RSPs, if you copy a file to nvram:startup-configuration\r\nwith automatic synchronization disabled, the system prompts whether you also want to copy the file to the\r\nsecondary startup configuration. The default answer is yes . If automatic synchronization is enabled, the system\r\nautomatically copies the file to the secondary startup configuration each time you use a copy command with\r\nnvram:startup-configuration as the destination.\r\nUsing the copy command with the ASR1000 Series Routers\r\nThe copy command is available in both privileged EXEC and diagnostic mode on the Cisco ASR1000 series\r\nrouters. Because the copy command is available in diagnostic mode, it can be used to copy all types of files\r\nbetween directories and remote locations even in the event of an IOS failure.\r\nExamples\r\nThe following examples illustrate uses of the copy command:\r\nExamples\r\nThe following example shows how to specify image verification before copying an image:\r\nRouter# copy /verify tftp://10.1.1.1/cisco/c7200-js-mz disk0:\r\nDestination filename [c7200-js-mz]?\r\nAccessing tftp://10.1.1.1/cisco/c7200-js-mz...\r\nLoading cisco/c7200-js-mz from 10.1.1.1 (via FastEthernet0/0):!!!!!!!!!!!!!!!!!!!!\r\n!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!\r\n!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!\r\n[OK - 19879944 bytes]\r\n19879944 bytes copied in 108.632 secs (183003 bytes/sec)\r\nVerifying file integrity of disk0:/c7200-js-mz ...................................................\r\n...................................................................................................\r\n...................................................................................................\r\n.......................................Done!\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 78 of 101\n\nEmbedded Hash MD5 :CFA258948C4ECE52085DCF428A426DCD\r\nComputed Hash MD5 :CFA258948C4ECE52085DCF428A426DCD\r\nCCO Hash MD5 :44A7B9BDDD9638128C35528466318183\r\nSignature Verified\r\nExamples\r\nThe following examples use a copy rcp: , copy tftp: , or copy ftp: command to copy an image file from a server to\r\nflash memory:\r\nExamples\r\nThe following example copies a system image named file1 from the remote rcp server with an IP address of\r\n172.16.101.101 to flash memory. On Class B file system platforms, the Cisco IOS software allows you to first\r\nerase the contents of flash memory to ensure that enough flash memory is available to accommodate the system\r\nimage.\r\nRouter#\r\ncopy rcp://netadmin@172.16.101.101/file1 flash:file1\r\nDestination file name [file1]?\r\nAccessing file 'file1' on 172.16.101.101...\r\nLoading file1 from 172.16.101.101 (via Ethernet0): ! [OK]\r\nErase flash device before writing? [confirm]\r\nFlash contains files. Are you sure you want to erase? [confirm]\r\nCopy 'file1' from server\r\n as 'file1' into Flash WITH erase? [yes/no] yes\r\nErasing device... eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee...erased\r\nLoading file1 from 172.16.101.101 (via Ethernet0): !\r\n[OK - 984/8388608 bytes]\r\nVerifying checksum... OK (0x14B3)\r\nFlash copy took 0:00:01 [hh:mm:ss]\r\nExamples\r\nThe following example copies a system image into a partition of flash memory. The system will prompt for a\r\npartition number only if there are two or more read/write partitions or one read-only and one read/write partition\r\nand dual flash bank support in boot ROMs. If the partition entered is not valid, the process terminates. You can\r\nenter a partition number, a question mark (? ) for a directory display of all partitions, or a question mark and a\r\nnumber (? number ) for directory display of a particular partition. The default is the first read/write partition. In\r\nthis case, the partition is read-only and has dual flash bank support in boot ROM, so the system uses flash Load\r\nHelper.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 79 of 101\n\nRouter# copy tftp: flash:\r\n \r\nSystem flash partition information:\r\nPartition Size Used Free Bank-Size State Copy-Mode\r\n 1 4096K 2048K 2048K 2048K Read Only RXBOOT-FLH\r\n 2 4096K 2048K 2048K 2048K Read/Write Direct\r\n[Type ?\u003cno\u003e for partition directory; ? for full directory; q to abort]\r\nWhich partition? [default = 2]\r\n **** NOTICE ****\r\nFlash load helper v1.0\r\nThis process will accept the copy options and then terminate\r\nthe current system image to use the ROM based image for the copy.\r\nRouting functionality will not be available during that time.\r\nIf you are logged in via telnet, this connection will terminate.\r\nUsers with console access can see the results of the copy operation.\r\n ---- ******** ----\r\nProceed? [confirm]\r\nSystem flash directory, partition 1:\r\nFile Length Name/status\r\n 1 3459720 master/igs-bfpx.100-4.3\r\n[3459784 bytes used, 734520 available, 4194304 total]\r\nAddress or name of remote host [255.255.255.255]? 172.16.1.1\r\n \r\nSource file name? master/igs-bfpx-100.4.3\r\n \r\nDestination file name [default = source name]?\r\nLoading master/igs-bfpx.100-4.3 from 172.16.1.111: !\r\nErase flash device before writing? [confirm]\r\nFlash contains files. Are you sure? [confirm]\r\nCopy 'master/igs-bfpx.100-4.3' from TFTP server\r\nas 'master/igs-bfpx.100-4.3' into Flash WITH erase? [yes/no] yes\r\n \r\nExamples\r\nThe following example copies the file c3600-i-mz from the rcp server at IP address 172.23.1.129 to the flash\r\nmemory card in slot 0 of a Cisco 3600 series router, which has only one partition. As the operation progresses, the\r\nCisco IOS software prompts you to erase the files on the flash memory PC card to accommodate the incoming\r\nfile. This entire operation takes 18 seconds to perform, as indicated at the end of the example.\r\nRouter# copy rcp: slot0:\r\nPCMCIA Slot0 flash\r\nPartition Size Used Free Bank-Size State Copy Mode\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 80 of 101\n\n1 4096K 3068K 1027K 4096K Read/Write Direct\r\n 2 4096K 1671K 2424K 4096K Read/Write Direct\r\n 3 4096K 0K 4095K 4096K Read/Write Direct\r\n 4 4096K 3825K 270K 4096K Read/Write Direct\r\n[Type ?\u003cno\u003e for partition directory; ? for full directory; q to abort]\r\nWhich partition? [default = 1]\r\nPCMCIA Slot0 flash directory, partition 1:\r\nFile Length Name/status\r\n 1 3142288 c3600-j-mz.test\r\n[3142352 bytes used, 1051952 available, 4194304 total]\r\nAddress or name of remote host [172.23.1.129]?\r\nSource file name? /tftpboot/images/c3600-i-mz\r\n \r\nDestination file name [/tftpboot/images/c3600-i-mz]?\r\nAccessing file '/tftpboot/images/c3600-i-mz' on 172.23.1.129...\r\nConnected to 172.23.1.129\r\nLoading 1711088 byte file c3600-i-mz: ! [OK]\r\nErase flash device before writing? [confirm]\r\nFlash contains files. Are you sure you want to erase? [confirm]\r\nCopy '/tftpboot/images/c3600-i-mz' from server\r\n as '/tftpboot/images/c3600-i-mz' into Flash WITH erase? [yes/no]\r\nyes\r\n \r\nErasing device... eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee ...erased\r\nConnected to 172.23.1.129\r\nLoading 1711088 byte file c3600-i-mz: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!\r\n!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!\r\n!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!\r\nVerifying checksum... OK (0xF89A)\r\nFlash device copy took 00:00:18 [hh:mm:ss]\r\nExamples\r\nThe following examples use copy commands to copy image files to a server for storage:\r\nExamples\r\nThe following example copies a system image from flash Memory to an rcp server using the default remote\r\nusername. Because the rcp server address and filename are not included in the command, the router prompts for it.\r\nRouter#\r\ncopy flash: rcp:\r\nIP address of remote host [255.255.255.255]? 172.16.13.110\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 81 of 101\n\nName of file to copy? gsxx\r\nwriting gsxx - copy complete\r\nExamples\r\nThe following example shows how to use scp to copy a system image from flash memory to a server that supports\r\nSSH:\r\nRouter# copy flash:c4500-ik2s-mz.scp scp://user1@host1/\r\n \r\nAddress or name of remote host [host1]?\r\nDestination username [user1]?\r\nDestination filename [c4500-ik2s-mz.scp]?\r\nWriting c4500-ik2s-mz.scp\r\nPassword:\r\n!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!\r\nBefore you can use the server-side functionality, SSH, authentication, and authorization must be properly\r\nconfigured so the router can determine whether a user is at the right privilege level. The scp server-side\r\nfunctionality is configured with the ip scp server enable command.\r\nExamples\r\nThe following example copies an image from a particular partition of flash memory to an rcp server using a\r\nremote username of netadmin1.\r\nThe system will prompt if there are two or more partitions. If the partition entered is not valid, the process\r\nterminates. You have the option to enter a partition number, a question mark (? ) for a directory display of all\r\npartitions, or a question mark and a number (? number ) for a directory display of a particular partition. The\r\ndefault is the first partition.\r\nRouter# configure terminal\r\nRouter# ip rcmd remote-username netadmin1\r\nRouter# end\r\nRouter# copy flash: rcp:\r\nSystem flash partition information:\r\nPartition Size Used Free Bank-Size State Copy-Mode\r\n 1 4096K 2048K 2048K 2048K Read Only RXBOOT-FLH\r\n 2 4096K 2048K 2048K 2048K Read/Write Direct\r\n[Type ?\u003cnumber\u003e for partition directory; ? for full directory; q to abort]\r\nWhich partition? [1] 2\r\nSystem flash directory, partition 2:\r\nFile Length Name/status\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 82 of 101\n\n1 3459720 master/igs-bfpx.100-4.3\r\n[3459784 bytes used, 734520 available, 4194304 total]\r\nAddress or name of remote host [ABC.CISCO.COM]?\r\nSource file name? master/igs-bfpx.100-4.3\r\nDestination file name [master/igs-bfpx.100-4.3]?\r\nVerifying checksum for 'master/igs-bfpx.100-4.3' (file # 1)... OK\r\nCopy 'master/igs-bfpx.100-4.3' from Flash to server\r\nas 'master/igs-bfpx.100-4.3'? [yes/no] yes\r\n!!!!...\r\nUpload to server done\r\nFlash copy took 0:00:00 [hh:mm:ss]\r\nExamples\r\nThe following example copies the file c3600-i-mz from partition 1 of the flash memory card in slot 0 to an FTP\r\nserver at IP address 172.23.1.129:\r\nRouter# show slot0: partition 1\r\nPCMCIA Slot0 flash directory, partition 1:\r\nFile Length Name/status\r\n 1 1711088 c3600-i-mz\r\n[1711152 bytes used, 2483152 available, 4194304 total]\r\nRouter# copy slot0:1:c3600-i-mz ftp://myuser:mypass@172.23.1.129/c3600-i-mz\r\nVerifying checksum for '/tftpboot/cisco_rules/c3600-i-mz' (file # 1)... OK\r\nCopy '/tftpboot/cisco_rules/c3600-i-mz' from Flash to server\r\n as 'c3700-i-mz'? [yes/no] yes\r\n!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!\r\n!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!\r\n!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!\r\nUpload to server done\r\nFlash device copy took 00:00:23 [hh:mm:ss]\r\nExamples\r\nThe following example copies an image from boot flash memory to a TFTP server:\r\nRouter#\r\ncopy bootflash:file1 tftp://192.168.117.23/file1\r\nVerifying checksum for 'file1' (file # 1)... OK\r\nCopy 'file1' from Flash to server\r\n as 'file1'? [yes/no]y\r\n!!!!...\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 83 of 101\n\nUpload to server done\r\nFlash copy took 0:00:00 [hh:mm:ss]\r\nExamples\r\nThe following example copies and runs a configuration filename host1-confg from the netadmin1 directory on the\r\nremote server with an IP address of 172.16.101.101:\r\nRouter#\r\ncopy rcp://netadmin1@172.16.101.101/host1-confg system:running-config\r\nConfigure using host1-confg from 172.16.101.101? [confirm]\r\nConnected to 172.16.101.101\r\nLoading 1112 byte file host1-confg:![OK]\r\nRouter#\r\n%SYS-5-CONFIG: Configured from host1-config by rcp from 172.16.101.101\r\nExamples\r\nThe following example copies a configuration file host2-confg from a remote FTP server to the startup\r\nconfiguration. The IP address is 172.16.101.101, the remote username is netadmin1, and the remote password is\r\nftppass.\r\nRouter#\r\ncopy ftp://netadmin1:ftppass@172.16.101.101/host2-confg nvram:startup-config\r\nConfigure using rtr2-confg from 172.16.101.101?[confirm]\r\nConnected to 172.16.101.101\r\nLoading 1112 byte file rtr2-confg:![OK]\r\n[OK]\r\nRouter#\r\n%SYS-5-CONFIG_NV:Non-volatile store configured from rtr2-config by\r\nFTP from 172.16.101.101\r\nExamples\r\nThe following example specifies a remote username of netadmin1. Then it copies the running configuration file\r\nnamed rtr2-confg to the netadmin1 directory on the remote host with an IP address of 172.16.101.101.\r\nRouter# configure terminal\r\n \r\nRouter(config)# ip rcmd remote-username netadmin1\r\n \r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 84 of 101\n\nRouter(config)#\r\nend\r\n \r\nRouter#\r\ncopy system:running-config rcp:\r\n \r\nRemote host[]? 172.16.101.101\r\n \r\nName of configuration file to write [Rtr2-confg]?\r\nWrite file rtr2-confg on host 172.16.101.101?[confirm]\r\nBuilding configuration...[OK]\r\nConnected to 172.16.101.101\r\nExamples\r\nThe following example copies the startup configuration to a TFTP server:\r\nRouter#\r\ncopy nvram:startup-config tftp:\r\nRemote host[]? 172.16.101.101\r\n \r\nName of configuration file to write [rtr2-confg]? \u003ccr\u003e\r\nWrite file rtr2-confg on host 172.16.101.101?[confirm] \u003ccr\u003e\r\n![OK]\r\nExamples\r\nThe following example copies the running configuration to the startup configuration. On a Class A flash file\r\nsystem platform, this command copies the running configuration to the startup configuration specified by the\r\nCONFIG_FILE variable.\r\ncopy system:running-config nvram:startup-config\r\nThe following example shows the warning that the system provides if you try to save configuration information\r\nfrom bootstrap into the system:\r\nRouter(boot)# copy system:running-config nvram:startup-config\r\nWarning: Attempting to overwrite an NVRAM configuration written\r\nby a full system image. This bootstrap software does not support\r\nthe full configuration command set. If you perform this command now,\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 85 of 101\n\nsome configuration commands may be lost.\r\nOverwrite the previous NVRAM configuration?[confirm]\r\nEnter no to escape writing the configuration information to memory.\r\nExamples\r\nOn some routers, you can store copies of configuration files on a flash memory device. Five examples follow:\r\nExamples\r\nThe following example copies the startup configuration file (specified by the CONFIG_FILE environment\r\nvariable) to a flash memory card inserted in slot 0:\r\nRouter# copy nvram:startup-config slot0:router-confg\r\nExamples\r\nThe following example copies the running configuration from the router to the flash memory PC card in slot 0:\r\nRouter# copy system:running-config slot0:berlin-cfg\r\n \r\nBuilding configuration...\r\n \r\n5267 bytes copied in 0.720 secs\r\nExamples\r\nThe following example copies the file named ios-upgrade-1 from the flash memory card in slot 0 to the running\r\nconfiguration:\r\nRouter# copy slot0:4:ios-upgrade-1 system:running-config\r\nCopy\r\n'ios-upgrade-1\r\n' from flash device\r\n as 'running-config' ? [yes/no] yes\r\n \r\nExamples\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 86 of 101\n\nThe following example copies the router-image file from the flash memory to the startup configuration:\r\nRouter# copy flash:router-image nvram:startup-config\r\nExamples\r\nThe following example copies the file running-config from the first partition in internal flash memory to the flash\r\nmemory PC card in slot 1. The checksum of the file is verified, and its copying time of 30 seconds is displayed.\r\nRouter# copy flash: slot1:\r\nSystem flash\r\nPartition Size Used Free Bank-Size State Copy Mode\r\n 1 4096K 3070K 1025K 4096K Read/Write Direct\r\n 2 16384K 1671K 14712K 8192K Read/Write Direct\r\n[Type ?\u003cno\u003e for partition directory; ? for full directory; q to abort]\r\nWhich partition? [default = 1]\r\nSystem flash directory, partition 1:\r\nFile Length Name/status\r\n 1 3142748 dirt/images/mars-test/c3600-j-mz.latest\r\n 2 850 running-config\r\n[3143728 bytes used, 1050576 available, 4194304 total]\r\nPCMCIA Slot1 flash directory:\r\nFile Length Name/status\r\n 1 1711088 dirt/images/c3600-i-mz\r\n 2 850 running-config\r\n[1712068 bytes used, 2482236 available, 4194304 total]\r\nSource file name? running-config\r\nDestination file name [running-config]?\r\nVerifying checksum for 'running-config' (file # 2)... OK\r\nErase flash device before writing? [confirm]\r\nFlash contains files. Are you sure you want to erase? [confirm]\r\nCopy 'running-config' from flash: device\r\n as 'running-config' into slot1: device WITH erase? [yes/no] yes\r\n \r\nErasing device... eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee ...erased\r\n!\r\n [OK - 850/4194304 bytes]\r\nFlash device copy took 00:00:30 [hh:mm:ss]\r\nVerifying checksum... OK (0x16)\r\nExamples\r\nIn the following example, the file config1 is copied from a remote server to flash memory using HTTP:\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 87 of 101\n\nRouter# copy\r\nhttp://\r\nwww.example.com:8080/configs/config1 flash:config1\r\nIn the following example, a default username and password for HTTP Client communications is configured, and\r\nthen the file sample.scr is copied from a secure HTTP server using HTTPS:\r\nRouter# configure terminal\r\n \r\nRouter(config)# ip http client username joeuser\r\nRouter(config)# ip http client password letmein\r\n \r\nRouter(config)# end\r\n \r\nRouter# copy https://www.example_secure.com/scripts/sample.scr flash:\r\nIn the following example, an HTTP proxy server is specified before using the copy http:// command:\r\nRouter# configure terminal\r\n \r\nRouter(config)# ip http client proxy-server edge2 proxy-port 29\r\n \r\nRouter(config)# end\r\n \r\nRouter# copy\r\nhttp://\r\nwww.example.com/configs/config3 flash:/configs/config3\r\nExamples\r\nThe following example copies the router-image file from the flash memory card inserted in slot 1 of the primary\r\nRSP card to slot 0 of the secondary RSP card in the same router:\r\nRouter# copy slot1:router-image slaveslot0:\r\nRelated Commands\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 88 of 101\n\nCommand Description\r\nboot config\r\nSpecifies the device and filename of the configuration file from which the router\r\nconfigures itself during initialization (startup).\r\nboot system Specifies the system image that the router loads at startup.\r\ncd Changes the default directory or file system.\r\ncopy xmodem:\r\nflash:\r\nCopies any file from a source to a destination.\r\ncopy ymodem:\r\nflash:\r\nCopies any file from a source to a destination.\r\ndelete Deletes a file on a flash memory device.\r\ndir Displays a list of files on a file system.\r\nerase Erases a file system.\r\nip rcmd\r\nremote-usernameConfigures the remote username to be used when requesting a remote copy using rcp.\r\nip scp server\r\nenable\r\nEnables scp server-side functionality.\r\nreload Reloads the operating system.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 89 of 101\n\nCommand Description\r\nshow bootvar\r\nDisplays the contents of the BOOT environment variable, the name of the configuration\r\nfile pointed to by the CONFIG_FILE environment variable, the contents of the\r\nBOOTLDR environment variable, and the configuration register setting.\r\nshow (flash file\r\nsystem)\r\nDisplays the layout and contents of a flash memory file system.\r\nslave auto-sync\r\nconfig\r\nTurns on automatic synchronization of configuration files for a Cisco 7507 or Cisco 7513\r\nrouter that is configured for Dual RSP Backup.\r\nverify\r\nbootflash:\r\nFile system or directory containing the files to list, followed by a colon.\r\ncopy erase flash\r\nThe copy erase flash command has been replaced by the erase flash: command. See the description of the erase\r\ncommand for more information.\r\nO n some platforms, use can use the copy /erase source-url flash: syntax to erase the local Flash file system before\r\ncopying a new file into Flash. See the desciption of the copy command for details on this option.\r\ncopy http\r\nThe copy http:// command is documented as part of the copy command.\r\ncopy https\r\nThe copy https:// command is documented as part of the copy command.\r\ncopy logging system\r\nTo copy archived system events to a destination file system, use the copy logging system command in privileged\r\nEXEC mode. To stop copying the archived system events, use the no form of the command.\r\ncopy logging system target: filename\r\nno copy logging system\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 90 of 101\n\nSyntax Description\r\ntarget :\r\nSpecifies the destination file system; Valid values are as follows:\r\nbootflash:\r\ndisk0:\r\ndisk1:\r\nftp:\r\nhttp:\r\nhttps:\r\nrcp:\r\nslavebootflash:\r\nslavedisk0:\r\nslavedisk1:\r\nslavesup-bootdisk:\r\nslavesup-bootflash:\r\nsup-bootdisk:\r\nsup-bootflash:\r\ntftp:\r\nfilename Name of the file.\r\nCommand Default\r\nThis command has no default settings.\r\nCommand Modes\r\nPrivileged EXEC (#)\r\nCommand History\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 91 of 101\n\nRelease Modification\r\n12.2(33)SXH This command was introduced.\r\n12.2(33)SCC\r\nThe command was introduced for the Cisco uBR10012 router in the Cisco IOS Software\r\nRelease 12.2(33)SCC.\r\nUsage Guidelines\r\nSystem Event Archive (SEA) is supported on switches that have a Supervisor Engine 32 or Supervisor Engine 720\r\nwith a compact flash adapter and a Compact Flash card (WS-CF-UPG= for Supervisor Engine 720).\r\nCisco Universal Broadband Router 10012\r\nThe System Event Archive (SEA) feature is used to address the debug trace and system console constraints. Use\r\nthe copy logging system command to copy the major and critical events stored in the sea_log.dat file, to the\r\ndestination file system.\r\nNote\r\nTo store the system event logs, the SEA requires either the PCMCIA ATA disk or Compact Flash Disk\r\nin compact flash adapter for PRE2.\r\nThe following example shows how to copy the SEA to the file system of disk0:\r\nRouter# copy logging system disk0:\r\nDestination filename [sea_log.dat]?\r\nThe following example shows how to copy the SEA using the remote file copy function (rcp):\r\nRouter# copy logging system rcp:\r\nAddress or name of remote host []? 192.0.2.1\r\nDestination username [Router]? username1\r\nDestination filename [sea_log.dat]? /auto/tftpboot-users/username1/sea_log.dat\r\nRelated Commands\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 92 of 101\n\nclear logging system Clears the event records stored in the SEA.\r\nlogging system Enables or disables SEA logging system.\r\nshow logging system Displays the SEA logging system disk.\r\ncopy xmodem\r\nTo copy a Cisco IOS image from a local or remote computer (such as a PC, Macintosh, or UNIX workstation) to\r\nFlash memory on a Cisco 3600 series router using the Xmodem protocol, use the copy xmodem: command in\r\nEXEC mode.\r\ncopy xmodem: flashfilesystem:\r\nSyntax Description\r\nflash-filesystem : Destination of the copied file, followed by a colon.\r\nCommand Modes\r\nEXEC\r\nCommand History\r\nRelease Modification\r\n11.2 P This command was introduced.\r\n12.2(15)T\r\nThis command is no longer supported in Cisco IOS Mainline or Technology-based (T)\r\nreleases. It may continue to appear in Cisco IOS 12.2S-family releases.\r\n12.2(33)SRA This command was integrated into Cisco IOS Release 12.2(33)SRA.\r\nUsage Guidelines\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 93 of 101\n\nThis command is a form of the copy command. The copy xmodem: and copy xmodem commands are identical.\r\nSee the description of the copy command for more information.\r\nCopying a file using FTP, rcp, or TFTP is much faster than copying a file using Xmodem. Use the copy xmodem:\r\ncommand only if you do not have access to an FTP, TFTP, or rcp server.\r\nThis copy operation is performed through the console or AUX port. The AUX port, which supports hardware flow\r\ncontrol, is recommended.\r\nNo output is displayed on the port over which the transfer is occurring. You can use the logging buffered\r\ncommand to log all router messages sent to the console port during the file transfer.\r\nExamples\r\nThe following example initiates a file transfer from a local or remote computer to the router’s internal Flash\r\nmemory using the Xmodem protocol:\r\ncopy xmodem: flash:\r\nRelated Commands\r\nCommand Description\r\ncopy Copies any file from a source to a destination.\r\ncopy\r\nymodem:\r\nCopies a Cisco IOS image from a local or remote computer (such as a PC, Macintosh, or\r\nUNIX workstation) to Flash memory on a Cisco 3600 series router using the Ymodem\r\nprotocol.\r\ncopy ymodem\r\nTo copy a Cisco IOS image from a local or remote computer (such as a PC, Macintosh, or UNIX workstation) to\r\nFlash memory on a Cisco 3600 series router using the Ymodem protocol, use the copy ymodem: command in\r\nEXEC mode.\r\ncopy ymodem: flashfilesystem:\r\nSyntax Description\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 94 of 101\n\nflash-filesystem : Destination of the copied file, followed by a colon.\r\nCommand Modes\r\nEXEC\r\nCommand History\r\nRelease Modification\r\n11.2 P This command was introduced.\r\n12.2(15)T\r\nThis command is no longer supported in Cisco IOS Mainline or Technology-based (T)\r\nreleases. It may continue to appear in Cisco IOS 12.2S-family releases.\r\n12.2(33)SRA This command was integrated into Cisco IOS Release 12.2(33)SRA.\r\nUsage Guidelines\r\nThe copy ymodem: and copy ymodem commands are identical. See the description of the copy command for\r\nmore information.\r\nCopying a file using FTP, rcp, or TFTP is much faster than copying a file using Ymodem. Use the copy ymodem:\r\ncommand only if you do not have access to an FTP, rcp, or TFTP server.\r\nThis copy operation is performed through the console or AUX port. The AUX port, which supports hardware flow\r\ncontrol, is recommended.\r\nNo output is displayed on the port over which the transfer is occurring. You can use the logging buffered\r\ncommand to log all router messages sent to the console port during the file transfer.\r\nExamples\r\nThe following example initiates a file transfer from a local or remote computer to the router’s internal Flash\r\nmemory using the Ymodem protocol:\r\ncopy ymodem: flash:\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 95 of 101\n\nRelated Commands\r\nCommand Description\r\ncopy\r\nxmodem:\r\nCopies a Cisco IOS image from a local or remote computer (such as a PC, Macintosh, or\r\nUNIX workstation) to Flash memory on a Cisco 3600 series router using the Xmodem\r\nprotocol.\r\ncopy noverify\r\nTo disable the automatic image verification for the current copy operation, use the copy /noverify command.\r\ncopy /noverify source-url destination-url\r\nSyntax Description\r\nsource-url\r\nLocation URL or alias of the source file or directory to be copied; see the “Usage\r\nGuidelines” section for additional information.\r\ndestination-urlDestination URL or alias of the copied file or directory; see the “Usage Guidelines” section\r\nfor additional information.\r\nCommand Default\r\nVerification is done automatically after completion of a copy operation.\r\nCommand Modes\r\nPrivileged EXEC\r\nCommand History\r\nRelease Modification\r\n12.2(14)SX Support for this command was introduced on the Supervisor Engine 720.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 96 of 101\n\nRelease Modification\r\n12.2(17d)SXB\r\nSupport for this command on the Supervisor Engine 2 was extended to Release\r\n12.2(17d)SXB.\r\n12.2(33)SRA This command was integrated into Cisco IOS Release 12.2(33)SRA.\r\nUsage Guidelines\r\nThe exact format of the source and destination URLs varies according to the file or directory location. You may\r\nenter either an alias keyword for a particular file or an alias keyword for a file system type (not a file within a\r\ntype).\r\nTimesaver\r\nAliases are used to cut down on the amount of typing that you need to perform. For example, it\r\nis easier to type copy run start (the abbreviated form of the copy running-config startup-config\r\ncommand) than it is to type copy system:r nvram:s (the abbreviated form of the copy\r\nsystem:running-config nvram:startup-config command). These aliases allow you to continue\r\nusing some of the common commands that are used in previous versions of Cisco IOS\r\nsoftware.\r\nThe table below shows two keyword shortcuts to URLs.\r\nTable 6. Common Keyword Aliases to URLs\r\nKeyword Source or Destination\r\nrunning-config(Optional) Specifies the alias for the system:running-config URL. This keyword does not work\r\nin the more and show file command syntaxes.\r\nstartup-config\r\n(Optional) Specifies the alias for the nvram:startup-config URL. The nvram:startup-config\r\nkeyword represents the configuration file that is used during initialization (startup). This file is\r\ncontained in NVRAM. This keyword does not work in more and show file EXEC command\r\nsyntaxes.\r\nThe following tables list aliases by file system type. If you do not specify an alias, the system looks for a file in\r\nthe current directory.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 97 of 101\n\nThe table below lists the URL prefix aliases for special (opaque) file systems.\r\nTable 7. URL Prefix Aliases for Special File Systems\r\nAlias Source or Destination\r\nflh: Source URL for Flash load helper log files.\r\nnvram:\r\nRouter NVRAM. You can copy the startup configuration into or from NVRAM. You can also\r\ndisplay the size of a private configuration file.\r\nnull: Null destination for copies or files. You can copy a remote file to null to determine its size.\r\nsystem: Source or destination URL for system memory, which includes the running configuration.\r\nxmodem: Source destination for the file from a network device that uses the Xmodem protocol.\r\nymodem: Source destination for the file from a network device that uses the Ymodem protocol.\r\nThe table below lists the URL prefix aliases for network file systems.\r\nTable 8. URL Prefix Aliases for Network File Systems\r\nAlias Source or Destination\r\nftp:\r\nSource or destination URL for an FTP network server. The syntax for this alias is as follows:ftp:\r\n[[[//username [:password]@]location]/directory]/filename.\r\nrcp:\r\nSource or destination URL for an rcp network server. The syntax for this alias is as follows: rcp:\r\n[[[//username@ ] location]/directory]/filename.\r\ntftp:\r\nSource or destination URL for a TFTP network server. The syntax for this alias is tftp:\r\n[[//location]/directory]/filename.\r\nThe table below lists the URL prefix aliases for local writable storage file systems.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 98 of 101\n\nTable 9. URL Prefix Aliases for Local Writable Storage File Systems\r\nAlias Source or Destination\r\nbootflash: Source or destination URL for boot flash memory.\r\ndisk0: and\r\ndisk1:\r\nSource or destination URL of rotating media.\r\nflash:\r\nSource or destination URL for Flash memory. This alias is available on all platforms.\r\nFor platforms that lack a Flash: device, note that flash: is aliased to slot0:, allowing you to\r\nrefer to the main Flash memory storage area on all platforms.\r\nslavebootflash:\r\nSource or destination URL for internal Flash memory on the secondary RSP card of a\r\ndevice that is configured for HSA.\r\nslaveram: NVRAM on a secondary RSP card of a device that is configured for HSA.\r\nslavedisk0:\r\nSource or destination URL of the first PCMCIA card on a secondary RSP card of a device\r\nthat is configured for HSA.\r\nslavedisk1:\r\nSource or destination URL of the second PCMCIA slot on a secondary RSP card of a\r\ndevice that is configured for HSA.\r\nslaveslot0:\r\nSource or destination URL of the first PCMCIA card on a secondary RSP card of a router\r\nconfigured for HSA--Available on systems that are configured with a Supervisor Engine 2.\r\nslaveslot1:\r\nSource or destination URL of the second PCMCIA slot on a secondary RSP card of a\r\nrouter configured for HSA--Available on systems that are configured with a Supervisor\r\nEngine 2.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 99 of 101\n\nAlias Source or Destination\r\nslot0:\r\nSource or destination URL of the first PCMCIA Flash memory card--Available on systems\r\nthat are configured with a Supervisor Engine 2.\r\nslot1:\r\nSource or destination URL of the second PCMCIA Flash memory card--Available on\r\nsystems that are configured with a Supervisor Engine 2.\r\nYou can enter on the command line all necessary source- and destination-URL information and the username and\r\npassword to use, or you can enter the copy command and have the switch prompt you for any missing\r\ninformation.\r\nIf you enter information, choose one of the following three options: running-config , startup-config , or a file\r\nsystem alias (see the tables above). The location of a file system dictates the format of the source or destination\r\nURL.\r\nThe colon is required after the alias. However, earlier commands that do not require a colon remain supported but\r\nare unavailable in context-sensitive help.\r\nThe entire copying process may take several minutes and differs from protocol to protocol and from network to\r\nnetwork.\r\nIn the alias syntax for ftp: , rcp: , and tftp: , the location is either an IP address or a hostname. The filename is\r\nspecified for the directory that is used for file transfers.\r\nEnter the file verify auto command to set up verification globally.\r\nExamples\r\nThis example shows how to disable the automatic image verification for the current copy operation:\r\nRouter# copy /noverify tftp: sup-bootflash:\r\n.................................................\r\n[OK - 24301348 bytes]\r\n24301348 bytes copied in 157.328 secs (154463 bytes/sec)\r\nRouter#\r\nRelated Commands\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 100 of 101\n\nCommand Description\r\nfile verify\r\nauto\r\nVerifies the compressed Cisco IOS image checksum.\r\nverify\r\nVerifies the checksum of a file on a Flash memory file system or compute an MD5 signature\r\nfor a file.\r\nBack to Top\r\nSource: https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689\r\nPage 101 of 101",
	"extraction_quality": 1,
	"language": "EN",
	"sources": [
		"MITRE"
	],
	"references": [
		"https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/C_commands.html#wp1068167689"
	],
	"report_names": [
		"C_commands.html#wp1068167689"
	],
	"threat_actors": [],
	"ts_created_at": 1775441440,
	"ts_updated_at": 1775791222,
	"ts_creation_date": 0,
	"ts_modification_date": 0,
	"files": {
		"pdf": "https://archive.orkl.eu/46f19d067413dd82a2c8cacb93a54673f70ccfd6.pdf",
		"text": "https://archive.orkl.eu/46f19d067413dd82a2c8cacb93a54673f70ccfd6.txt",
		"img": "https://archive.orkl.eu/46f19d067413dd82a2c8cacb93a54673f70ccfd6.jpg"
	}
}