{
	"id": "ea5c37d4-c808-4e9d-89c8-84c1a934d548",
	"created_at": "2026-04-06T00:21:59.171161Z",
	"updated_at": "2026-04-10T03:35:21.522295Z",
	"deleted_at": null,
	"sha1_hash": "a02407bc14f9034dc414c8da3d88ab4a70e172b2",
	"title": "Cisco IOS Configuration Fundamentals Command Reference - D through E [Support]",
	"llm_title": "",
	"authors": "",
	"file_creation_date": "0001-01-01T00:00:00Z",
	"file_modification_date": "0001-01-01T00:00:00Z",
	"file_size": 444700,
	"plain_text": "Cisco IOS Configuration Fundamentals Command Reference - D\r\nthrough E [Support]\r\nPublished: 2025-12-16 · Archived: 2026-04-05 18:21:37 UTC\r\nD through E\r\nD through E\r\ndatabits\r\nTo set the number of data bits per character that are interpreted and generated by the router hardware, use the\r\ndatabits command in line configuration mode. To restore the default value, use the no form of the command.\r\ndatabits {5 | 6 | 7 | 8}\r\nno databits\r\nSyntax Description\r\n5 Five data bits per character.\r\n6 Six data bits per character.\r\n7 Seven data bits per character.\r\n8 Eight data bits per character. This is the default.\r\nCommand Default\r\nEight data bits per character\r\nCommand Modes\r\nLine configuration\r\nCommand History\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 1 of 111\n\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\nThe databits line configuration command can be used to mask the high bit on input from devices that generate 7\r\ndata bits with parity. If parity is being generated, specify 7 data bits per character. If no parity generation is in\r\neffect, specify 8 data bits per character. The other keywords are supplied for compatibility with older devices and\r\ngenerally are not used.\r\nExamples\r\nThe following example sets the number of data bits per character to seven on line 4:\r\nRouter(config)# line 4\r\nRouter(config-line)# databits 7\r\nRelated Commands\r\nCommand Description\r\ndata-character-bits\r\nSets the number of data bits per character that are interpreted and generated by the\r\nCisco IOS software.\r\nterminal databits\r\nChanges the number of data bits per character for the current terminal line for this\r\nsession.\r\nterminal data-character-bitsSets the number of data bits per character that are interpreted and generated by the\r\nCisco IOS software for the current line and session.\r\ndata-character-bits\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 2 of 111\n\nTo set the number of data bits per character that are interpreted and generated by the Cisco IOS software, use the\r\ndata-character-bits command in line configuration mode. To restore the default value, use the no form of this\r\ncommand.\r\ndata-character-bits {7 | 8}\r\nno data-character-bits\r\nSyntax Description\r\n7 Seven data bits per character.\r\n8 Eight data bits per character. This is the default.\r\nCommand Default\r\nEight data bits per character\r\nCommand Modes\r\nLine 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\nUsage Guidelines\r\nThe data-character-bits line configuration command is used primarily to strip parity from X.25 connections on\r\nrouters with the protocol translation software option. The data-character-bits line configuration command does not\r\nwork on hard-wired lines.\r\nExamples\r\nThe following example sets the number of data bits per character to seven on virtual terminal line (vty) 1:\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 3 of 111\n\nRouter(config)# line vty 1\r\nRouter(config-line)# data-character-bits 7\r\nRelated Commands\r\nCommand Description\r\nterminal data-character-bitsSets the number of data bits per character that are interpreted and generated by the\r\nCisco IOS software for the current line and session.\r\ndefault-value data-character-bits\r\nTo configure the number of data bits per character that are generated and interpreted by Cisco software to either 7\r\nbits or 8 bits, use the default-value data-character-bits command in global configuration mode. To disable the\r\nconfigured size, use the no form of this command.\r\ndefault-value data-character-bits {7 | 8}\r\nno default-value data-character-bits\r\nSyntax Description\r\n7 Selects 7 bits as the default size.\r\n8 Selects 8 bits as the default size.\r\nCommand Default\r\n8 data bits per character are generated.\r\nCommand Modes\r\nGlobal configuration (config)\r\nCommand History\r\nRelease Modification\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 4 of 111\n\nRelease Modification\r\n15.0(1)M\r\nThis command was introduced in 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 integrated into Cisco IOS XE Release 2.1.\r\nExamples\r\nThe following example shows how to set the default number of data character bits to 8:\r\nRouter# configure terminal\r\nRouter(config)# default-value data-character-bits 8\r\nRelated Commands\r\nCommand Description\r\ndefault-value exec-character-bits Defines the EXEC character width to either 7 bits or 8 bits.\r\ndefault-value modem-signal Configures the default frequency time to scan modem signals.\r\ndefault-value special-character-bitsConfigures the flow control default value from a 7-bit width to an 8-bit\r\nwidth.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 5 of 111\n\ndefault-value exec-character-bits\r\nTo define the EXEC character width for either 7 bits or 8 bits, use the default-value exec-character-bits command\r\nin global configuration mode. To restore the default value, use the no form of this command.\r\ndefault-value exec-character-bits {7 | 8}\r\nno default-value exec-character-bits\r\nSyntax Description\r\n7 Selects the 7-bit ASCII character set. This is the default.\r\n8 Selects the full 8-bit ASCII character set .\r\nCommand Default\r\n7-bit ASCII character set\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\nUsage Guidelines\r\nConfiguring the EXEC character width to 8 bits allows you to add graphical and international characters in\r\nbanners, prompts, and so on. However, setting the EXEC character width to 8 bits can also cause failures. If a user\r\non a terminal that is sending parity enters the help command, an “unrecognized command” message appears\r\nbecause the system is reading all 8 bits, although the eighth bit is not needed for the help command.\r\nExamples\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 6 of 111\n\nThe following example selects the full 8-bit ASCII character set for EXEC banners and prompts:\r\nRouter(config)# default-value exec-character-bits 8\r\nRelated Commands\r\nCommand Description\r\ndefault-value special-character-bits\r\nConfigures the flow control default value from a 7-bit width to an 8-bit width.\r\nexec-character-bits\r\nConfigures the character widths of EXEC and configuration command\r\ncharacters.\r\nlength Sets the terminal screen length.\r\nterminal exec-character-bitsLocally changes the ASCII character set used in EXEC and configuration\r\ncommand characters for the current session.\r\nterminal special-character-bitsChanges the ASCII character widths to accept special characters for the current\r\nterminal line and session.\r\ndefault-value modem-interval\r\nTo configure the default frequency time to scan modem signals, use the default-value modem-interval command in\r\nglobal configuration mode. To disable the configured frequency, use the no form of this command.\r\ndefault-value modem-interval milliseconds\r\nno default-value modem-interval\r\nSyntax Description\r\nmilliseconds Time frequency, in milliseconds (ms). The range is from 0 to 1000.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 7 of 111\n\nCommand Default\r\nThe frequency time to scan modem signals is 50 ms.\r\nCommand Modes\r\nGlobal configuration (config)\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\nExamples\r\nThe following example shows how to set the default time to scan the modem signal to 345 ms:\r\nRouter# configure terminal\r\nRouter(config)# default-value modem-signal 345\r\nRelated Commands\r\nCommand Description\r\ndefault-value data-character-bits Configures the default size of bits handled to either 7 bits or 8 bits.\r\ndefault-value exec-character-bits Defines the EXEC character width to either 7 bits or 8 bits.\r\ndefault-value special-character-bitsConfigures the flow control default value from a 7-bit width to an 8-bit\r\nwidth.\r\ndefault-value special-character-bits\r\nTo configure the flow control default value from a 7-bit width to an 8-bit width, use the default-value special-character-bits command in global configuration mode. To restore the default value, use the no form of this\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 8 of 111\n\ncommand.\r\ndefault-value special-character-bits commanddefault-value special-character-bits {7 | 8}\r\nno default-value special-character-bits\r\nSyntax Description\r\n7 Selects the 7-bit character set. This is the default.\r\n8 Selects the full 8-bit character set.\r\nCommand Default\r\n7-bit character set\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\nUsage Guidelines\r\nConfiguring the special character width to 8 bits allows you to add graphical and international characters in\r\nbanners, prompts, and so on.\r\nExamples\r\nThe following example selects the full 8-bit special character set:\r\nRouter(config)# default-value special-character-bits 8\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 9 of 111\n\nRelated Commands\r\nCommand Description\r\ndefault-value exec-character-bits\r\nDefines the EXEC character width for either 7 bits or 8 bits.\r\nexec-character-bits\r\nConfigures the character widths of EXEC and configuration command\r\ncharacters.\r\nlength Sets the terminal screen length.\r\nterminal exec-character-bitsLocally changes the ASCII character set used in EXEC and configuration\r\ncommand characters for the current session.\r\nterminal special-character-bitsChanges the ASCII character widths to accept special characters for the current\r\nterminal line and session.\r\ndefine interface-range\r\nTo create an interface-range macro, use the define interface-range command in global configuration mode. To\r\nremove an interface-range macro, use the no form of this command.\r\ndefine interface-range macro-name interface-range\r\nSyntax Description\r\nmacro-name Name of the interface-range macro.\r\ninterface-range\r\nType of interface range.\r\nFor a list of valid values, see the “Usage Guidelines” section.\r\nCommand Default\r\nInterface-range macro is not configured.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 10 of 111\n\nCommand Modes\r\nGlobal configuration (config)\r\nCommand History\r\nRelease Modification\r\n12.2(14)SX This command was introduced.\r\n12.2(17d)SXB This command was integrated into Cisco IOS XE Release 12.2(17d)SXB.\r\n12.2(33)SRA This command was integrated into Cisco IOS Release 12.2(33)SRA.\r\n15.1(2)SNG\r\nThis command was implemented on the Cisco ASR 901 Series Aggregation Services\r\nRouters.\r\nUsage Guidelines\r\nThe define interface-range command applies a particular configuration on multiple interfaces and creates\r\nmultiple logical, and sub interfaces.\r\nAn interface range macro name can comprise up to 32 characters.\r\nAn interface range for a macro can accept a maximum of five ranges. However, the subinterface range for a\r\nmacro accepts only one range.\r\nAn interface range cannot span slots.\r\nUse the interface-type slot/first-interface last-interface format to enter the interface range.\r\nValid values for the interface-type argument are as follows:\r\natm —Supported on Cisco 7600 series routers that are configured with a Supervisor Engine 2\r\nethernet\r\nfastethernet\r\nge-wan —Supported on Cisco 7600 series routers that are configured with a Supervisor Engine 2\r\ngigabitethernet\r\nloopback\r\nport-channel interface-number —Valid values are from 1 to 256\r\npos —Supported on Cisco 7600 series routers that are configured with a Supervisor Engine 2\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 11 of 111\n\ntengigabitethernet\r\ntunnel\r\nvlan vlan-id —Valid values are from 1 to 4094\r\nExamples\r\nThe following example shows how to create a multiple-interface macro:\r\nDevice(config)# define interface-range macro1 ethernet 1/2 - 5, fastethernet 5/5 - 10\r\nThe following example shows how to create multiple loopback interfaces:\r\nDevice(config)# define interface-range loopback1-10\r\nRelated Commands\r\nCommand Description\r\ninterface range Executes a command on multiple ports at the same time.\r\ndelete\r\nTo delete a file on a Flash memory device or NVRAM, use the delete command in EXEC, privileged EXEC, or\r\ndiagnostic mode.\r\ndelete url [/force | /recursive]\r\nSyntax Description\r\nurl\r\nCisco IOS File System URL of the file to be deleted. Include the file system prefix, followed by\r\na colon, and, optionally, the name of a file or directory. See the table below for a list of supported\r\nURLs.\r\n/force\r\n(Optional) Deletes the specified file or directory without prompting you for verification.\r\nNote\r\n \r\nUse this keyword with caution: the system will not ask you to confirm the file\r\ndeletion.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 12 of 111\n\n/recursive (Optional) Deletes all files in the specified directory, as well as the directory itself.\r\nCommand Modes\r\nEXEC (\u003e)\r\nPrivileged EXEC (#)\r\nDiagnostic (diag)\r\nCommand History\r\nRelease Modification\r\n11.0 This command was introduced.\r\n12.3(14)T\r\nThe usbflash 0 9 : and usbtoken 0 9 : options were added to the list of Cisco IOS File\r\nSystem URLs.\r\n12.2(33)SRA This command was integrated into Cisco IOS Release 12.2(33)SRA.\r\nCisco IOS XE\r\nRelease 2.1\r\nThis command was introduced on the Cisco ASR 1000 Series Routers and the following\r\nenhancements were introduced:\r\nThis command was introduced in diagnostic mode for the first time. The\r\ncommand can be entered in both privileged EXEC and diagnostic mode on the\r\nCisco ASR1000 Series Routers.\r\nThe harddisk: , obfl: , stby-bootflash: stby-harddisk: , stby-nvram: , stby-obfl: ,\r\nstby-usb [0 -1 ]: , and usb [0 1 ]: url options were introduced.\r\nUsage Guidelines\r\nIf you attempt to delete the configuration file or image specified by the CONFIG_FILE or BOOTLDR\r\nenvironment variable, the system prompts you to confirm the deletion. Also, if you attempt to delete the last valid\r\nsystem image specified in the BOOT environment variable, the system prompts you to confirm the deletion. To\r\naccept the change, you may enter y , Y , or simply hit the Enter key. Entering ? will emit a help prompt.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 13 of 111\n\nWhen you delete a file in Flash memory, the software simply marks the file as deleted, but it does not erase the\r\nfile. To later recover a “deleted” file in Flash memory, use the undelete EXEC command. You can delete and\r\nundelete a file up to 15 times.\r\nTo permanently delete all files marked “deleted” on a linear Flash memory device, use the squeeze EXEC\r\ncommand.\r\nThe table below contains a list of Cisco IOS File System URLs.\r\nTable 1. URL File System Prefix Keywords\r\nPrefix Filesystem\r\nbootflash: Delete the file from boot Flash memory.\r\nflash: Delete the file from Flash memory.\r\nharddisk: Delete the file from the harddisk file system.\r\nnvram: Delete the from the router NVRAM.\r\nobfl: Delete the file from the onboard failure logging file system.\r\nslot0: Delete the file from the first PCMCIA Flash memory card.\r\nstby-bootflash: Delete the file from the standby bootflash file system.\r\nstby-harddisk: Delete the file from the standby harddisk file system.\r\nstby-nvram: Delete the from the router NVRAM on the standby hardware.\r\nstby-obfl: Delete the file from the onboard failure logging file system on the standby hardware.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 14 of 111\n\nPrefix Filesystem\r\nstby-usb [ 0 - 1 ]: Delete the file from the standby USB Flash drive.\r\nusb [ 0 - 1 ]; Delete the file from the USB Flash drive.\r\nusbflash 0 9 : Delete the file from the USB Flash drive.\r\nusbtoken 0 9 : Delete the file from the USB eToken.\r\nExamples\r\nThe following example deletes the file named test from the Flash card inserted in slot 0:\r\nRouter# delete slot0:test\r\n \r\nDelete slot0:test? [confirm]\r\nRelated Commands\r\nCommand Description\r\ncd Changes the default directory or file system.\r\ndir Displays a list of files on a file system.\r\nshow\r\nbootvar\r\nDisplays the contents of the BOOT environment variable, the name of the configuration file\r\npointed to by the CONFIG_FILE environment variable, the contents of the BOOTLDR\r\nenvironment variable, and the configuration register setting.\r\nsqueeze Permanently deletes Flash files by squeezing a Class A Flash file system.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 15 of 111\n\nCommand Description\r\nundelete Recovers a file marked “deleted” on a Class A or Class B Flash file system.\r\ndiag\r\nTo perform field diagnostics on a line card, on the Gigabit Route Processor (GRP), on the Switch Fabric Cards\r\n(SFCs), and on the Clock Scheduler Card (CSC) in Cisco 12000 series Gigabit Switch Routers (GSRs), use the\r\ndiag command in privileged EXEC mode. To disable field diagnostics on a line card, use the no form of this\r\ncommand.\r\ndiag command diag slot-number [halt | previous | post | verbose [wait] | wait]\r\nno diag slot-number\r\nSyntax Description\r\nslot-number\r\nSlot number of the line card you want to test. Slot numbers range from 0 to 11 for the Cisco\r\n12012 and 0 to 7 for the Cisco 12008 router. Slot numbers for the CSC are 16 and 17, and for the\r\nFSC are 18, 19, and 20.\r\nhalt (Optional) Stops the field diagnostic testing on the line card.\r\nprevious (Optional) Displays previous test results (if any) for the line card.\r\npost\r\n(Optional) Initiates an EPROM-based extended power-on self-test (EPOST) only. The EPOST\r\ntest suite is not as comprehensive as the field diagnostics, and a pass/fail message is the only\r\nmessage displayed on the console.\r\nverbose\r\n[wait\r\n(Optional) Enables the maximum status messages to be displayed on the console. By default,\r\nonly the minimum status messages are displayed on the console. If you specify the optional wait\r\nkeyword, the Cisco IOS software is not automatically reloaded on the line card after the test\r\ncompletes.\r\nwait (Optional) Stops the automatic reloading of the Cisco IOS software on the line card after the\r\ncompletion of the field diagnostic testing. If you use this keyword, you must use the microcode\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 16 of 111\n\nreload slot global configuration command, or manually remove and insert the line card (to power\r\nit up) in the slot so that the GRP will recognize the line card and download the Cisco IOS\r\nsoftware image to the line card.\r\nCommand Default\r\nNo field diagnostics tests are performed on the line card.\r\nCommand Modes\r\nPrivileged EXEC\r\nCommand History\r\nRelease Modification\r\n11.2 GS This command was introduced to support the Cisco 12000 series GSR.\r\n12.2(33)SRA This command was integrated into Cisco IOS Release 12.2(33)SRA.\r\nUsage Guidelines\r\nThe diag command must be executed from the GRP main console port.\r\nPerform diagnostics on the CSC only if a redundant CSC is in the router.\r\nDiagnostics will stop and ask you for confirmation before altering the router’s configuration. For example,\r\nrunning diagnostics on a SFC or CSC will cause the fabric to go from full bandwidth to one-fourth bandwidth.\r\nBandwidth is not affected by GRP or line card diagnostics.\r\nThe field diagnostic software image is bundled with the Cisco IOS software and is downloaded automatically\r\nfrom the GRP to the target line card prior to testing.\r\nCaution\r\nPerforming field diagnostics on a line card stops all activity on the line card. Before the diag\r\nEXEC command begins running diagnostics, you are prompted to confirm the request to perform\r\nfield diagnostics on the line card.\r\nIn normal mode, if a test fails, the title of the failed test is displayed on the console. However, not all tests that are\r\nperformed are displayed. To view all the tests that are performed, use the verbose keyword.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 17 of 111\n\nAfter all diagnostic tests are completed on the line card, a PASSED or TEST FAILURE message is displayed. If\r\nthe line card sends a PASSED message, the Cisco IOS software image on the line card is automatically reloaded\r\nunless the wait keyword is specified. If the line card sends a TEST FAILURE message, the Cisco IOS software\r\nimage on the line card is not automatically reloaded.\r\nIf you want to reload the line card after it fails diagnostic testing, use the microcode reload slot global\r\nconfiguration command.\r\nNote\r\nWhen you stop the field diagnostic test, the line card remains down (that is, in an unbooted state). In\r\nmost cases, you stopped the testing because you need to remove the line card or replace the line card.\r\nIf that is not the case, and you want to bring the line card back up (that is, online), you must use the\r\nmicrocode reload global configuration command or power cycle the line card.\r\nIf the line card fails the test, the line card is defective and should be replaced. In future releases this might not be\r\nthe case because DRAM and SDRAM SIMM modules might be field replaceable units. For example, if the\r\nDRAM test failed you might only need to replace the DRAM on the line card.\r\nFor more information, refer to the Cisco 12000 series installation and configuration guides.\r\nExamples\r\nIn the following example, a user is shown the output when field diagnostics are performed on the line card in slot\r\n3. After the line card passes all field diagnostic tests, the Cisco IOS software is automatically reloaded on the card.\r\nBefore starting the diagnostic tests, you must confirm the request to perform these tests on the line card because\r\nall activity on the line card is halted. The total/indiv. timeout set to 600/220 sec. message indicates that 600\r\nseconds are allowed to perform all field diagnostics tests, and that no single test should exceed 220 seconds to\r\ncomplete.\r\nRouter# diag 3\r\n \r\nRunning Diags will halt ALL activity on the requested slot. [confirm]\r\nRouter#\r\nLaunching a Field Diagnostic for slot 3\r\nRunning DIAG config check\r\nRUNNING DIAG download to slot 3 (timeout set to 400 sec.)\r\nsending cmd FDIAG-DO ALL to fdiag in slot 3\r\n(total/indiv. timeout set to 600/220 sec.)\r\nField Diagnostic ****PASSED**** for slot 3\r\nField Diag eeprom values: run 159 fial mode 0 (PASS) slot 3\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 18 of 111\n\nlast test failed was 0, error code 0\r\nsending SHUTDOWN FDIAG_QUIT to fdiag in slot 3\r\nBoard will reload\r\n.\r\n.\r\n.\r\nRouter#\r\nIn the following example, a user is shown the output when field diagnostics are performed on the line card in slot\r\n3 in verbose mode:\r\nRouter# diag 3 verbose\r\n \r\nRunning Diags will halt ALL activity on the requested slot. [confirm]\r\nRouter#\r\nLaunching a Field Diagnostic for slot 3\r\nRunning DIAG config check\r\nRUNNING DIAG download to slot 3 (timeout set to 400 sec.)\r\nsending cmd FDIAG-DO ALL to fdiag in slot 3\r\n(total/indiv. timeout set to 600/220 sec.)\r\nFDIAG_STAT_IN_PROGRESS: test #1 R5K Internal Cache\r\nFDIAG_STAT_PASS test_num 1\r\nFDIAG_STAT_IN_PROGRESS: test #2 Sunblock Ordering\r\nFDIAG_STAT_PASS test_num 2\r\nFDIAG_STAT_IN_PROGRESS: test #3 Dram Datapins\r\nFDIAG_STAT_PASS test_num 3\r\n.\r\n.\r\n.\r\nField Diags: FDIAG_STAT_DONE\r\nField Diagnostic ****PASSED**** for slot 3\r\nField Diag eeprom values: run 159 fial mode 0 (PASS) slot 3\r\n last test failed was 0, error code 0\r\nsending SHUTDOWN FDIAG_QUIT to fdiag in slot 3\r\nBoard will reload\r\n.\r\n.\r\n.\r\nRouter#\r\nRelated Commands\r\nCommand Description\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 19 of 111\n\nCommand Description\r\nmicrocode\r\nreload\r\nReloads the Cisco IOS image on a line card on the Cisco 7000 series with RSP7000, Cisco\r\n7500 series, or Cisco 12000 series routers after all microcode configuration commands have\r\nbeen entered.\r\ndiagnostic bootup level\r\nTo set the diagnostic bootup level, use the diagnostic bootup level command in global configuration mode. To skip\r\nall diagnostic tests, use the no form of this command.\r\ndiagnostic bootup level {minimal | complete}\r\nno diagnostic bootup level\r\nSyntax Description\r\nminimal Specifies minimal diagnostics. See the Usage Guidelines section for additional information.\r\ncomplete Specifies complete diagnostics. See the Usage Guidelines section for additional information.\r\nCommand Default\r\nminimal\r\nCommand Modes\r\nGlobal configuration (config)\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/D_through_E.html#wp3557227463\r\nPage 20 of 111\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\n12.2(33)SCC\r\nThe command was integrated in this release to support Generic Online Diagnostics (GOLD)\r\nfunctionality for Cisco UBR10012 Universal Broadband Router.\r\nUsage Guidelines\r\nSetting the diagnostic level determines the level of testing that occurs when the system or module is reset. The two\r\nlevels are as follows:\r\nComplete--Runs all tests.\r\nMinimal--Runs only EARL tests for the supervisor engine and loopback tests for all ports in the system.\r\nNote\r\nAlthough the default is minimal , you can set the diagnostic level to complete for troubleshooting\r\nhardware problems.\r\nIn certain circumstances, you might want to skip the bootup online diagnostics completely. For example, you\r\nmight skip the bootup online diagnostics to verify that a port is as bad as online diagnostics reports. To skip online\r\ndiagnostic testing completely, use the no diagnostic bootup level command.\r\nFor information on the diagnostic test types, use the show diagnostic command.\r\nThe new level takes effect at the next reload or the next time that an online insertion and removal is performed.\r\nExamples\r\nThe following example shows how to set the diagnostic bootup level:\r\nRouter(config)#\r\ndiagnostic bootup level complete\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 21 of 111\n\nRelated Commands\r\nCommand Description\r\nshow diagnostic bootup level Displays the coverage level for the configured bootup diagnostics.\r\ndiagnostic cns\r\nTo configure the Cisco Networking Services (CNS) diagnostics, use the diagnostic cns command in global\r\nconfiguration mode. To disable sending diagnostic results to the CNS event bus., use the no form of this\r\ncommand.\r\ndiagnostic cns {publish | subscribe} [subject]\r\nno diagnostic cns {publish | subscribe} [subject]\r\nSyntax Description\r\npublish\r\nSends diagnostic results to a remote network application to make decisions and take corrective\r\nactions that are based on the diagnostic results.\r\nsubscribe\r\nReceives messages from remote network applications to perform diagnostic tests or retrieve\r\ndiagnostic results.\r\nsubject (Optional) Event subject name.\r\nCommand Default\r\nThe following are the default settings for diagnostic cns:\r\ndiagnostic cns publish cisco.cns.device.diag_results\r\ndiagnostic cns subscribe cisco.cns.device.diag_commands\r\nCommand Modes\r\nGlobal configuration\r\nCommand History\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 22 of 111\n\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\nThe online diagnostics receive events by subscribing to an event subject name. The subject is the event that you\r\nsubscribe (receive) or publish (generate) through the CNS bus.\r\nThe diagnostic cns publish command sends diagnostic results to a remote network application to make decisions\r\nand take corrective actions that are based on the diagnostic results.\r\nThe diagnostic cns subscribe command receives messages from remote network applications to perform\r\ndiagnostic tests or retrieve diagnostic results.\r\nExamples\r\nThis example shows how to enable the publishing of diagnostic results:\r\nRouter(config)#\r\ndiagnostic cns publish my.cns.publish\r\nRouter(config)#\r\nThis example shows how to receive messages from remote network applications to perform diagnostic tests or\r\nretrieve diagnostic results:\r\nRouter(config)#\r\ndiagnostic cns subscribe my.cns.subscribe\r\nRouter(config)#\r\nThis example shows how to set the default to publish :\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 23 of 111\n\nRouter(config)#\r\ndefault\r\ndiagnostic cns publish\r\nRouter(config)#\r\nRelated Commands\r\nCommand Description\r\nshow diagnostic cns publish Displays the publish information about the CNS subject.\r\nshow diagnostic cns subscribe Displays the subscribe information about the CNS subject.\r\ndiagnostic event-log size\r\nTo modify the diagnostic event log size dynamically, use the diagnostic event-log size command in global\r\nconfiguration mode. To return to the default settings, use the no form of this command.\r\ndiagnostic event-log size size\r\nno diagnostic event-log size\r\nSyntax Description\r\nsize Diagnostic event-log sizes. The valid values range from 1 to 10000 entries.\r\nCommand Default\r\nThe event log size is 500 entries.\r\nCommand Modes\r\nGlobal configuration (config)\r\nCommand History\r\nRelease Modification\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 24 of 111\n\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\n12.2(33)SCC\r\nThe command was integrated in this release to support Generic Online Diagnostics (GOLD)\r\nfunctionality for Cisco UBR10012 Universal Broadband Router.\r\nUsage Guidelines\r\nThe events are dynamically allocated and stored in a circular queue.\r\nYou can enter either the default diagnostic event-log size command or the no diagnostic event-log size command\r\nto return to the default settings.\r\nExamples\r\nThe following example shows how to set the diagnostic event-log size:\r\nRouter(config)#\r\ndiagnostic event-log size 600\r\nRelated Commands\r\nCommand Description\r\nshow diagnostic events Displays the event log for the diagnostic events.\r\ndiagnostic level\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 25 of 111\n\nTo turn on power-on diagnostic tests for the network service engines (NSEs) installed in a Cisco 7300 series\r\nrouter, use the diagnostic level command in privileged EXEC configuration mode. There is no no form of this\r\ncommand.\r\ndiagnostic level {power-on | bypass}\r\nSyntax Description\r\npower-on Power-on diagnostic tests are performed at system bootup on the NSEs.\r\nbypass No diagnostic tests are performed. This is the default.\r\nCommand Default\r\nNo diagnostic tests are performed.\r\nCommand Modes\r\nPrivileged EXEC\r\nCommand History\r\nRelease Modification\r\n12.1(10)EX2 This command was introduced.\r\n12.2(18)S This command was introduced on Cisco 7304 routers running Cisco IOS Release 12.2 S.\r\n12.2(33)SRA This command was integrated into Cisco IOS Release 12.2(33)SRA.\r\n12.2SX\r\nThis command is supported in the Cisco IOS Release 12.2SX train. Support in a specific\r\n12.2SX release of this train depends on your feature set, platform, and platform hardware.\r\nUsage Guidelines\r\nUse this command to enable power-on diagnostic tests to run on the installed NSEs of a Cisco 7300 series router\r\nwhen the system is booted. It is recommended that you issue this command only if you are experiencing problems\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 26 of 111\n\nwith an NSE and are planning on rebooting the router. Issuing this command causes an increase in the boot time.\r\nExamples\r\nThe following example shows how to enable diagnostic power-on tests:\r\ndiagnostic level power-on\r\nThe following sample output shows the output that is displayed upon system bootup after a power cycle or router\r\ncrash:\r\n.\r\n.\r\n.\r\nSystem Power On Diagnostics\r\nDRAM Size ....................128 MB\r\nTesting DRAM..................Passed\r\nLevel2 Cache .................Present\r\nTesting Level2 Cache (256 KB)Passed\r\nLevel3 Cache .................Present\r\nTesting Level3 Cache (1024 KB)Passed\r\nSystem Power On Diagnostics Complete\r\nNote\r\nThis output is displayed when the system is booting, not when the command is issued.\r\nRelated Commands\r\nCommand Description\r\ndebug redundancy Enables NSE redundancy debugging.\r\nshow c7300\r\nDisplays the types of cards (NSE and line cards) installed in a Cisco 7300 series\r\nrouter.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 27 of 111\n\nCommand Description\r\nshow redundancy\r\n(7300)\r\nDisplays redundancy information for the active and standby NSEs.\r\ndiagnostic monitor\r\nTo configure health-monitoring diagnostic testing, use the diagnostic monitor command in global configuration\r\nmode. To disable testing, use the no form of this command.\r\ndiagnostic monitor intervalmodule number test {test-id | test-id-range | all} hh:mm:ss milliseconds days\r\ndiagnostic monitor syslog\r\ndiagnostic monitor module num test {test-id | test-id-range | all}\r\nno diagnostic monitor {interval | syslog}\r\nCisco UBR10012 Router\r\ndiagnostic monitor {bay slot/ bay | slot slot number | subslot slot/ subslot} test {test-id | test-id-range | all}\r\ndiagnostic monitor interval {bay slot/ bay | slot slot-no | subslot slot/ subslot} test {test-id | test-id-range |\r\nall} hh:mm:ss milliseconds days\r\ndiagnostic monitor syslog\r\ndiagnostic monitor threshold {bay slot/ bay | slot slot-no | subslot slot/ subslot} test {test-id | test-id-range |\r\nall} failure count failures [ {runs | days | hours | minutes | seconds | milliseconds} window_size]\r\nSyntax Description\r\ninterval Sets the interval between testing.\r\nmodule number Specifies the module number.\r\ntest Specifies a test to run.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 28 of 111\n\ntest-id\r\nIdentification number for the test to run. See the “Usage Guidelines” section for additional\r\ninformation.\r\ntest-id-range\r\nRange of identification numbers for tests to be run. See the “Usage Guidelines” section\r\nfor additional information.\r\nall Runs all the diagnostic tests.\r\nhour hh\r\n(Optional) Specifies the number of hours between tests. See the “Usage Guidelines”\r\nsection for formatting guidelines.\r\nmin mm\r\n(Optional) Specifies the number of minutes between tests. See the “Usage Guidelines”\r\nsection for formatting guidelines.\r\nsecond ss\r\n(Optional) Specifies the number of seconds between tests. See the “Usage Guidelines”\r\nsection for formatting guidelines.\r\nmillisec ms\r\n(Optional) Specifies the number of milliseconds between tests; see the “Usage\r\nGuidelines” section for formatting guidelines.\r\nsyslog Enables system logging messages when a health-monitoring test fails.\r\nbay slot/bay\r\nIndicates the card slot and bay number where the diagnostic test is run periodically and\r\nmonitored. The bay keyword is used to refer a SPA on the router. The valid range for the\r\nslot number is from 1 to 8 and 0 to 3 for the bay number.\r\nslot slotnumber\r\nIndicates the slot number of the full-height line card where the diagnostic test is run\r\nperiodically and monitored. The slot keyword is used to refer a full-height line card on the\r\nrouter. The valid range for the slot is from 1 to 8.\r\nsubslot\r\nslot/subslot\r\nIndicates the slot and subslot number of half-height line card on which the diagnostic test\r\nis run periodically and monitored. The subslot keyword is used to refer a half-height line\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 29 of 111\n\ncard on the router. The valid range for the slot number is from 1 to 8 and 0 to 1 for the\r\nsubslot number.\r\nthreshold Configures the failure threshold value for the specified bay, slot, or subslot.\r\nfailure count\r\nfailures\r\nConfigures the count for maximum failures allowed after which the failed test results are\r\ndisplayed in the output of the show diagnostic results command. The range for number of\r\nallowed failures is 0 to 99.\r\nhh:mm:ss Hours, minutes, and seconds interval configured to run the test again.\r\nmilliseconds Number of milliseconds between tests.\r\ndays Number of days between tests. The valid range is from 0 to 20.\r\nruns\r\nwindow_size\r\nNumber of test-run count for the failure window-size.\r\ndays\r\nwindow_size\r\nNumber of days for the failure window-size.\r\nhours\r\nwindow_size\r\nNumber of hours for the failure window-size.\r\nminutes\r\nwindow_size\r\nNumber of minutes for the failure window-size.\r\nseconds\r\nwindow_size\r\nNumber of seconds for the failure window-size.\r\nmilliseconds\r\nwindow_size\r\nNumber of milliseconds for the failure window-size.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 30 of 111\n\nCommand Default\r\nThe defaults are as follows:\r\nDepending on the test run, monitoring may be enabled or disabled.\r\nDepending on the test run, the default monitoring interval varies.\r\nsyslog is enabled.\r\nCommand Modes\r\nGlobal configuration (config)\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\n12.2(33)SCC\r\nThe command was integrated into Cisco IOS Release 12.2(33)SCC to support Generic\r\nOnline Diagnostics (GOLD) functionality for Cisco UBR10012 Universal Broadband\r\nRouter. The keywords bay , slot , and subslot were added for the Cisco UBR10012\r\nUniversal Broadband Router.\r\nUsage Guidelines\r\nUse these guidelines when scheduling testing:\r\ntest-id -- Enter the show diagnostic content command to display the test ID list .\r\ntest-id-range -- Enter the show diagnostic content command to display the test ID list . Enter the range as\r\nintegers separated by a comma and a hyphen (for example, 1,3-6 specifies test IDs 1, 3, 4, 5, and 6).\r\nhh-- Enter the hours from 1 to 24.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 31 of 111\n\nmm-- Enter the minutes from 1 to 60.\r\ndays-- Enter the number of days between tests.\r\nss-- Enter the seconds from 1 to 60.\r\nms-- Enter the milliseconds from 1 to 1000.\r\nEnter the [no ] diagnostic monitor test {test-id | test-id-range | all } command to enable or disable the specified\r\nhealth monitoring test.\r\nWhen entering the diagnostic monitor module number test {test-id | test-id-range | all } command, observe the\r\nfollowing:\r\nRequired\r\nIsolate network traffic by disabling all connected ports and do not pump test packets during the test.\r\nRemove all modules for testing FIB TCAM and SSRAM memory on the PFC of the supervisor\r\nengine.\r\nReset the system or the test module before putting the system back into the normal operating mode.\r\nRecommended\r\nIf the DFC module is present, remove all modules, and then reboot the system before starting the\r\nmemory test on the central PFC3B of the supervisor engine.\r\nTurn off all background health-monitoring tests on the supervisor engine and the modules using the\r\nno diagnostic monitor module number test {test-id | test-id-range | all } command.\r\nThe FIB TCAM test for central PFC3BXL or PFC3B (on the supervisor engine) takes approximately 4 hours and\r\n30 minutes.\r\nThe FIB TCAM test for the distributed PFC3BXL or PFC3B (on the DFC module) takes approximately 16 hours.\r\nYou can run the FIB TCAM test on multiple DFC3BX modules simultaneously.\r\nCisco UBR10012 Router\r\nThe command syntax to refer a line card or SPAs is different on Cisco UBR10012 Router. The keyword is slot x\r\nfor a full-height line card, slot x/y for a half-height card, and bay x/y for a SPA.\r\nTo monitor a diagnostic test periodically, you first need to configure the hours, minutes, and seconds interval to\r\nrun the diagnostic test using the diagnostic monitor interval command. An error message is displayed, if the\r\ninterval is not configured before enabling the monitoring.\r\nTo store log details for failed tests, execute the diagnostic monitor syslog command. A threshold value to specify\r\nthe maximum count for allowed failures is configured using the diagnostic monitor threshold command. The\r\nfailed test results can be viewed using the show diagnostic results command, after the number of failed test\r\nreaches the maximum number of allowed failures configured using the diagnostic monitor threshold command.\r\nExamples\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 32 of 111\n\nThe following example shows how to run the specified test every 3 days:\r\nRouter(config)# diagnostic monitor interval module 5 test 7 09:07:05 45 3\r\nThe following example shows how to enable the generation of a syslog message when any health-monitoring test\r\nfails:\r\nRouter(config)#\r\ndiagnostic monitor syslog\r\nExamples\r\nThe following example shows a sample output of an error message displayed when monitoring is enabled before\r\nconfiguring the test interval:\r\nRouter(config)# diagnostic monitor bay 1/0 test 2\r\nAug 12 18:04:56.280: %DIAG-3-MONITOR_INTERVAL_ZERO: Bay 1/0: Monitoring interval\r\nis 0. Cannot enable monitoring for Test #2\r\nThe following example shows how to configure the periodic interval for running diagnostic tests on the the router\r\nbefore enabling monitoring:\r\nRouter(config)# diagnostic monitor interval bay 1/0 test 2 06:00:00 100 10\r\nThe following example shows how to enable the diagnostic monitoring on bay 1/0:\r\nRouter(config)# diangostic monitor bay 1/0 test 2\r\nThe following example shows how to enable logging of failed messages to syslog:\r\nRouter(config)# diangostic monitor syslog\r\nThe following example shows how to configure the failure threshold value after which the failed test results are\r\ndisplayed in the command output for show diagnostic results :\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 33 of 111\n\nRouter(config)# diagnostic monitor threshold bay 1/0 test 2 failure count 10\r\nRelated Commands\r\nCommand Description\r\nshow diagnostic\r\ncontent\r\nDisplays test information including test ID, test attributes, and supported coverage test\r\nlevels for each test and for all modules.\r\ndiagnostic ondemand\r\nTo configure the on-demand diagnostics, use the diagnostic ondemand command in privileged EXEC mode.\r\ndiagnostic ondemand {iteration iteration-count | action-on-failure {continue error-count | stop}}\r\nSyntax Description\r\niteration\r\niteration-count\r\nSets the number of times the same test to rerun when the command is issued . The valid\r\nrange for iteration-count is between 1 to 999.\r\naction-on-failure Sets the execution action when a failure is detected.\r\ncontinue Continues testing when a test failure is detected.\r\nstop Stops testing when a test failure is detected.\r\nerror-count\r\n(Optional) Number of errors that are allowed before stopping. This argument is used with\r\nthe continue optio n. The valid range for error-count is from 0 to 65534.\r\nCommand Default\r\nThe default settings are as follows:\r\niteration-count is 1\r\naction-on-error is continue\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 34 of 111\n\nerror-count is 0\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\n12.2(33)SCC\r\nThe command was integrated in this release to support Generic Online Diagnostics (GOLD)\r\nfunctionality for Cisco UBR10012 Universal Broadband Router.\r\nUsage Guidelines\r\nEntering 0 for the error-count sets the number of errors that are allowed to unlimited.\r\nExamples\r\nThe following example shows how to set the ondemand testing iteration count:\r\nRouter#\r\ndiagnostic ondemand iteration 4\r\nRouter#\r\nThe following example shows how to set the execution action when an error is detected:\r\nRouter#\r\ndiagnostic ondemand action-on-failure continue 2\r\nRouter#\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 35 of 111\n\nRelated Commands\r\nCommand Description\r\nshow diagnostic ondemand settings Displays the settings for on-demand diagnostics.\r\ndiagnostic schedule module\r\nTo set the scheduling of test-based diagnostic testing for a specific module or schedule a supervisor engine\r\nswitchover, use the diagnostic schedule module command in global configuration mode. To remove the\r\nscheduling, use the no form of this command.\r\ndiagnostic schedule module {module-number | slot/subslot} test {test-id | all | complete | minimal | non-disruptive | [per-port [port {interface-port-number | port-number-list | all}]]} {on month dd yyyy hh:mm | daily\r\nhh:mm | weekly day-of-week hh:mm}\r\nno diagnostic schedule module {module-number | slot/subslot} test {test-id | all | complete | minimal | non-disruptive | [per-port [port {interface-port-number | port-number-list | all}]]} {on month dd yyyy hh:mm | daily\r\nhh:mm | weekly day-of-week hh:mm}\r\nSyntax Description\r\nmodule-number Specifies the module number.\r\nslot / subslot Specifies the slot number of the active supervisor engine.\r\ntest Specifies the diagnostic test suite attribute.\r\ntest-id\r\nIdentification number for the test to be run; see the “Usage Guidelines” section for\r\nadditional information.\r\nall Runs all diagnostic tests.\r\ncomplete Selects the complete bootup test suite.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 36 of 111\n\nminimal Selects the minimal bootup test suite.\r\nnon-disruptive Selects the nondisruptive test suite.\r\nper-port Selects the per-port test suite.\r\nport (Optional) Specifies the port to schedule testing.\r\ninterface-port-number\r\n(Optional) Port number.\r\nport-number-list (Optional) Range of port numbers, separated by a hyphen.\r\nall (Optional) Specifies all ports.\r\non month dd yyyy hh\r\n: mm\r\nSpecifies the scheduling of a test-based diagnostic task; see the “Usage Guidelines”\r\nsection for formatting guidelines.\r\ndaily hh : mm\r\nSpecifies the daily scheduling of a test-based diagnostic task; see the “Usage\r\nGuidelines” section for formatting guidelines.\r\nweekly day-of-week\r\nhh : mm\r\nSpecifies the weekly scheduling of a test-based diagnostic task; see the “Usage\r\nGuidelines” section for formatting guidelines.\r\nCommand Default\r\nTest-based diagnostic testing for a specific module is not scheduled.\r\nCommand Modes\r\nGlobal configuration (config)\r\nCommand History\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 37 of 111\n\nRelease Modification\r\n12.2(14)SX This command was introduced on the Supervisor Engine 720.\r\n12.2(17b)SXA This command was modified to support scheduled switchover for supervisor engines.\r\n12.2(17d)SXB This command was modified to support the Supervisor Engine 2.\r\n12.2(33)SRA This command was integrated into Cisco IOS Release 12.2(33)SRA.\r\n12.2(33)SRE\r\nThis command was modified. The complete , minimal , non-disruptive , and per-port\r\nkeywords were added.\r\nUsage Guidelines\r\nUse these guidelines when scheduling testing:\r\ntest-id -- Enter the show diagnostic content command to display the test ID list .\r\nmonth-- Spell out the month such as january, february ... december (either uppercase or lowercase\r\ncharacters).\r\ndd-- Enter the day as a two-digit number.\r\nyyyy-- Enter the year as a four-digit number.\r\nhh : mm-- Enter the time as a two-digit number (for a 24-hour clock) for hours:minutes; the colon (: ) is\r\nrequired.\r\nday-of-week-- Spell out the day of the week, such as monday, tuesday... sunday (either uppercase or\r\nlowercase characters).\r\nper-port is not supported when specifying a scheduled switchover.\r\nYou can use the diagnostic schedule module slot / subslot test test-id command to schedule a switchover from the\r\nactive supervisor engine to the standby supervisor engine.\r\nEnter the show diagnostic content module slot / subslot command to display the test ID list and look for the test ID\r\nin the ScheduleSwitchover field.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 38 of 111\n\nYou can specify a periodic switchover (daily or weekly) or a single switchover occurrence at a specific time using\r\nthese commands:\r\ndiagnostic schedule module slot / subslot test test-id on mm dd yyyy hh:mm\r\ndiagnostic schedule module slot / subslot test test-id daily hh:mm\r\ndiagnostic schedule module slot / subslot test test-id weekly day-of-week hh:mm\r\nNote\r\nTo avoid system downtime in the event that the standby supervisor engine cannot switch over the\r\nsystem, Cisco recommends that you schedule a switchover from the standby supervisor engine to the\r\nactive supervisor engine 10 minutes after the switchover occurs.\r\nExamples\r\nThe following example shows how to schedule the diagnostic testing on a specific month, date and time for a\r\nspecific module:\r\nRouter(config)# diagnostic schedule module 1 test 5 on may 27 2010 10:30\r\nThe following example shows how to schedule the diagnostic testing to occur daily at a certain time for a specific\r\nmodule:\r\nRouter(config)# diagnostic schedule module 1 test 5 daily 12:25\r\nThe following example shows how to schedule the diagnostic testing to occur weekly on a certain day for a\r\nspecific module:\r\nRouter(config)# diagnostic schedule module 1 test 5 weekly friday 09:23\r\nRelated Commands\r\nCommand Description\r\nshow diagnostic\r\ncontent\r\nDisplays test information including test ID, test attributes, and supported coverage test\r\nlevels for each test and for all modules.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 39 of 111\n\nCommand Description\r\nshow diagnostic\r\nschedule\r\nDisplays the current scheduled diagnostic tasks.\r\ndiagnostic start\r\nTo run the specified diagnostic test, use the diagnostic start command in privileged EXEC mode.\r\ndiagnostic start module num test {test-id | test-id-range | minimal | complete | basic | per-port | non-disruptive |\r\nall} [port {num | port#-range | all}]\r\ndiagnostic start system test all\r\nCisco UBR10012 Universal Broadband Router\r\ndiagnostic start {bay slot/ bay | slot slot-no} test {test-id | test-id-range | all | complete | minimal | non-disruptive}\r\ndiagnostic start subslot slot/subslot test {test-id | test-id-range | all | complete | minimal | non-disruptive | [per-port [port {num | port#-range | all}]]}\r\nSyntax Description\r\nmodule num Specifies the module number.\r\ntest Specifies a test to run.\r\ntest-id\r\nIdentification number for the test to run. See the Usage Guidelines section for additional\r\ninformation.\r\ntest-id-range\r\nRange of identification numbers for tests to run. See the Usage Guidelines section for\r\nadditional information.\r\nminimal Runs minimal bootup diagnostic tests.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 40 of 111\n\ncomplete Runs complete bootup diagnostic tests.\r\nbasic Runs basic on-demand diagnostic tests.\r\nper-port Runs per-port level tests.\r\nnon-disruptive\r\nRuns the non disruptive health-monitoring tests.\r\nall Runs all diagnostic tests.\r\nport num (Optional) Specifies the interface port number.\r\nport port#\r\nrange\r\n(Optional) Specifies the interface port number range. See the Usage Guidelines section for\r\nadditional information.\r\nport all (Optional) Specifies all ports.\r\nsystem test\r\nall\r\nRuns all disruptive and nondisruptive diagnostic tests at once. All test dependencies are\r\nhandled automatically.\r\nbay slot/bay\r\nIndicates the card slot and bay number where the diagnostic test is executed. The bay\r\nkeyword is used to refer a SPA on the router. The valid range for the slot number is from 1 to\r\n8 and 0 to 3 for the bay number.\r\nslot slot-no\r\nIndicates the slot number of the full-height line card where the diagnostic test is executed.\r\nThe slot keyword is used to refer a full-height line card on the router. The valid range for slot\r\nis from 1 to 8.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 41 of 111\n\nsubslot\r\nslot/sub-slot\r\nIndicates the slot and subslot number of half-height line card where the diagnostic test is\r\nexecuted. The subslot keyword is used to refer a half-height line card on the router. The valid\r\nrange for the slot number is from 1 to 8 and 0 to 1 for the subslot number.\r\nCommand Default\r\nNone\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(17a)SX This command was changed to include the complete and basic keywords.\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\n12.2.(33)SXH This command was changed to include the system test all keywords.\r\n12.2(33)SCC\r\nThe command was integrated in this release to support Generic Online Diagnostics (GOLD)\r\nfunctionality for Cisco UBR10012 Universal Broadband Router. The keywords bay , slot ,\r\nand subslot were added for the Cisco UBR10012 Universal Broadband Router.\r\nUsage Guidelines\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 42 of 111\n\nNote Running all online diagnostic tests disrupts normal system operation. Reset the system after the\r\ndiagnostic start system test all command has completed. Do not insert, remove, or power down line\r\ncards or the supervisor while the system test is running. Do not issue any diagnostic command other\r\nthan the diagnostic stop system test all command while the system test is running. Make sure no\r\ntraffic is running in background.\r\nNote\r\nDo not enter the diagnostic start module x test all command on systems that are configured with a\r\nDFC3A because this command causes the TCAM test to fail.\r\nEnter the show diagnostic content command to display the test ID list .\r\nEnter the test-id-range or port# range as integers separated by a comma and a hyphen (for example, 1,3-6\r\nspecifies test IDs 1, 3, 4, 5, and 6).\r\nUse diagnostic stop command to stop the testing process.\r\nCisco UBR10012 Router\r\nThe command syntax to refer a line card or SPAs is different on Cisco UBR10012 Router. The keyword is slot x\r\nfor a full-height line card, slot x/y for a half-height card, and bay x/y for a SPA.\r\nNote\r\nTo start a diagnostic test on the Cisco UBR10012 Router execute the command diagnostic stop with\r\nthe bay , slot or subslot keyword respectively.\r\nThe GOLD test cases used to poll for system errors in Cisco IOS Software Release 12.2(33)SCC are Low Latency\r\nQueueing (LLQ) drop, Cable Line Card (CLC) memory leak, and Guardian index leak tests.\r\nExamples\r\nThe following example shows how to run the specified diagnostic test at the specified slot:\r\nRouter# diagnostic start module 1 test 5\r\nModule 1:Running test(s) 5 may disrupt normal system operation\r\nDo you want to run disruptive tests? [no] yes\r\n00:48:14:Running OnDemand Diagnostics [Iteration #1] ...\r\n00:48:14:%DIAG-SP-6-TEST_RUNNING:Module 1:Running TestNewLearn{ID=5} ...\r\n00:48:14:%DIAG-SP-6-TEST_OK:Module 1:TestNewLearn{ID=5} has completed successfully\r\n00:48:14:Running OnDemand Diagnostics [Iteration #2] ...\r\n00:48:14:%DIAG-SP-6-TEST_RUNNING:Module 1:Running TestNewLearn{ID=5} ...\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 43 of 111\n\n00:48:14:%DIAG-SP-6-TEST_OK:Module 1:TestNewLearn{ID=5} has completed successfully\r\nRouter#\r\nThis example shows how to start all online diagnostic tests:\r\nRouter# diagnostic start system test all\r\n*************************************************************************\r\n* WARNING: *\r\n* 'diagnostic start system test all' will disrupt normal system *\r\n* operation. The system requires RESET after the command *\r\n* 'diagnostic start system test all' has completed prior to *\r\n* normal use. *\r\n* *\r\n* IMPORTANT: *\r\n* 1. DO NOT INSERT, OIR, or POWER DOWN Linecards or *\r\n* Supervisor while system test is running. *\r\n* *\r\n* 2. DO NOT ISSUE ANY DIAGNOSTIC COMMAND except *\r\n* \"diagnostic stop system test all\" while system test *\r\n* is running. *\r\n* *\r\n* 3. PLEASE MAKE SURE no traffic is running in background. *\r\n*************************************************************************\r\nDo you want to continue? [no]:\r\nExamples\r\nThe following example shows how to run a diagnostic test with test id 2 on a SPA:\r\nubr-122s-1# diagnostic start bay 1/0 test 2\r\nubr-122s-1#\r\nAug 5 09:24:42.019: %DIAG-6-TEST_RUNNING: Bay 1/0: Running TestModenaLLQDrops{I\r\nD=2} ...\r\nAug 5 09:24:42.019: %DIAG-6-TEST_OK: Bay 1/0: TestModenaLLQDrops{ID=2} has comp\r\nleted successfully\r\nRelated Commands\r\nCommand Description\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 44 of 111\n\nCommand Description\r\ndiagnostic schedule Sets the diagnostic test schedule for a particular bay, slot, or subslot.\r\nshow diagnostic description Provides the description for the diagnostic tests.\r\ndiagnostic stop Runs the specified diagnostic test.\r\nshow diagnostic content module Displays the available diagnostic tests.\r\ndiagnostic bootup level Configures the diagnostic bootup level.\r\ndiagnostic event-log size Modifies the diagnostic event-log size dynamically.\r\ndiagnostic monitor Configures the health-monitoring diagnostic testing.\r\ndiagnostic ondemand Configures the on-demand diagnostics.\r\nshow diagnostic bootup Displays the configured diagnostics level at bootup.\r\nshow diagnostic events Displays the diagnostic event log.\r\nshow diagnostic ondemand settings Displays the settings for the on-demand diagnostics.\r\nshow diagnostic result Displays the diagnostic test results for a module.\r\nshow diagnostic schedule Displays the current scheduled diagnostic tasks.\r\nshow diagnostic status Displays the running diagnostics tests.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 45 of 111\n\ndiagnostic stop\r\nTo stop the testing process, use the diagnostic stop command in privileged EXEC mode.\r\ndiagnostic stop module num\r\nCisco UBR10012 Universal Broadband Router\r\ndiagnostic stop {bay slot/ bay | slot slot-no | subslot slot/ subslot}\r\nSyntax Description\r\nmodule num Module number.\r\nbay slot/bay\r\nIndicates the card slot and bay number of the SPA for which the diagnostic test has stopped.\r\nThe bay keyword is used to refer a SPA on the router. The valid range for the slot number is\r\nfrom 1 to 8 and 0 to 3 for the bay number.\r\nslot slot-no\r\nIndicates the slot number of full height line card for which the diagnostic test has to be\r\nstopped. The slot keyword is used to refer a full-height line card on the router. Valid range\r\nfor the slot is from 1 to 8.\r\nsubslot\r\nslot/subslot\r\nIndicates the slot and subslot number of half-height line card for which the diagnostic test\r\nhas to be stopped. The subslot keyword is used to refer a half-height line card on the router.\r\nThe valid range for the slot number is from 1 to 8 and 0 to 1 for the subslot number.\r\nCommand Default\r\nNone\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/D_through_E.html#wp3557227463\r\nPage 46 of 111\n\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\n12.2(33)SCC\r\nThe command was integrated in this release to support Generic Online Diagnostics (GOLD)\r\nfunctionality for Cisco UBR10012 Universal Broadband Router. The keywords bay , slot ,\r\nand subslot were added for the Cisco UBR10012 Universal Broadband Router.\r\nUsage Guidelines\r\nUse the diagnostic start command to start the testing process.\r\nCisco UBR10012 Router\r\nThe command syntax to refer a line card or SPAs is different on Cisco UBR10012 Router. The keyword is slot x\r\nfor a full-height line card, slot x/y for a half-height card, and bay x/y for a SPA.\r\nNote\r\nTo stop a diagnostic test on the Cisco UBR10012 Router execute the command diagnostic stop with\r\nthe bay , slot or subslot keyword respectively.\r\nThe GOLD test cases used to poll for system errors in Cisco IOS Software Release 12.2(33)SCC are Low Latency\r\nQueueing (LLQ) drop, Cable Line Card (CLC) memory leak, and line card index leak tests.\r\nExamples\r\nThis example shows how to stop the diagnostic test process:\r\nRouter# diagnostic stop module 3\r\nRouter#\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 47 of 111\n\nThis example shows how to stop the diagnostic test process for subslot 5/0 on the Cisco UBR10012 Universal\r\nBroadband Router:\r\nRouter# diagnostic stop subslot 5/0\r\nRouter#\r\nRelated Commands\r\nCommand Description\r\ndiagnostic schedule Sets the diagnostic test schedule for a particular bay, slot, or subslot.\r\nshow diagnostic description Provides the description for the diagnostic tests.\r\ndiagnostic start Stops the specified diagnostic test.\r\nshow diagnostic content module Displays the available diagnostic tests.\r\ndiagnostic bootup level Configures the diagnostic bootup level.\r\ndiagnostic event-log size Modifies the diagnostic event-log size dynamically.\r\ndiagnostic monitor Configures the health-monitoring diagnostic testing.\r\ndiagnostic ondemand Configures the on-demand diagnostics.\r\nshow diagnostic bootup Displays the configured diagnostics level at bootup.\r\nshow diagnostic events Displays the diagnostic event log.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 48 of 111\n\nCommand Description\r\nshow diagnostic ondemand settings Displays the settings for the on-demand diagnostics.\r\nshow diagnostic result Displays the diagnostic test results for a module.\r\nshow diagnostic schedule Displays the current scheduled diagnostic tasks.\r\nshow diagnostic status Displays the running diagnostics tests.\r\ndir\r\nTo display a list of files on a file system, use the dir command in EXEC, privileged EXEC, or diagnostic mode.\r\ndir [/ all] [/ recursive] [all-filesystems] [filesystem: ] [file-url]\r\nSyntax Description\r\n/all (Optional) Lists deleted files, undeleted files, and files with errors.\r\n/recursive (Optional) Lists files recursively.\r\nall-filesystems\r\n(Optional) Lists all files in all file systems on the router.\r\nfilesystem: (Optional) File system or directory containing the files to list, followed by a colon.\r\nfile-url\r\n(Optional) The name of the files to display on a specified device. The files can be of any type.\r\nYou can use wildcards in the filename. A wildcard character (*) matches all patterns. Strings\r\nafter a wildcard are ignored.\r\nCommand Default\r\nWhen you omit the /all keyword, the Cisco IOS software displays only undeleted files.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 49 of 111\n\nCommand Modes\r\nUser EXEC (\u003e) Privileged EXEC (#) Diagnostic (diag)\r\nCommand History\r\nRelease Modification\r\n11.0 This command was introduced.\r\n12.3\r\nThis command was modified. A timestamp that shows the offset from Coordinated\r\nUniversal Time (UTC) was added to the dir command display.\r\n12.3(14)T\r\nThis command was modified. The usbflash 0 9 : and usbtoken 0 9 : options were\r\nadded as available file systems.\r\n12.2(33)SRA This command was integrated into Cisco IOS Release 12.2(33)SRA.\r\n12.4(11)T\r\nThis command was modified. Support for this command was implemented on the\r\nCisco 7200VXR NPE-G2 platform.\r\nCisco IOS XE\r\nRelease 2.1\r\nThis command was introduced on the Cisco ASR 1000 Series Routers, and the\r\nfollowing enhancements were introduced:\r\nThe command was made available in diagnostic mode.\r\nThe /recursive option was introduced.\r\nThe file systems available with the Cisco ASR 1000 Series Routers became\r\navailable as filesystem : options.\r\n15.0(1)M This command was modified. The output modifier was added.\r\n15.0(01)XO\r\nNote added to explain different byte and usage calculations for show file systems and\r\ndir commands on cat4000 series routers.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 50 of 111\n\nUsage Guidelines\r\nUse the show file systems command to display more details about the files in a particular file system.\r\nNote\r\nAs of release 15.0(01)XO, on cat4000 series routers, the show (flash file system) and dir will display\r\nslightly different byte count and usage information for the same file system. This is due to slight\r\ndifference in how IOS computes these figures for this platform.\r\nYou can use the Cisco IOS software output modifiers to filter the output of the dir command, to display only those\r\nlines you are interested in.\r\nThe output modifier feature is invoked by using the pipe symbol (| ). To use this feature, enter the dir command as\r\nnormal but add a space and the pipe symbol at the end of the command line. Then add one of the keywords shown\r\nin the table below.\r\nTable 2. Using Output Modifiers\r\nCommand Purpose\r\nappend regular\r\nexpression\r\nAppends redirected output to URL (only to the URLs supporting the append\r\noperation).\r\nbegin regular\r\nexpression\r\nDisplays the first line that matches the regular expression, and then all other lines\r\nthat follow that line.\r\ninclude regular\r\nexpression\r\nDisplays all lines that match the regular expression.\r\nexclude regular\r\nexpression\r\nDisplays all lines except those that match the regular expression.\r\nformat regular\r\nexpression\r\nFormats the output using the specification file.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 51 of 111\n\nCommand Purpose\r\nredirect regular\r\nexpression\r\nRedirects the output to the URL.\r\nsection regular\r\nexpression\r\nFilters a section of the output.\r\ntee regular expression Copies output to the URL.\r\nNote\r\nThe append , redirect and tee keywords do not support rcp in the display.\r\nExamples\r\nThe following is sample output from the dir command:\r\nRouter# dir slot0:\r\nDirectory of slot0:/\r\n1 -rw- 4720148 Dec 29 2003 17:49:36 -08:00 hampton/nitro/c7200-j-mz\r\n 2 -rw- 4767328 Jan 02 2004 18:42:53 -08:00 c7200-js-mz\r\n 5 -rw- 639 Jan 03 2004 12:09:32 -08:00 rally\r\n 7 -rw- 639 Jan 03 2004 12:37:13 -08:00 the_time\r\n20578304 bytes total (3104544 bytes free)\r\nThe following is sample output from the dir /all command:\r\nRouter# dir /all slot0:\r\nDirectory of slot0:/\r\n1 -rw- 4720148 Dec 15 2003 17:49:36 -08:00 hampton/nitro/c7200-j-mz\r\n 2 -rw- 4767328 Jan 02 2004 18:42:53 -08:00 c7200-js-mz\r\n 3 -rw- 7982828 Jan 02 2004 18:48:14 -08:00 [rsp-jsv-mz]\r\n 4 -rw- 639 Jan 03 2004 12:09:17 -08:00 the_time]\r\n 5 -rw- 639 Jan 03 1994 12:09:32 -08:00 rally\r\n 6 -rw- 639 Jan 03 1994 12:37:01 -08:00 [the_time]\r\n 7 -rw- 639 Jan 03 1994 12:37:13 -08:00\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 52 of 111\n\nThe table below describes the significant fields shown in the displays.\r\nTable 3. dir Field Descriptions\r\nField Description\r\n1 Index number of the file.\r\n-rw-Permissions. The file can be any or all of the following:\r\nd--directory\r\nr--readable\r\nw--writable\r\nx--executable\r\n4720148 Size of the file, in bytes.\r\nDec 15 2003 17:49:36 Last modification date.\r\n-08:00\r\nConversion to local time in hours from Coordinated Universal Time (UTC). In the\r\nexample, -08:00 indicates that the given time is 8 hours behind UTC or Pacific\r\nStandard Time (PST).\r\nhampton/nitro/c7200-j-mz\r\nFilename. Deleted files are indicated by square brackets around the filename.\r\nThe following example shows how to use the output modifier feature with the exclude keyword and regular\r\nexpression. The table above describes the significant fields shown in the output.\r\nRoutwe# dir | exclude asr\r\nDirectory of bootflash:/\r\n 12 drwx 4096 Jan 5 2005 01:34:50 +00:00 lost+found\r\n59265 drwx 4096 Apr 20 2004 01:51:10 +00:00 .installer\r\n14817 drwx 4096 Apr 20 2004 01:54:37 +00:00 .ssh\r\n88897 drwx 4096 Jan 7 2005 22:13:26 +00:00 .prst_sync\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 53 of 111\n\nRelated Commands\r\nCommand Description\r\ncd Changes the default directory or file system.\r\ndelete Deletes a file on a Flash memory device.\r\nundelete Recovers a file marked “deleted” on a Class A or Class B flash file system.\r\ndisable\r\nTo exit privileged EXEC mode and return to user EXEC mode, or to exit to a lower privilege level, enter the\r\ndisable command in EXEC, privileged EXEC, or diagnostic mode.\r\ndisable [privilege-level]\r\nSyntax Description\r\nprivilege-level (Optional) Specific privilege level (other than user EXEC mode).\r\nCommand Modes\r\nEXEC (\u003e) Privileged EXEC (#) Diagnostic (diag)\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\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 54 of 111\n\nRelease Modification\r\nCisco IOS XE\r\nRelease 2.1\r\nThis command was introduced on the Cisco ASR 1000 Series Routers, and became\r\navailable in diagnostic mode.\r\nUsage Guidelines\r\nUp to 16 security levels can be configured using Cisco IOS software. If such levels are configured on a system,\r\nusing this command with the privilege-level option allows you to exit to a lower security level. If a level is not\r\nspecified, the user will exit to the user EXEC mode, which is the default.\r\nNote\r\nFive EXEC commands are associated with privilege level 0: disable , enable , exit , help , and logout .\r\nIf you configure a privilege level greater than 0, these five commands will not be included in the\r\ncommand set for that privilege level.\r\nExamples\r\nIn the following example, the user enters privileged EXEC mode using the enable command, then exits back to\r\nuser EXEC mode using the disable command. Note that the prompt for user EXEC mode is \u003e, and the prompt for\r\nprivileged EXEC mode is #.\r\nRouter\u003e enable\r\nPassword: \u003cletmein\u003e\r\nRouter# disable\r\nRouter\u003e\r\nRelated Commands\r\nCommand Description\r\nenable Enables higher privilege level access, such as privileged EXEC mode.\r\ndisconnect-character\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 55 of 111\n\nTo define a character to disconnect a session, use the disconnect-character command in line configuration mode.\r\nTo remove the disconnect character, use the no form of this command.\r\ndisconnect-character ascii-number\r\nno disconnect-character\r\nSyntax Description\r\nascii-number Decimal representation of the session disconnect character.\r\nCommand Default\r\nNo disconnect character is defined.\r\nCommand Modes\r\nLine 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\nUsage Guidelines\r\nSee the “ASCII Character Set and Hex Values” appendix for a list of ASCII characters.\r\nThe Break character is represented by zero; NULL cannot be represented.\r\nTo use the session-disconnect character in normal communications, precede it with the escape character.\r\nExamples\r\nThe following example defines the disconnect character for virtual terminal line 4 as Escape, which is decimal\r\ncharacter 27:\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 56 of 111\n\nRouter(config)# line vty 4\r\nRouter(config-line)# disconnect-character 27\r\ndispatch-character\r\nTo define a character that causes a packet to be sent, use the dispatch-character command in line configuration\r\nmode. To remove the definition of the specified dispatch character, use the no form of this command.\r\ndispatch-character ascii-number1 [ascii-number2. . . ]\r\nno dispatch-character ascii-number1 [ascii-number2. . . ]\r\nSyntax Description\r\nascii-number1\r\nDecimal representation of the desired dispatch character.\r\nascii-number2 . . .(Optional) Additional decimal representations of characters. This syntax indicates that you\r\ncan define any number of characters as dispatch characters.\r\nCommand Default\r\nNo dispatch character is defined.\r\nCommand Modes\r\nLine 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\nUsage Guidelines\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 57 of 111\n\nSee the “ASCII Character Set and Hex Values” appendix for a list of ASCII characters.\r\nThe dispatch-character command defines one or more dispatch characters that cause a packet to be sent even if the\r\ndispatch timer has not expired. Use of a dispatch character causes the Cisco IOS software to attempt to buffer\r\ncharacters into larger-sized packets for transmission to the remote host.\r\nEnable the dispatch-character command from the session that initiates the connection, not from the incoming side\r\nof a streaming Telnet session.\r\nThis command can take multiple arguments, so you can define any number of characters as dispatch characters.\r\nExamples\r\nThe following example defines the Return character (decimal 13) as the dispatch character for virtual terminal line\r\n(vty) line 4:\r\nRouter(config)# line vty 4\r\nRouter(config-line)# dispatch-character 13\r\nRelated Commands\r\nCommand Description\r\ndispatch-machine\r\nSpecifies an identifier for a TCP packet dispatch state machine on a particular\r\nline.\r\ndispatch-timeout Sets the character dispatch timer.\r\nstate-machine Specifies the transition criteria for the state of a particular state machine.\r\nterminal dispatch-character\r\nDefines a character that causes a packet to be sent for the current session.\r\ndispatch-machine\r\nTo specify an identifier for a TCP packet dispatch state machine on a particular line, use the dispatch-machine\r\ncommand in line configuration mode. To disable a state machine on a particular line, use the no form of this\r\ncommand.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 58 of 111\n\ndispatch-machine name\r\nno dispatch-machine\r\nSyntax Description\r\nname Name of the state machine that determines when to send packets on the asynchronous line.\r\nCommand Default\r\nNo dispatch state machine identifier is defined.\r\nCommand Modes\r\nLine 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\nUsage Guidelines\r\nWhen the dispatch-timeout command is specified, a packet being built will be sent when the timer expires, and the\r\nstate will be reset to zero.\r\nAny dispatch characters specified using the dispatch-character command are ignored when a state machine is also\r\nspecified.\r\nIf a packet becomes full, it will be sent regardless of the current state, but the state will not be reset. The packet\r\nsize depends on the traffic level on the asynchronous line and the dispatch-timeout value. There is always room\r\nfor 60 data bytes. If the dispatch-timeout value is greater than or equal to 100 milliseconds, a packet size of 536\r\n(data bytes) is allocated.\r\nExamples\r\nThe following example specifies the name linefeed for the state machine:\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 59 of 111\n\nRouter(config)# state-machine linefeed 0 0 9 0\r\nRouter(config)# state-machine linefeed 0 11 255 0\r\nRouter(config)# state-machine linefeed 0 10 10 transmit\r\nRouter(config)# line 1\r\nRouter(config-line)# dispatch-machine linefeed\r\nRelated Commands\r\nCommand Description\r\ndispatch-character Defines a character that causes a packet to be sent.\r\ndispatch-timeout Sets the character dispatch timer.\r\nstate-machine Specifies the transition criteria for the state of a particular state machine.\r\ndispatch-timeout\r\nTo set the character dispatch timer, use the dispatch-timeout command in line configuration mode. To remove the\r\ntimeout definition, use the no form of this command.\r\ndispatch-timeout milliseconds\r\nno dispatch-timeout\r\nSyntax Description\r\nmilliseconds\r\nInteger that specifies the number of milliseconds (ms) that the Cisco IOS software waits after\r\nputting the first character into a packet buffer before sending the packet. During this interval,\r\nmore characters can be added to the packet, which increases the processing efficiency of the\r\nremote host.\r\nCommand Default\r\nNo dispatch timeout is defined.\r\nCommand Modes\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 60 of 111\n\nLine 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\nUsage Guidelines\r\nUse this command to increase the processing efficiency for the remote host.\r\nThe dispatch-timeout line configuration command causes the software to buffer characters into packets for\r\ntransmission to the remote host. The Cisco IOS software sends a packet a specified amount of time after the first\r\ncharacter is put into the buffer. You can use the dispatch-timeout and dispatch-character line configuration\r\ncommands together. In this case, the software dispatches a packet each time the dispatch character is entered, or\r\nafter the specified dispatch timeout interval, depending on which condition is met first.\r\nNote\r\nThe system response time might appear intermittent if the timeout interval is greater than 100\r\nmilliseconds and remote echoing is used. For lines with a reverse-Telnet connection, use a dispatch-timeout value less than 10 milliseconds.\r\nExamples\r\nThe following example sets the dispatch timer to 80 milliseconds for virtual terminal line (vty) lines 0 through 4:\r\nRouter(config)# line vty 0 4\r\nRouter(config-line)# dispatch-timeout 80\r\nRelated Commands\r\nCommand Description\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 61 of 111\n\nCommand Description\r\nbuffer-length Specifies the maximum length of data streams forwarded on a line.\r\ndispatch-character Defines a character that causes a packet to be sent.\r\ndispatch-machine\r\nSpecifies an identifier for a TCP packet dispatch state machine on a particular\r\nline.\r\nstate-machine Specifies the transition criteria for the state of a particular state machine.\r\nterminal dispatch-timeout\r\nSets the character dispatch timer for the current session.\r\ndo\r\nTo execute user EXEC or privileged EXEC commands from global configuration mode or other configuration\r\nmodes or submodes, use the do command in any configuration mode.\r\ndo command\r\nSyntax Description\r\ncommand The user EXEC or privileged EXEC command to be executed.\r\nCommand Default\r\nA user EXEC or privileged EXEC command is not executed from a configuration mode.\r\nCommand Modes\r\nAll configuration modes\r\nCommand History\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 62 of 111\n\nRelease Modification\r\n12.2(8)T This command was introduced.\r\n12.2(14)S This command was integrated into Cisco IOS Release 12.2(14)S.\r\n12.2(14)SX Support for this command was added for the Supervisor Engine 720.\r\n12.2(17a)SX This command was changed to support the copy command restriction.\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\n15.1(3)T This command was integrated into Cisco IOS Release 15.1(3)T.\r\nUsage Guidelines\r\nUse this command to execute user EXEC or privileged EXEC commands (such as show , clear , and debug\r\ncommands) while configuring your routing device. After the EXEC command is executed, the system will return\r\nto the configuration mode you were using.\r\nTip\r\nThis command can be useful for saving your configuration to the startup-config file without having to\r\nreturn to the user EXEC mode or privileged EXEC mode (do copy running-config startup-config ) or\r\nfor checking the status of a feature (using a do show command) while configuring the feature.\r\nCaution\r\nDo not enter the do command in user EXEC mode or privileged EXEC mode. Interruption of\r\nservice might occur.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 63 of 111\n\nYou cannot use the do command to execute the configure terminal c ommand because entering the configure\r\nterminal command changes the user EXEC mode or privileged EXEC mode to the global configuration mode.\r\nYou cannot use the do command to execute copy or write c ommands in the global configuration or any other\r\nconfiguration mode or submode.\r\nExamples\r\nThe following example shows how to enter the show interfaces serial privileged EXEC command from within\r\nglobal configuration mode:\r\nRouter(config)# do show interfaces serial 3/0\r\nSerial3/0 is up, line protocol is up\r\n Hardware is M8T-RS232\r\n MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, rely 255/255, load 1/255\r\n Encapsulation HDLC, loopback not set, keepalive set (10 sec)\r\n Last input never, output 1d17h, output hang never\r\n Last clearing of “show interface” counters never\r\n.\r\n.\r\n.\r\nThe following example shows how to enter the clear vpdn tunnel user EXEC or privileged EXEC command from\r\nwithin VPDN configuration mode:\r\nRouter(config-vpdn)# do clear vpdn tunnel\r\nRelated Commands\r\nCommand Description\r\nclear vpdn tunne l Shuts down a specified VPDN tunnel and all sessions within the tunnel.\r\nconfigure terminal Enters global configuration mode.\r\ncopy Copies any file from a source to a destination.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 64 of 111\n\nCommand Description\r\nshow interfaces Displays statistics for all interfaces configured on the router or access server.\r\nwrite core Tests the configuration of a core dump setup.\r\ndownward-compatible-config\r\nTo generate a configuration that is compatible with an earlier Cisco IOS release, use the downward-compatible-config command in global configuration mode. To disable this function, use the no form of this command.\r\ndownward-compatible-config version\r\nno downward-compatible-config\r\nSyntax Description\r\nversion\r\nCisco IOS release number, not earlier than Release 10.2.\r\nNote\r\n \r\nYou must have a period (. ) in the version number. For example, 12.4.\r\nCommand Default\r\nThe configuration is not compatible with earlier Cisco IOS releases.\r\nCommand Modes\r\nGlobal configuration (config)\r\nCommand History\r\nRelease Modification\r\n11.1 This command was introduced.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 65 of 111\n\nRelease Modification\r\n12.2(33)SRA This command was integrated into Cisco IOS Release 12.2(33)SRA.\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\nIn Cisco IOS Release 10.3, IP access lists changed format. Use the downward-compatible-config command to\r\nregenerate a configuration in a format prior to Release 10.3 if you will downgrade from your software version to\r\nversion 10.2 or 10.3. The earliest version value this command accepts is 10.2.\r\nWhen this command is configured, the router attempts to generate a configuration that is compatible with the\r\nspecified version. Note that this command affects only IP access lists.\r\nUnder some circumstances, the software might not be able to generate a fully backward-compatible configuration.\r\nIn such a case, the software issues a warning message.\r\nExamples\r\nThe following example shows how to generate a configuration file compatible with Cisco IOS Release 10.2 access\r\nlists:\r\nRouter(config)# downward-compatible-config 10.2\r\nRelated Commands\r\nCommand Description\r\naccess-list (extended) Provides extended access lists that allow more detailed access lists.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 66 of 111\n\nCommand Description\r\naccess-list (standard) Defines a standard XNS access list.\r\nediting\r\nTo reen able Cisco IOS enhanced editing features for a particular line after they have been disabled, use the\r\nediting command in line configuration mode. To disable these features, use the no form of this command.\r\nediting\r\nno editing\r\nSyntax Description\r\nThis command has no arguments or keywords.\r\nCommand Default\r\nEnabled\r\nCommand Modes\r\nLine 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\nUsage Guidelines\r\nEnhanced editing features are enabled by default. However, there may be situations in which you need to disable\r\nthese features. The no form of this command disables these enhanced editing features, and the plain form of the\r\ncommand can be used to reenable these features.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 67 of 111\n\nThe table below provides a description of the keys used to enter and edit commands when the editing features are\r\nenabled. Ctrl indicates the Control key, which must be pressed simultaneously with its associated letter key. Esc\r\nindicates the Escape key, which must be pressed first, followed by its associated letter key. A comma is used in the\r\nfollowing table to indicate a key sequence (the comma key should not be pressed). Keys are not case sensitive.\r\nMany letters used for CLI navigation and editing were chosen to provide an easy way of remembering their\r\nfunctions. In the following table, characters are bolded in the “Function Summary” column to indicate the relation\r\nbetween the letter used and the function.\r\nTable 4. Command Editing Keys and Functions\r\nKeys\r\nFunction\r\nSummary\r\nFunction Details\r\nTab\r\nComplete\r\ncommand\r\nCompletes a partial command name entry. When you enter a unique set of\r\ncharacters and press the Tab key, the system completes the command name.\r\nIf you enter a set of characters that could indicate more than one command,\r\nthe system beeps to indicate an error. To view the commands which match\r\nthe set of characters you have entered, enter a question mark (?)\r\nimmediately following the partial command (no space). The CLI will then\r\nlist the commands that begin with that string.\r\nReturn (at the\r\ncommand\r\nline)\r\nExecute Executes the command.\r\nReturn (at the\r\n--More--\r\nprompt)\r\nContinue Displays the next line of output.\r\nSpace Bar (at\r\nthe --More--\r\nprompt)\r\nContinue\r\nDisplays the next screen of output. The amount of output you see will\r\ndepend on the screen depth setting of your terminal.\r\nDelete or\r\nBackspace\r\nBackspace Erases the character to the left of the cursor.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 68 of 111\n\nKeys\r\nFunction\r\nSummary\r\nFunction Details\r\nLeft Arrow1\r\nor Ctrl-B\r\nB ack\r\ncharacter\r\nMoves the cursor one character to the left. When you enter a command that\r\nextends beyond a single line, you can press the Left Arrow or Ctrl-B keys\r\nrepeatedly to scroll back toward the system prompt and verify the\r\nbeginning of the command entry.\r\nRight Arrow1\r\nor Ctrl-F\r\nF orward\r\ncharacter\r\nMoves the cursor one character to the right.\r\nEsc, B B ack word Moves the cursor back one word.\r\nEsc, F\r\nF orward\r\nword\r\nMoves the cursor forward one word.\r\nCtrl-A\r\nBeginning of\r\nline\r\nMoves the cursor to the beginning of the line.\r\nCtrl-E E nd of line Moves the cursor to the end of the command line.\r\nCtrl-D\r\nD elete\r\ncharacter\r\nDeletes the character at the cursor.\r\nEsc, D\r\nD elete next\r\nword\r\nDeletes from the cursor to the end of the word.\r\nCtrl-W\r\nDelete\r\nprevious w\r\nord\r\nDeletes the word to the left of the cursor.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 69 of 111\n\nKeys\r\nFunction\r\nSummary\r\nFunction Details\r\nCtrl-K\r\nDelete line\r\nforward\r\nDeletes all characters from the cursor to the end of the command line.\r\nCtrl-U or\r\nCtrl-X\r\nDelete line\r\nbackward\r\nDeletes all characters from the cursor back to the beginning of the\r\ncommand line.\r\nCtrl-T\r\nT ranspose\r\ncharacters\r\nTransposes the character to the left of the cursor with the character located\r\nat the cursor.\r\nCtrl-R or\r\nCtrl-L\r\nR edisplay l\r\nine\r\nRedisplays the system prompt and command line.\r\nCtrl-V or\r\nEsc, Q\r\nIgnore\r\nediting\r\nInserts a code to indicate to the system that the keystroke immediately\r\nfollowing should be treated as a command entry, not as an editing key.\r\nUp Arrow1\r\nor Ctrl-P\r\nP revious\r\ncommand\r\nRecalls commands in the history buffer, beginning with the most recent\r\ncommand. Repeat the key sequence to recall successively older commands.\r\nDown\r\nArrow1 or\r\nCtrl-N (next)\r\nN ext\r\ncommand\r\nReturns to more recent commands in the history buffer (after recalling\r\ncommands with the Up Arrow or Ctrl-P). Repeat the key sequence to recall\r\nsuccessively more recent commands.\r\nCtrl-Y\r\nRecall last\r\ndeleted\r\ncommand\r\nRecalls the most recent entry in the delete buffer. The delete buffer contains\r\nthe last ten items you have deleted or cut. Ctrl-Y can be used in conjunction\r\nwith Esc Y.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 70 of 111\n\nKeys\r\nFunction\r\nSummary\r\nFunction Details\r\nEsc, Y\r\nRecall next\r\ndeleted\r\ncommand\r\nRecalls the next entry in the delete buffer. The delete buffer contains the\r\nlast ten items you have deleted. Press Ctrl-Y first to recall the most recent\r\nentry. Then press Esc Y up to nine times to recall the remaining entries in\r\nthe buffer. If you bypass an entry, continue to press Esc Y to cycle back to\r\nit.\r\nEsc, C\r\nC apitalize\r\nword\r\nCapitalizes the word from the cursor to the end of the word.\r\nEsc, U\r\nMake word\r\nu ppercase\r\nChanges all letters from the cursor to the next space on the line appear in\r\nuppercase letters.\r\nEsc, L\r\nMake word l\r\nowercase\r\nChanges the word to lowercase from the cursor to the end of the word.\r\n1\r\n The arrow keys function only with ANSI-compatible terminals.\r\nExamples\r\nIn the following example, enhanced editing mode is disabled on line 3:\r\nRouter(config)# line 3\r\nRouter(config-line)# no editing\r\nRelated Commands\r\nCommand Description\r\nterminal editing Controls CLI enhanced editing feature for the current terminal session.\r\nenable\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 71 of 111\n\nTo change the privilege level for a CLI session or to use a CLI view for a CLI session, use the enable command in\r\neither user EXEC, privileged EXEC, or diagnostic mode.\r\nenable [privilege-level] [view [view-name] ]\r\nSyntax Description\r\nprivilege-level\r\n(Optional) Privilege level at which to log in.\r\nview\r\n(Optional) Enters into root view, which enables users to configure CLI views.\r\nNote\r\n \r\nThis keyword is required if you want to configure a CLI view.\r\nview-name\r\n(Optional) Enters or exits a specified command-line interface (CLI) view. This keyword can\r\nbe used to switch from one CLI view to another CLI view.\r\nCommand Default\r\nPrivilege-level 15 (privileged EXEC)\r\nCommand Modes\r\nUser EXEC (\u003e)\r\nPrivileged EXEC (#)\r\nDiagnostic Mode (diag)\r\nCommand History\r\nRelease Modification\r\n10.0 This command was introduced.\r\n12.3(7)T The view keyword and view-name argument were added.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 72 of 111\n\nRelease Modification\r\n12.2(33)SRA This command was integrated into Cisco IOS Release 12.2(33)SRA.\r\n12.2(33)SRB\r\nThe view keyword and view-name argument were integrated into Cisco IOS Release\r\n12.2(33)SRB.\r\n12.2SX\r\nThis command is supported in the Cisco IOS Release 12.2SX train. Support in a\r\nspecific 12.2SX release of this train depends on your feature set, platform, and platform\r\nhardware.\r\n12.2(33)SB This command was integrated into Cisco IOS Release 12.2(22)SB.\r\nCisco IOS XE\r\nRelease 2.1\r\nThis command became available on the ASR 1000 Series Routers, and became\r\navailable in diagnostic mode for the first time.\r\nUsage Guidelines\r\nBy default, using the enable command without the privilege-level argument in user EXEC mode causes the router\r\nto enter privileged EXEC mode (privilege-level 15).\r\nEntering privileged EXEC mode enables the use of privileged commands. Because many of the privileged\r\ncommands set operating parameters, privileged access should be password-protected to prevent unauthorized use.\r\nIf the system administrator has set a password with the enable password global configuration command, you are\r\nprompted to enter the password before being allowed access to privileged EXEC mode. The password is case\r\nsensitive.\r\nIf an enable password has not been set, only enable mode can be accessed through the console connection.\r\nSecurity levels can be set by an administrator using the enable password and privilege level commands. Up to 16\r\nprivilege levels can be specified, using the numbers 0 through 15. Using these privilege levels, the administrator\r\ncan allow or deny access to specific commands. Privilege level 0 is associated with user EXEC mode, and\r\nprivilege level 15 is associated with privileged EXEC mode.\r\nFor more information on defined privilege levels, see the Cisco IOSSecurity Configuration Guide and the Cisco\r\nIOS Security Command Reference publications.\r\nIf a level is not specified when entering the enable command, the user will enter the default mode of privileged\r\nEXEC (level 15).\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 73 of 111\n\nAccessing a CLI View\r\nCLI views restrict user access to specified CLI and configuration information. To configure and access CLI views,\r\nusers must first enter into root view, which is accomplished via the enable view command (without the view-name\r\nargument). Thereafter, users are prompted for a password, which is the same password as the privilege level 15\r\npassword.\r\nThe view-name argument is used to switch from one view to another view.\r\nTo prevent dictionary attacks, a user is prompted for a password even if an incorrect view name is given. The user\r\nis denied access only after an incorrect view name and password are given.\r\nExamples\r\nIn the following example, the user enters privileged EXEC mode (changes to privilege-level 15) by using the\r\nenable command without a privilege-level argument. The system prompts the user for a password before allowing\r\naccess to the privileged EXEC mode. The password is not printed to the screen. The user then exits back to user\r\nEXEC mode using the disable command. Note that the prompt for user EXEC mode is the greater than symbol\r\n(\u003e), and the prompt for privileged EXEC mode is the number sign (#).\r\nRouter\u003e enable\r\nPassword: \u003cletmein\u003e\r\nRouter# disable\r\nRouter\u003e\r\nThe following example shows which commands are available inside the CLI view “first” after the user has logged\r\ninto this view:\r\nRouter# enable view first\r\nPassword:\r\n00:28:23:%PARSER-6-VIEW_SWITCH:successfully set to view 'first'.\r\nRouter# ?\r\nExec commands:\r\n configure Enter configuration mode\r\n enable Turn on privileged commands\r\n exit Exit from the EXEC\r\n show Show running system information\r\nRouter# show ?\r\n ip IP information\r\n parser Display parser information\r\n version System hardware and software status\r\nRouter# show ip ?\r\n \r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 74 of 111\n\naccess-lists List IP access lists\r\n accounting The active IP accounting database\r\n aliases IP alias table\r\n arp IP ARP table\r\n as-path-access-list List AS path access lists\r\n bgp BGP information\r\n cache IP fast-switching route cache\r\n casa display casa information\r\n cef Cisco Express Forwarding\r\n community-list List community-list\r\n dfp DFP information\r\n dhcp Show items in the DHCP database\r\n drp Director response protocol\r\n dvmrp DVMRP information\r\n eigrp IP-EIGRP show commands\r\n extcommunity-list List extended-community list\r\n flow NetFlow switching\r\n helper-address helper-address table\r\n http HTTP information\r\n igmp IGMP information\r\n irdp ICMP Router Discovery Protocol\r\n.\r\n.\r\nThe following example shows how to use the enable view command to switch from the root view to the CLI view\r\n“first”:\r\nRouter# enable view\r\nRouter#\r\n01:08:16:%PARSER-6-VIEW_SWITCH:successfully set to view 'root'.\r\nRouter#\r\n! Enable the show parser view command from the root view\r\nRouter# show parser view\r\nCurrent view is 'root'\r\n! Enable the show parser view command from the root view to display all views\r\nRouter# show parser view all\r\nViews Present in System:\r\nView Name: first\r\nView Name: second\r\n! Switch to the CLI view “first.”\r\nRouter# enable view first\r\n \r\nRouter#\r\n01:08:09:%PARSER-6-VIEW_SWITCH:successfully set to view 'first'.\r\n! Enable the show parser view command from the CLI view “first.”\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 75 of 111\n\nRouter# show parser view\r\nCurrent view is 'first'\r\nRelated Commands\r\nCommand Description\r\ndisable\r\nExits from privileged EXEC mode to user EXEC mode, or, if privilege levels are set,\r\nto the specified privilege level.\r\nenable password Sets a local password to control access to various privilege levels.\r\nprivilege level\r\n(global)\r\nSets a privilege level for a command.\r\nprivilege level\r\n(line)\r\nSets a privilege level for a command for a specific line.\r\nenable last-resort\r\nTo enable password parameters as the last resort without specifying the local enable password if no TACACS\r\nservers respond, use the enable last-resort command in global configuration mode. To disable the password\r\nparameters, use the no form of this command.\r\nno enable last-resort {password | succeed}\r\nno enable last-resort\r\nSyntax Description\r\npassword Enables password parameters by specifying the local enable password.\r\nsucceed Enables password parameters without specifying the local enable password.\r\nCommand Default\r\nThe password parameters for the router are not enabled.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 76 of 111\n\nCommand Modes\r\nGlobal configuration (config)\r\nCommand History\r\nRelease Modification\r\n15.0(1)M This command was introduced in a release earlier than Cisco IOS 15.0(1)M.\r\nExamples\r\nThe following example shows how to enable password parameters as the last resort without specifying the local\r\nenable password if no TACACS servers respond:\r\nRouter\u003e enable\r\nRouter# configure terminal\r\nRouter(config)# enable last-resort succeed\r\nRelated Commands\r\nCommand Description\r\nshow tacacs Displays statistics for a TACACS+ server.\r\nend\r\nTo en d the current configuration session and return to privileged EXEC mode, use the end command in global\r\nconfiguration mode.\r\nend\r\nSyntax Description\r\nThis command has no arguments or keywords.\r\nCommand Default\r\nNo default behavior or values.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 77 of 111\n\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\nUsage Guidelines\r\nThis command will bring you back to privileged EXEC mode regardless of what configuration mode or\r\nconfiguration submode you are in.\r\nNote\r\nThis global configuration command can be used in any configuration mode.\r\nUse this command when you are done configuring the system and you want to return to EXEC mode to perform\r\nverification steps.\r\nExamples\r\nIn the following example, the end command is used to exit from ALPS ASCU configuration mode and return to\r\nprivileged EXEC mode. A show command is used in privileged EXEC mode to verify the configuration.\r\nRouter# configure terminal\r\nRouter(config)# interface serial 1:1\r\n \r\nRouter(config-if)# alps ascu 4B\r\n \r\nRouter(config-alps-ascu)# end\r\nRouter# show interface serial 1:1\r\nRelated Commands\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 78 of 111\n\nCommand Description\r\nexit (global) Exits from the current configuration mode.\r\nenvironment-monitor shutdown temperature\r\nTo enable monitoring of the environment sensors, use the environment-monitor shutdown temperature command\r\nin global configuration mode. To disable monitoring of the environment sensors, use the no form of this\r\ncommand.\r\nenvironment-monitor shutdown temperature [rommon | powerdown]\r\nno environment-monitor shutdown temperature [rommon | powerdown]\r\nSyntax Description\r\nrommon (Optional) Places the supervisor engine in ROMMON when a major active alarm is identified.\r\npowerdown (Optional) Powers down the supervisor engine when a new active major alarm is identified.\r\nCommand Default\r\nBy default, rommon is enabled.\r\nCommand Modes\r\nGlobal configuration\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(18)SXF17 Support for powerdown keyword added.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 79 of 111\n\nRelease Modification\r\n12.2(33)SXH6 Support for powerdown keyword added.\r\nExamples\r\nThis example shows how to place the supervisor engine in ROMMON when a major active alarm occurs:\r\nRouter(config)#\r\nenvironment-monitor shutdown temperature rommon\r\nRouter(config)#\r\nThis example shows how to power down the supervisor engine when a major active alarm occurs:\r\nRouter(config)#\r\nenvironment-monitor shutdown temperature powerdown\r\nRouter(config)#\r\nenvironment temperature-controlled\r\nTo enable the ambient temperature control, use the environment temperature-controlled command in global\r\nconfiguration mode. To disable the ambient temperature control, use the no form of this command.\r\nenvironment temperature-controlled\r\nno environment temperature-controlled\r\nSyntax Description\r\nThis command has no arguments or keywords.\r\nCommand Default\r\nThis command is disabled by default.\r\nCommand Modes\r\nGlobal configuration\r\nCommand History\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 80 of 111\n\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\nThis command does not affect temperature monitoring and alarm thresholds; it only affects whether a module may\r\nbe powered on. The software does not validate the inlet temperature.\r\nIf you enter the no form of this command and the cooling capacity is reduced below the module cooling\r\nrequirement, a syslog warning (and SNMP alarm) is generated. This module status does not change, and an\r\nenvironmental alarm is not raised when you enter the no form of this command.\r\nExamples\r\nThis example shows how to enable the ambient temperature control:\r\nRouter(config)#\r\nenvironment temperature-controlled\r\nRouter(config)#\r\nThis example shows how to disable the ambient temperature control:\r\nRouter(config)#\r\nno environment temperature-controlled\r\nRouter(config)#\r\nerase\r\nTo erase a file system or all files available on a file system, use the erase command in privileged EXEC or\r\ndiagnostic mode.\r\nerase {/all nvram: | /no-squeeze-reserve-space filesystem: | filesystem: | startup-config}\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 81 of 111\n\nCisco 7600 Series Routers and Cisco ASR 1000 Series Routers\r\nerase {/all nvram: | filesystem: | startup-config}\r\nSyntax Description\r\n/all Erases all files in the specified file system.\r\nnvram: Erases all files in the NVRAM.\r\nfile-system:\r\nFile system name, followed by a colon. For example, flash: or nvram: .\r\nNote\r\n \r\nThis argument may not be used if the device memory contains logging\r\npersistent files.\r\n/no-squeeze-reserve-spaceDisables the squeeze operation to conserve memory and makes the erase command\r\ncompatible with older file systems.\r\nstartup-config Erases the contents of the configuration memory.\r\nCommand Modes\r\nPrivileged EXEC (#) Diagnostic (#)\r\nCommand History\r\nRelease Modification\r\n11.0 This command was introduced.\r\n12.2(11)T This command was modified. The /no-squeeze-reserve-space keyword was added.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 82 of 111\n\nRelease Modification\r\n12.2(14)SX\r\nThis command was modified. Support for this command was added for the Supervisor\r\nEngine 720.\r\n12.2(33)SRA This command was integrated into Cisco IOS Release 12.2(33)SRA.\r\nCisco IOS XE\r\nRelease 2.1\r\nThis command was modified. The command was introduced in diagnostic mode on\r\nthe Cisco ASR 1000 Series Routers, and the /all keyword was added.\r\n15.0(1)M\r\nThis command was modified in a release earlier than Cisco IOS Release 15.0(1)M.\r\nThe file-system : argument was added.\r\nUsage Guidelines\r\nThe erase nvram: command replaces the write erase command and the erase startup-config command.\r\nCaution\r\nWhen you use the erase command to erase a file system, you cannot recover the files in the file\r\nsystem.\r\nThe word help feature is disabled for the erase command. You must enter the complete command name to enable\r\nthe command. The parser does not complete the command name if you enter partial syntax of the command and\r\npress the Tab key. For more information on the word help feature, refer to the Using the Cisco IOS Command-Line Interface feature guide.\r\nThe erase command can be used on Class B and Class C flash file systems only.\r\nClass A flash file systems cannot be erased. You can delete individual files using the delete command and then\r\nreclaim the space using the squeeze command. You can use the format command to format the flash file system.\r\nThe format command when used on ATA disk clears the File Allocation Table (FAT) and root directory entries\r\nonly. The data is not erased.\r\nThe erase nvram: command erases NVRAM. On Class A file system platforms, if the CONFIG_FILE variable\r\nspecifies a file in flash memory, the specified file will be marked “deleted.”\r\nThe erase /all nvram: command erases all files on NVRAM, including private NVRAM.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 83 of 111\n\nThe /no-squeeze-reserve-space keyword is available on systems with small amounts of flash memory in order to\r\nconserve memory. When a squeeze operation is performed, the last two erase sectors are permanently reserved for\r\nthe squeeze logs and squeeze buffer. The /no-squeeze-reserve-space keyword prevents the reservation of space\r\nthat guarantees the ability to run the squeeze command. Disabling the squeeze operation keeps these memory\r\nsectors free. If any sectors using squeeze data are detected, they will be erased when the /no-squeeze-reserve-space keyword is used. The /no-squeeze-reserve-space keyword increases the available amount of usable flash\r\nspace, but you may not be able to run the squeeze command. This is typically fine if the file system (such as flash)\r\nis used to store a single, large file. For example, an IOS image.\r\nOn Class C flash file systems, space is dynamically reclaimed when you use the delete command. You can also\r\nuse either the format or erase command to reinitialize a Class C flash file system.\r\nNote\r\nUse the context-sensitive help to determine which file systems can be used for the erase command.\r\nThe output will vary based on the platform.\r\nExamples\r\nThe following example shows how to erase the NVRAM, including the startup configuration located there:\r\nRouter# erase nvram:\r\nThe following example shows how to erase all of partition 2 in internal flash memory:\r\nRouter# erase flash:2\r\n \r\nSystem flash directory, partition 2:\r\nFile Length Name/status\r\n 1 1711088 dirt/images/c3600-i-mz\r\n[1711152 bytes used, 15066064 available, 16777216 total]\r\nErase flash device, partition 2? [confirm]\r\nAre you sure? [yes/no]:\r\nyes\r\nErasing device... eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee ...erased\r\nThe following example shows how to erase flash memory when flash is partitioned, but no partition is specified in\r\nthe command:\r\nRouter# erase flash:\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 84 of 111\n\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\nThe system will prompt only if there are two or more read/write partitions. If the partition entered is not valid or is\r\nthe read-only partition, the process terminates. You can enter a partition number, a question mark (? ) for a\r\ndirectory display of all partitions, or a question mark and a number (? number ) for directory display of a\r\nparticular partition. The default is the first read/write partition.\r\nSystem flash directory, partition 2:\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\nErase flash device, partition 2? [confirm] \u003cReturn\u003e\r\nRelated Commands\r\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\ndelete Deletes a file on a flash memory device.\r\nmore\r\nnvram:startup-config\r\nDisplays the startup configuration file contained in NVRAM or specified by the\r\nCONFIG_FILE environment variable.\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\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 85 of 111\n\nCommand Description\r\nsqueeze\r\nRemoves all deleted files from the flash file system and recovers the memory space\r\nused by deleted files.\r\nundelete Recovers a file marked “deleted” on a Class A or Class B flash file system.\r\nwrite erase\r\nThe write erase command is replaced by the erase nvram: command. See the description\r\nof the erase command for more information\r\nerase bootflash\r\nThe erase bootflash: and erase bootflash commands have identical functions. See the description of the erase\r\ncommand in this chapter for more information.\r\nerrdisable detect cause\r\nTo enable error-disable detection, use the errdisable detect cause command in global configuration mode. To\r\ndisable error-disable detection, use the no form of this command.\r\nerrdisable detect cause {all | bpduguard | dtp-flap | l2ptguard | link-flap | packet-buffer-error | pagp-flap |\r\nrootguard | udld}\r\nno errdisable detect cause {all | bpduguard | dtp-flap | l2ptguard | link-flap | pagp-flap | rootguard | udld}\r\nSyntax Description\r\nall Specifies error-disable detection for all error-disable causes.\r\nbpduguard\r\nSpecifies detection for the Bridge Protocol Data Unit (BPDU)-guard error-disable\r\ncause.\r\ndtp-flap Specifies detection for the Dynamic Trunking Protocol (DTP)-flap error-disable cause.\r\nl2ptguard Specifies detection for the Layer 2 Protocol Tunneling guard error-disable cause.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 86 of 111\n\nlink-flap Specifies detection for the link flap error-disable cause.\r\npacket-buffer-error\r\nCauses the packet buffer error to error-disable the affected port.\r\npagp-flap Specifies detection for the Port Aggregation Protocol (PAgP)-flap error-disable cause.\r\nrootguard Specifies detection for the root-guard error-disable cause.\r\nudld Specifies detection for the Unidirectional Link Detection (UDLD) error-disable cause.\r\nCommand Default\r\nError-disable detection is enabled for all causes.\r\nCommand Modes\r\nGlobal configuration (config)\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(14)SX This command was modified. Support was added for the Supervisor Engine 720.\r\n12.2(17b)SXA This command was modified. The packet-buffer-error keyword was added.\r\n12.2(17d)SXB\r\nThis command was modified. Support for this command on the Supervisor Engine 2 was\r\nextended to Release 12.2(17d)SXB.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 87 of 111\n\nRelease Modification\r\n12.2(33)SRA This command was integrated into Cisco IOS Release 12.2(33)SRA.\r\nUsage Guidelines\r\nNote\r\nEntering the no errdisable detect cause packet-buffer-error command allows you to detect the fault\r\nthat triggers a power cycle of the affected module.\r\nA cause (bpduguard, dtp-flap, link-flap, pagp-flap, root-guard, udld) is defined as the reason why the error-disable\r\nstate occurred. When a cause is detected on an interface, the interface is placed in an error-disable state (an\r\noperational state that is similiar to the link-down state).\r\nYou must enter the shutdown and then the no shutdown commands to recover an interface manually from the\r\nerror-disable state.\r\nExamples\r\nThe following example shows how to enable error-disable detection for the Layer 2 protocol-tunnel guard error-disable cause:\r\nRouter(config)#\r\nerrdisable detect cause l2ptguard\r\nRelated Commands\r\nCommand Description\r\nshow errdisable\r\ndetect\r\nDisplays the error-disable detection status.\r\nshow interfaces\r\nstatus\r\nDisplays the interface status or a list of interfaces in an error-disable state on LAN\r\nports only.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 88 of 111\n\nCommand Description\r\nshutdown Disables an interface.\r\nerrdisable recovery\r\nTo configure recovery mechanism variables, use the errdisable recovery command in global configuration mode.\r\nTo return to the default state, use the no form of this command.\r\nerrdisable recovery {cause {all | arp-inspection | bpduguard | channel-misconfig | dhcp-rate-limit | dtp-flap |\r\ngbic-invalid | l2ptguard | link-flap | pagp-flap | psecure-violation | security-violation | rootguard | udld | unicast-flood} | interval seconds}\r\nno errdisable recovery {cause {all | arp-inspection | bpduguard | channel-misconfig | dhcp-rate-limit | dtp-flap |\r\ngbic-invalid | l2ptguard | link-flap | pagp-flap | psecure-violation | security-violation | rootguard | udld | unicast-flood} | interval seconds}\r\nSyntax Description\r\ncause Enables error-disable recovery from a specific cause.\r\nall Enables the recovery timers for all error-disable causes.\r\narp-inspection\r\nEnables error-disable recovery from an Address Resolution Protocol (ARP) inspection\r\ncause.\r\nbpduguard\r\nEnables the recovery timer for the Bridge Protocol Data Unit (BPDU)-guard error-disable\r\ncause.\r\nchannel-misconfig\r\nEnables the recovery timer for the channel-misconfig error-disable cause.\r\ndhcp-rate-limit\r\nEnables the recovery timer for the Dynamic Host Configuration Protocol (DHCP)-rate-limit error-disable cause.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 89 of 111\n\ndtp-flap\r\nEnables the recovery timer for the Dynamic Trunking Protocol (DTP)-flap error-disable\r\ncause.\r\ngbic-invalid\r\nEnables the recovery timer for the Gigabit Interface Converter (GBIC)-invalid error-disable cause.\r\nl2ptguard Enables the recovery timer for the Layer 2 Protocol Tunneling (L2PT) error-disable cause.\r\nlink-flap Enables the recovery timer for the link-flap error-disable cause.\r\npagp-flap\r\nEnables the recovery timer for the Port Aggregation Protocol (PAgP)-flap error-disable\r\ncause.\r\npsecure-violation\r\nEnables the recovery timer for the psecure-violation error-disable cause.\r\nsecurity-violationEnables the automatic recovery of ports that were disabled because of 802.1X security\r\nviolations.\r\nrootguard Enables the recovery timer for the root-guard error-disable cause.\r\nudld\r\nEnables the recovery timer for the Unidirectional Link Detection (UDLD) error-disable\r\ncause.\r\nunicast-flood Enables the recovery timer for the unicast-flood error-disable cause.\r\ninterval\r\nseconds\r\nSpecifies the time, in seconds, to recover from a specified error-disable cause. The range is\r\nfrom 30 to 86400. The default interval is 300.\r\nCommand Default\r\nThe recovery mechanisms are disabled.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 90 of 111\n\nCommand Modes\r\nGlobal configuration (config)\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(14)SX\r\nThis command was modified. This command was implemented on the Supervisor Engine\r\n720.\r\n12.2(17d)SXB This command was modified. This command was implemented on the Supervisor Engine 2.\r\n12.2(18)SXD This command was modified. The arp-inspection keyword was added.\r\n12.2(33)SRA This command was integrated into Cisco IOS Release 12.2(33)SRA.\r\nUsage Guidelines\r\nA cause (bpduguard, channel-misconfig, dhcp-rate-limit, dtp-flap, l2ptguard, link-flap, pagp-flap, psecure-violation, security-violation, rootguard, udld, or unicast-flood) is defined as the reason why the error-disable state\r\noccurred. When a cause is detected on an interface, the interface is placed in an error-disable state (an operational\r\nstate that is similar to the link-down state). If you do not enable error-disable recovery for the cause, the interface\r\nstays in the error-disable state until a shutdown and no shutdown occur. If you enable recovery for a cause, the\r\ninterface is brought out of the error-disable state and allowed to retry operation once all the causes have timed out.\r\nYou must enter the shutdown command and then the no shutdown command to manually recover an interface\r\nfrom the error-disable state.\r\nNote\r\nA separate line is required each time you want to enter the errdisable recovery cause command to add\r\na new reason for recovery; each new reason does not get appended to the original single line. This\r\nmeans you must enter each new reason separately.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 91 of 111\n\nExamples\r\nThis example shows how to enable the recovery timer for the BPDU-guard error-disable cause:\r\nRouter(config)#\r\n errdisable recovery cause bpduguard\r\nThis example shows how to set the recovery timer to 300 seconds:\r\nRouter(config)#\r\n errdisable recovery interval 300\r\nRelated Commands\r\nCommand Description\r\nshow errdisable\r\nrecovery\r\nDisplays the information about the error-disable recovery timer.\r\nshow interfaces status\r\nDisplays the interface status or a list of interfaces in an error-disabled state on LAN\r\nports only.\r\nshutdown Disables an interface.\r\nescape-character\r\nTo define a system escape character, use the escape-character command in line configuration mode. To set the\r\nescape character to Break, use the no or default form of this command.\r\nescape-character {break | char | default | none | soft}\r\nno escape-character [soft]\r\ndefault escape-character [soft]\r\nSyntax Description\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 92 of 111\n\nbreak\r\nSets the escape character to Break. Note that the Break key should not be used as an escape\r\ncharacter on a console terminal.\r\nchar\r\nCharacter (for example, ! ) or its ASCII decimal representation ( integer in the range of 0 to 255) to\r\nbe used as the escape character.\r\ndefault Sets the escape key sequence to the default of Ctrl-^, X.\r\nnone Disables escape entirely.\r\nsoft Sets an escape character that will wait until pending input is processed before it executes.\r\nCommand Default\r\nThe default escape key sequence is Ctrl-Shift-6 (Ctrl-^) or Ctrl-Shift-6, X (^^X). The X is generally only required\r\nfor modem connections.\r\nThe default escape-character command sets the escape character to Break (the default setting for Break is Ctrl-C).\r\nCommand Modes\r\nLine configuration\r\nCommand History\r\nRelease Modification\r\n10.0 This command was introduced.\r\n11.3 The soft keyword was 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/D_through_E.html#wp3557227463\r\nPage 93 of 111\n\nSee the \"ASCII Character Set and Hexidecimal Values\" appendix for a list of ASCII characters.\r\nThe escape character (or key sequence) suspends any actively running processes and returns you to privileged\r\nEXEC mode or, if a menu is being used, to the system menu interface. The escape character is used for\r\ninterrupting or terminating a process started by previously executed command. Examples of processes from which\r\nyou can escape include Domain-Name lookup, ping , trace , and Telnet sessions initiated from the device to which\r\nyou are connected.\r\nTo view the current setting of the escape sequence for a line, use the show line command followed by the specific\r\nline identifier (for example, show line 0 , or show line console ). The default escape sequence for a line is often\r\ndisplayed as ^^X . The first caret symbol represents the Control (Ctrl) key, the second caret symbol is literal\r\n(Shift-6), and the X is literal (for most systems, the X is not required).\r\nTo set the escape key for the active terminal line session, use the terminal escape-character command.\r\nThe Break key cannot be used as an escape character on a console terminal because the Cisco IOS software\r\ninterprets Break as an instruction to halt the system. Depending upon the configuration register setting, break\r\ncommands issued from the console line either will be ignored or cause the server to shut down.\r\nTo send an escape sequence over a Telnet connection, press Ctrl-Shift-6 twice.\r\nThe escape-character soft form of this command defines a character or character sequence that will cause the\r\nsystem to wait until pending input is processed before suspending the current session. This option allows you to\r\nprogram a key sequence to perform multiple actions, such as using the F1 key to execute a command, then execute\r\nthe escape function after the first command is executed.\r\nThe following restrictions apply when using the soft keyword:\r\nThe length of the logout sequence must be 14 characters or fewer.\r\nThe soft escape character cannot be the same as the generic Cisco escape character, Break, or the\r\ncharacters b, d, n, or s.\r\nThe soft escape character should be an ASCII value from 1 to 127. Do not use the number 30.\r\nExamples\r\nThe following example sets the escape character for the console line to the keyboard entry Ctrl-P, which is\r\nrepresented by the ASCII decimal value of 16:\r\nRouter(config)# line console\r\nRouter(config-line)# escape-character 16\r\nThe following example sets the escape character for line 1 to ! , which is represented in the configuration file as\r\nthe ASCII number 33:\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 94 of 111\n\nRouter(config)# line 1\r\nRouter(config-line)# escape-character !\r\nRouter(config-line)# end\r\nRouter# show running-config\r\nBuilding configuration...\r\n.\r\n.\r\n.\r\nline 1\r\n autoselect during-login\r\n autoselect ppp\r\n modem InOut\r\n transport preferred none\r\n transport output telnet\r\n escape-character 33\r\nRelated Commands\r\nCommand Description\r\nshow line Displays information about the specified line connection, or all the lines.\r\nterminal escape-character Sets the escape character for the current terminal line for the current session.\r\nexec\r\nTo allow an EXEC process on a line, use the exec command in line configuration mode. To turn off the EXEC\r\nprocess for the specified line, use the no form of this command.\r\nexec\r\nno exec\r\nSyntax Description\r\nThis command has no arguments or keywords.\r\nCommand Default\r\nThe EXEC processes is enabled on all lines.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 95 of 111\n\nCommand Modes\r\nLine 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\nUsage Guidelines\r\nWhen you want to allow only an outgoing connection on a line, use the no exec command.\r\nThe no exec command allows you to disable the EXEC process for connections which may attempt to send\r\nunsolicited data to the router. (For example, the control port of a rack of modems attached to an auxiliary port of\r\nrouter.) When certain types of data are sent to a line connection, an EXEC process can start, which makes the line\r\nunavailable.\r\nWhen a user tries to Telnet to a line with the EXEC process disabled, the user will get no response when\r\nattempting to log on.\r\nExamples\r\nThe following example disables the EXEC process on line 7.\r\nRouter(config)# line 7\r\n \r\nRouter(config-line)# no exec\r\n \r\nexec-banner\r\nTo reenable the display of EXEC and message-of-the-day (MOTD) banners on the specified line or lines, use the\r\nexec-banner command in line configuration mode. To suppress the banners on the specified line or lines, use the\r\nno form of this command.\r\nexec-banner\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 96 of 111\n\nno exec-banner\r\nSyntax Description\r\nThis command has no arguments or keywords.\r\nCommand Default\r\nEnabled on all lines\r\nCommand Modes\r\nLine 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\nUsage Guidelines\r\nThis command determines whether the router will display the EXEC banner and the message-of-the-day (MOTD)\r\nbanner when an EXEC session is created. These banners are defined with the banner exec and banner motd global\r\nconfiguration commands. By default, these banner are enabled on all lines. Disable the EXEC and MOTD banners\r\nusing the no exec-banner command.\r\nThis command has no effect on the incoming banner, which is controlled by the banner incoming command.\r\nThe MOTD banners can also be disabled by the no motd-banner line configuration command, which disables\r\nMOTD banners on a line. If the no exec-banner command is configured on a line, the MOTD banner will be\r\ndisabled regardless of whether the motd-banner command is enabled or disabled. The table below summarizes the\r\neffects of the exec-banner command and the motd-banner command.\r\nTable 5. Banners Displayed Based On exec-banner and motd-banner Combinations\r\nexec-banner (default) no exec-banner\r\nmotd-banner (default) MOTD banner None\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 97 of 111\n\nexec-banner (default) no exec-banner\r\nEXEC banner\r\nno motd-banner EXEC banner None\r\nFor reverse Telnet connections, the EXEC banner is never displayed. Instead, the incoming banner is displayed.\r\nThe MOTD banner is displayed by default, but it is disabled if either the no exec-banner command or no motd-banner command is configured. The table below summarizes the effects of the exec-banner command and the\r\nmotd-banner command for reverse Telnet connections.\r\nTable 6. Banners Displayed Based On exec-banner and motd-banner Combinations for Reverse Telnet Sessions to\r\nAsync Lines\r\nexec-banner (default) no exec-banner\r\nmotd-banner (default)\r\nMOTD banner\r\nIncoming banner\r\nIncoming banner\r\nno motd-banner Incoming banner Incoming banner\r\nExamples\r\nThe following example suppresses the EXEC and MOTD banners on virtual terminal lines 0 to 4:\r\nRouter(config)# line vty 0 4\r\n \r\nRouter(config-line)# no exec-banner\r\n \r\nRelated Commands\r\nCommand Description\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 98 of 111\n\nCommand Description\r\nbanner exec\r\nDefines and enables a customized banner to be displayed whenever the EXEC process is\r\ninitiated.\r\nbanner\r\nincoming\r\nDefines and enables a customized message to be displayed when there is an incoming\r\nconnection to a terminal line from a host on the network.\r\nbanner motd Defines and enables a customized message-of-the-day banner.\r\nmotd-banner\r\nControls (enables or disables) the display of message-of-the-day banners on a specified line\r\nor lines.\r\nexec-character-bits\r\nTo configure the character widths of EXEC and configuration command characters, use the exec-character-bits\r\ncommand in line configuration mode. To restore the default value, use the no form of this command.\r\nexec-character-bits {7 | 8}\r\nno exec-character-bits\r\nSyntax Description\r\n7 Selects the 7-bit character set. This is the default.\r\n8\r\nSelects the full 8-bit character set for use of international and graphical characters in banner messages,\r\nprompts, and so on.\r\nCommand Default\r\n7-bit ASCII character set\r\nCommand Modes\r\nLine configuration\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 99 of 111\n\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\nSetting the EXEC character width to 8 allows you to use special graphical and international characters in banners,\r\nprompts, and so on. However, setting the EXEC character width to 8 bits can cause failures. If a user on a terminal\r\nthat is sending parity enters the help command, an “ unrecognized command” message appears because the system\r\nis reading all 8 bits, and the eighth bit is not needed for the help command.\r\nNote\r\nIf you are using the autoselect function, set the activation character to the default (Return) and the\r\nvalue for exec-character-bits to 7. If you change these defaults, the application will not recognize the\r\nactivation request.\r\nExamples\r\nThe following example enables full 8-bit international character sets, except for the console, which is an ASCII\r\nterminal. It illustrates use of the default-value exec-character-bits global configuration command and the exec-character-bits line configuration command.\r\nRouter(config)# default-value exec-character-bits 8\r\nRouter(config)# line 0\r\nRouter(config-line)# exec-character-bits 7\r\nRelated Commands\r\nCommand Description\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 100 of 111\n\nCommand Description\r\ndefault-value exec-character-bits\r\nDefines the EXEC character width for either 7 bits or 8 bits.\r\ndefault-value special-character-bits\r\nConfigures the flow control default value from a 7-bit width to an 8-bit width.\r\nlength Sets the terminal screen length.\r\nterminal exec-character-bitsLocally changes the ASCII character set used in EXEC and configuration\r\ncommand characters for the current session.\r\nterminal special-character-bitsChanges the ASCII character widths to accept special characters for the current\r\nterminal line and session.\r\nexec-timeout\r\nTo set the interval that the EXEC command interpreter waits until user input is detected, use the exec-timeout\r\ncommand in line configuration mode. To remove the timeout definition, use the no form of this command.\r\nexec-timeout minutes [seconds]\r\nno exec-timeout\r\nSyntax Description\r\nminutes Integer that specifies the number of minutes. The default is 10 minutes.\r\nseconds (Optional) Additional time intervals in seconds.\r\nCommand Default\r\n10 minutes\r\nCommand Modes\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 101 of 111\n\nLine 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\n15.0(1)SY2 The no form of the command updated to configure an exec-timeout of 0 0 on the device.\r\nUsage Guidelines\r\nIf no input is detected during the interval, the EXEC facility resumes the current connection. If no connections\r\nexist, the EXEC facility returns the terminal to the idle state and disconnects the incoming session.\r\nTo specify no timeout, enter the no form of this command.\r\nExamples\r\nThe following example sets a time interval of 2 minutes, 30 seconds:\r\nRouter(config)# line console 0\r\nRouter(config-line)# exec-timeout 2 30\r\nThe following example sets a time interval of 10 seconds:\r\nRouter(config)# line console 0\r\n \r\nRouter(config-line)# exec-timeout 0 10\r\nexecute-on\r\nTo execute commands on a line card, use the execute-on command in privileged EXEC mode.\r\nexecute-on {slot slot-number | all | master} command\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 102 of 111\n\nSyntax Description\r\nslot slot-number\r\nExecutes the command on the line card in the specified slot. Slot numbers can be chosen\r\nfrom the following ranges:\r\nCisco 12012 router: 0 to 11\r\nCisco 12008 access server: 0 to 7\r\nCisco AS5800 access server: 0 to 13\r\nall Executes the command on all line cards.\r\nmaster\r\n(AS5800 only) Executes the designated command on a Dial Shelf Controller (DSC). Do not\r\nuse this option; it is used for technical support troubleshooting only.\r\ncommand Cisco IOS command to remotely execute on the line card.\r\nCommand Modes\r\nPrivileged EXEC\r\nCommand History\r\nRelease Modification\r\n11.2 GS This command was introduced to support Cisco 12000 series Gigabit Switch Routers.\r\n11.3(2)AA This command was implemented in images for the Cisco AS5800 series.\r\n12.2(33)SRA This command was integrated into Cisco IOS Release 12.2(33)SRA.\r\n12.2(33)SRE\r\nThis command was integrated into Cisco IOS Release 12.2(33)SRE. Pipe '|\" options can now\r\nbe used with show option in the execute-on command on SUP and SAMI consoles.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 103 of 111\n\nUsage Guidelines\r\nUse this command to execute a command on one or all line cards to monitor and maintain information on one or\r\nmore line cards (for example, a line card in a specified slot on a dial shelf). This allows you to issue commands\r\nremotely; that is, to issue commands without needing to log in to the line card directly. The all form of the\r\ncommand allows you to issue commands to all the line cards without having to log in to each in turn.\r\nThough this command does not have a no form, note that it is possible to use the no form of the remotely executed\r\ncommands used in this command.\r\nTip\r\nThis command is useful when used with show EXEC commands (such as show version ), because you\r\ncan verify and troubleshoot the features found only on a specific line card. Please note, however, that\r\nbecause not all statistics are maintained on the line cards, the output from some of the show commands\r\nmight not be consistent.\r\nCisco 12000 GSR Guidelines and Restrictions\r\nYou can use the execute-on privileged EXEC command only from Cisco IOS software running on the GRP card.\r\nTimesaver\r\nThough you can use the attach privileged EXEC command to execute commands on a specific\r\nline card, using the execute-on slot command saves you some steps. For example, first you\r\nmust use the attach command to connect to the Cisco IOS software running on the line card.\r\nNext you must issue the command. Finally you must disconnect from the line card to return to\r\nthe Cisco IOS software running on the GRP card. With the execute-on slot command, you can\r\nperform three steps with one command. In addition, the execute-on all command allows you to\r\nperform the same command on all line cards simultaneously.\r\nCisco c7600 Sup Guidelines and Restrictions\r\nBeginning with the 12.2(33)SRE Cisco IOS release, all pipe '|\" options can now be used with show option in the\r\nexecute-on command on SUP and SAMI consoles.\r\nCisco AS5800 Guidelines and Restrictions\r\nThe purpose of the command is to conveniently enable certain commands to be remotely executed on the dial\r\nshelf cards from the router without connecting to each line card. This is the recommended procedure, because it\r\navoids the possibility of adversely affecting a good configuration of a line card in the process. The execute-on\r\ncommand does not give access to every Cisco IOS command available on the Cisco AS5800 access server. In\r\ngeneral, the purpose of the execute-on command is to provide access to statistical reports from line cards without\r\ndirectly connecting to the dial shelf line cards.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 104 of 111\n\nCaution\r\nDo not use this command to change configurations on dial shelf cards, because such changes will\r\nnot be reflected in the router shelf.\r\nUsing this command makes it possible to accumulate inputs for inclusion in the show tech-support command.\r\nThe master form of the command can run a designated command remotely on the router from the DSC card.\r\nHowever, using the console on the DSC is not recommended. It is used for technical support troubleshooting only.\r\nThe show tech-support command for each dial shelf card is bundled into the router shelf's show tech-support\r\ncommand via the execute-on facility.\r\nThe execute-on command also support interactive commands such as the following:\r\nrouter: execute-on slave slot\r\n \r\nslot\r\n ping\r\nThe execute-on command has the same limitations and restrictions as a vty telnet client has; that is, it cannot\r\nreload DSC using the following command:\r\nrouter: execute-on slave slot\r\n \r\nslot\r\n reload\r\nYou can use the execute-on command to enable remote execution of the commands included in the following\r\npartial list:\r\ndebug dsc clock\r\nshow context\r\nshow diag\r\nshow environment\r\nshow dsc clock\r\nshow dsi\r\nshow dsip\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 105 of 111\n\nshow tech-support\r\nExamples\r\nIn the following example, the user executes the show controllers command on the line card in slot 4 of a Cisco\r\n12000 series GSR:\r\nRouter# execute-on slot 4 show controllers\r\n========= Line Card (Slot 4) =======\r\nInterface POS0\r\nHardware is BFLC POS\r\nlcpos_instance struct 6033A6E0\r\nRX POS ASIC addr space 12000000\r\nTX POS ASIC addr space 12000100\r\nSUNI framer addr space 12000400\r\nSUNI rsop intr status 00\r\nCRC16 enabled, HDLC enc, int clock\r\nno loop\r\nInterface POS1\r\nHardware is BFLC POS\r\nlcpos_instance struct 6033CEC0\r\nRX POS ASIC addr space 12000000\r\nTX POS ASIC addr space 12000100\r\nSUNI framer addr space 12000600\r\nSUNI rsop intr status 00\r\nCRC32 enabled, HDLC enc, int clock\r\nno loop\r\nInterface POS2\r\nHardware is BFLC POS\r\nlcpos_instance struct 6033F6A0\r\nRX POS ASIC addr space 12000000\r\nTX POS ASIC addr space 12000100\r\nSUNI framer addr space 12000800\r\nSUNI rsop intr status 00\r\nCRC32 enabled, HDLC enc, int clock\r\nno loop\r\nInterface POS3\r\nHardware is BFLC POS\r\nlcpos_instance struct 60341E80\r\nRX POS ASIC addr space 12000000\r\nTX POS ASIC addr space 12000100\r\nSUNI framer addr space 12000A00\r\nSUNI rsop intr status 00\r\nCRC32 enabled, HDLC enc, ext clock\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 106 of 111\n\nno loop\r\nRouter#\r\nIn the following example, the user executes the show version command on the line card in slot 2 and 3 of a Cisco\r\nc7600 Sup series device:\r\nExample for c7600 SUP -\r\nRouter#execute-on 2 3 show\r\n \r\n WORD Command to be executed\r\n | Output modifiers\r\n \u003ccr\u003e\r\nRouter#execute-on 2 3 show version\r\n | ?\r\n append Append redirected output to URL (URLs supporting append operation\r\n only)\r\n begin Begin with the line that matches\r\n exclude Exclude lines that match\r\n format Format the output using the specified spec file\r\n include Include lines that match\r\n redirect Redirect output to URL\r\n section Filter a section of output\r\n tee Copy output to URL\r\nRouter#execute-on 2 3 execute-on 4 show version\r\n ?\r\n WORD Command to be executed\r\n | Output modifiers\r\n \u003ccr\u003e\r\nRouter#execute-on 2 3 execute-on 4 show version\r\n | redirect\r\n ?\r\n bootflash: Uniform Resource Locator\r\n const_nvram: Uniform Resource Locator\r\n disk0: Uniform Resource Locator\r\n disk1: Uniform Resource Locator\r\n nvram: Uniform Resource Locator\r\n sami#2-fs: Uniform Resource Locator\r\n sami#3-fs: Uniform Resource Locator\r\n slavebootflash: Uniform Resource Locator\r\n slaveconst_nvram: Uniform Resource Locator\r\n slavedisk0: Uniform Resource Locator\r\n slavedisk1: Uniform Resource Locator\r\n slavenvram: Uniform Resource Locator\r\n slavercsf: Uniform Resource Locator\r\n slavesup-bootdisk: Uniform Resource Locator\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 107 of 111\n\nslavesup-bootflash: Uniform Resource Locator\r\n sup-bootdisk: Uniform Resource Locator\r\n sup-bootflash: Uniform Resource Locator\r\nIn the following example, the user executes the show command on the line card in slot 4 of a Cisco c7600 SAMI\r\nseries device:\r\nRouter#execute-on 4 show\r\n?\r\n WORD Command to be executed\r\n | Output modifiers\r\n \u003ccr\u003e\r\nRouter#execute-on 4 show\r\n | ?\r\n append Append redirected output to URL (URLs supporting append operation\r\n only)\r\n begin Begin with the line that matches\r\n exclude Exclude lines that match\r\n include Include lines that match\r\n redirect Redirect output to URL\r\n section Filter a section of output\r\n tee Copy output to URL\r\nRelated Commands\r\nCommand Description\r\nattach\r\nConnects you to a specific line card for the purpose of executing commands using the Cisco\r\nIOS software image on that line card.\r\nexit (EXEC)\r\nTo close an active terminal session by logging off the router, use the exit command in EXEC mode.\r\nexit\r\nSyntax Description\r\nThis command has no arguments or keywords.\r\nCommand Default\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 108 of 111\n\nNo default behavior or values\r\nCommand Modes\r\nEXEC\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\nUse the exit command in EXEC mode to exit the active session (log off the device). This command can be used in\r\nany EXEC mode (such as User EXEC mode or Privileged EXEC mode) to exit from the EXEC process.\r\nExamples\r\nIn the following example, the exit (global) command is used to move from global configuration mode to\r\nprivileged EXEC mode, the disable command is used to move from privileged EXEC mode to user EXEC mode,\r\nand the exit (EXEC) command is used to log off (exit the active session):\r\nRouter(config)# exit\r\nRouter# disable\r\nRouter\u003e exit\r\nRelated Commands\r\nCommand Description\r\ndisconnect Disconnects a line.\r\nend Ends your configuration session by exiting to EXEC mode.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 109 of 111\n\nCommand Description\r\nexit (global) Exits from the current configuration mode to the next highest configuration mode.\r\nlogout Closes your connection to the device (equivilant to the exit command).\r\nexit (global)\r\nTo exit any configuration mode to the next highest mode in the CLI mode hierarchy, use the exit command in any\r\nconfiguration mode.\r\nexit\r\nSyntax Description\r\nThis command has no arguments or keywords.\r\nCommand Default\r\nNo default behavior or values\r\nCommand Modes\r\nAll configuration modes\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\nThe exit command is used in the Cisco IOS CLI to exit from the current command mode to the next highest\r\ncommand mode in the CLI mode hierarchy.\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 110 of 111\n\nFor example, use the exit command in global configuration mode to return to privileged EXEC mode. Use the exit\r\ncommand in interface, line, or router configuration mode to return to global configuration mode. Use the exit\r\ncommand in subinterface configuration mode to return to interface configuration mode. At the highest level,\r\nEXEC mode, the exit command will exit the EXEC mode and disconnect from the router interface (see the\r\ndescription of the exit (EXEC) command for details).\r\nExamples\r\nThe following example shows how to exit from the subinterface configuration mode and to return to the interface\r\nconfiguration mode:\r\nRouter(config-subif)# exit\r\nRouter(config-if)#\r\nThe following example displays an exit from the interface configuration mode to return to the global configurati\r\nRouter(config-if)# exit\r\nRouter(config)#\r\nRelated Commands\r\nCommand Description\r\ndisconnect Disconnects a line.\r\nend Ends your configuration session by exiting to privileged EXEC mode.\r\nexit (EXEC) Closes the active terminal session by logging off the router.\r\nBack to Top\r\nSource: https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nhttps://www.cisco.com/c/en/us/td/docs/ios-xml/ios/fundamentals/command/cf_command_ref/D_through_E.html#wp3557227463\r\nPage 111 of 111\n\nRelease 12.1(10)EX2 Modification This command was introduced.    \n12.2(18)S This command was introduced on Cisco 7304 routers running Cisco IOS Release 12.2 S.\n12.2(33)SRA This command was integrated into Cisco IOS Release 12.2(33)SRA.  \n This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific\n12.2SX      \n 12.2SX release of this train depends on your feature set, platform, and platform hardware.\nUsage Guidelines      \nUse this command to enable power-on diagnostic tests to run on the installed NSEs of a Cisco 7300 series router\nwhen the system is booted. It is recommended that you issue this command only if you are experiencing problems\n   Page 26 of 111",
	"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/D_through_E.html#wp3557227463"
	],
	"report_names": [
		"D_through_E.html#wp3557227463"
	],
	"threat_actors": [
		{
			"id": "2864e40a-f233-4618-ac61-b03760a41cbb",
			"created_at": "2023-12-01T02:02:34.272108Z",
			"updated_at": "2026-04-10T02:00:04.97558Z",
			"deleted_at": null,
			"main_name": "WildCard",
			"aliases": [],
			"source_name": "ETDA:WildCard",
			"tools": [
				"RustDown",
				"SysJoker"
			],
			"source_id": "ETDA",
			"reports": null
		},
		{
			"id": "9041c438-4bc0-4863-b89c-a32bba33903c",
			"created_at": "2023-01-06T13:46:38.232751Z",
			"updated_at": "2026-04-10T02:00:02.888195Z",
			"deleted_at": null,
			"main_name": "Nitro",
			"aliases": [
				"Covert Grove"
			],
			"source_name": "MISPGALAXY:Nitro",
			"tools": [],
			"source_id": "MISPGALAXY",
			"reports": null
		},
		{
			"id": "a2b44a04-a080-4465-973d-976ce53777de",
			"created_at": "2022-10-25T16:07:23.911791Z",
			"updated_at": "2026-04-10T02:00:04.786538Z",
			"deleted_at": null,
			"main_name": "Nitro",
			"aliases": [
				"Covert Grove",
				"Nitro"
			],
			"source_name": "ETDA:Nitro",
			"tools": [
				"AngryRebel",
				"Backdoor.Apocalipto",
				"Chymine",
				"Darkmoon",
				"Farfli",
				"Gen:Trojan.Heur.PT",
				"Gh0st RAT",
				"Ghost RAT",
				"Moudour",
				"Mydoor",
				"PCClient",
				"PCRat",
				"Poison Ivy",
				"SPIVY",
				"Spindest",
				"pivy",
				"poisonivy"
			],
			"source_id": "ETDA",
			"reports": null
		},
		{
			"id": "256a6a2d-e8a2-4497-b399-628a7fad4b3e",
			"created_at": "2023-11-30T02:00:07.299845Z",
			"updated_at": "2026-04-10T02:00:03.484788Z",
			"deleted_at": null,
			"main_name": "WildCard",
			"aliases": [],
			"source_name": "MISPGALAXY:WildCard",
			"tools": [],
			"source_id": "MISPGALAXY",
			"reports": null
		}
	],
	"ts_created_at": 1775434919,
	"ts_updated_at": 1775792121,
	"ts_creation_date": 0,
	"ts_modification_date": 0,
	"files": {
		"pdf": "https://archive.orkl.eu/a02407bc14f9034dc414c8da3d88ab4a70e172b2.pdf",
		"text": "https://archive.orkl.eu/a02407bc14f9034dc414c8da3d88ab4a70e172b2.txt",
		"img": "https://archive.orkl.eu/a02407bc14f9034dc414c8da3d88ab4a70e172b2.jpg"
	}
}