To verify the Multiple Spanning Tree (MST) configuration, use the show command. in MST configuration submode. Show
show [current | pending] Syntax Description
DefaultsThis command has no default settings. Command ModesMST configuration submode Command History
Usage GuidelinesThe display output from the show pending command is the edited configuration that will replace the current configuration if you enter the exit command to exit MST configuration mode. Entering the show command with no arguments displays the pending configurations. ExamplesThis example shows how to display the edited configuration: This example shows how to display the current configuration: Related Commands
show <command> appendTo redirect and add the output of any show command to an existing file, use the show command | append command in privileged EXEC mode. show command | append url Syntax Description
Command ModesPrivileged EXEC Command History
Usage GuidelinesTo display all URL prefixes that are supported for this command, use the show command | append ? command. This command adds the show command output to the end of the specified file. ExamplesIn the following example, output from the show tech-support command is redirected to an existing file on Disk 1 with the file-name of "showoutput.txt." This output is added at the end of any existing data in the file. Related Commands
show <command> beginTo begin the output of any show command from a specified string, use the show command | begin command in EXEC mode. show command | begin regular-expression Syntax Description
Command ModesEXEC Command History
Usage GuidelinesThe regular-expression argument is case sensitive and allows for complex matching requirements. Use parenthesis to indicate a literal use of spaces. For example, | begin u indicates that the show output should begin with any line that contains a u; | begin ( u) indicates that the show output should begin with any line that contains a space and a u together (line has a word that begins with a lowercase u). To search the remaining output of the show command, use the following command at the --More-- prompt: /regular-expression You can specify a filtered search at any --More-- prompt. To filter the remaining output of the show command, use one of the following commands at the --More-- prompt: -regular-expression +regular-expression When output volume is large, the search can produce long lists of output. To interrupt the output, press Ctrl-^ (Ctrl-Shift-6) or Ctrl-z.  Note Once you specify a filter for a show command, you cannot specify another filter at the next --More-- prompt. The first specified filter remains until the more command output finishes or until you interrupt the output. The use of the keyword begin does not constitute a filter. Because prior output is not saved, you cannot search or filter backward through prior output. Note A few show commands that have long output requirements do not require user input at the --More-- prompt to jump to the next table of output; these types of output require you to enter the same number of Ctrl-^ or Ctrl-Z combinations as there are --More-- prompts to completely abort output. ExamplesThe following is partial sample output of the show interface | begin command that begins unfiltered output with the first line that contains the regular expression "Ethernet." At the --More-- prompt, the user specifies a filter to show only the lines in the remaining output that contain the regular expression "Serial." Related Commands
show <command> excludeTo filter show command output so that it excludes lines that contain a particular regular expression, use the show command | exclude command in EXEC mode. show command | exclude regular-expression Syntax Description
Command ModesEXEC Command History
Usage GuidelinesThe regular-expression argument is case sensitive and allows for complex matching requirements. You can specify a new search at every --More-- prompt. To search the remaining output of the show command, use the following syntax at the --More-- prompt: /regular-expression When output volume is large, the search can produce long lists of output. To interrupt the output, press Ctrl-^ (Ctrl-Shift-6) or Ctrl-Z. Because prior output is not saved, you cannot search or filter backward through prior output. Note A few show commands that have long output requirements do not require user input at the --More-- prompt to jump to the next table of output; these types of output require you to enter the same number of Ctrl-^ or Ctrl-Z combinations as there are --More-- prompts to completely abort output. ExamplesThe following is partial sample output of the show | exclude command used with the show buffers command. It excludes lines that contain the regular expression "0 misses." At the --More-- prompt, the user searches for the regular expression "Serial0," which continues the filtered output with the first line that contains "Serial0." Related Commands
show <command> includeTo filter show command output so that it only displays lines that contain a particular regular expression, use the show command | include command in EXEC mode. show command | include regular-expression Syntax Description
Command ModesEXEC Command History
Usage GuidelinesThe regular-expression argument is case sensitive and allows for complex matching requirements. You can specify a new search at every --More-- prompt. To search the remaining output of the show command, use the following syntax at the --More-- prompt: /regular-expression When output volume is large, the search can produce long lists of output. To interrupt the output, press Ctrl-^ (Ctrl-Shift-6) or Ctrl-Z. Because prior output is not saved, you cannot search or filter backward through prior output. Note A few show commands that have long output requirements do not require user input at the --More-- prompt to jump to the next table of output; these types of output require you to enter the same number of Ctrl-^ or Ctrl-Z combinations as there are --More-- prompts to completely abort output. ExamplesThe following is partial sample output of the show interface | include command. It displays only lines that contain the regular expression "( is )." The parentheses force the inclusion of the spaces before and after "is." Use of the parenthesis ensures that only lines containing "is" with a space both before and after it will be included in the output. Lines with words like "disconnect" will be excluded because there are not spaces around the instance of the string "is". At the --More-- prompt, the user searches for the regular expression "Serial0:13", which continues filtered output with the first line that contains "Serial0:13." Related Commands
show <command> redirectTo redirect the output of any show command to a file, use the show command | redirect command in privileged EXEC mode. show command | redirect url Syntax Description
Command ModesPrivileged EXEC Command History
Usage GuidelinesTo display all URL prefixes that are supported for this command, use the show command | redirect ? command. This command creates a new file at the specified location, or overwrites an existing file. ExamplesIn the following example, output from the show tech-support command is write to the file "showtech.txt" on the host at 172.16.101.101 in the directory "//tftpboot/docs/" using FTP: Related Commands
show <command> sectionTo filter the output of a show command to match a given expression as well as any lines associated with that expression, use the show command section command in privileged EXEC mode. show command | section [include | exclude] regular-expression Syntax Description
Command ModesPrivileged EXEC Command History
Usage GuidelinesIn many cases, it is useful to filter the output of a show command to match a specific expression. Filtering provides some control over the type and amount of information displayed by the system. The show section command provides enhanced filtering capabilities by matching lines in the show command output containing specific expressions as well as matching any entries associated with those expressions. Filtering is especially useful, for example, when displaying large configuration files using the show running-configuration command or the show interfaces command. If the include or exclude keyword is not specified, include is the default. If there are no associated entries for an expression, then only the line matching the expression is displayed. ExamplesThe following examples compare the filtering characteristics of the show running-config | include command with the show running-config | section command. The first example gathers just the lines from the configuration file with "interface" in them. The next example uses the show command section command to gather the lines in the configuration file with "interface" in them as well as any lines associated with those entries. In this example, interface configuration information is captured. Related Commands
show <command> teeTo copy the output of any show command to a file while displaying it on the terminal, use the show command | tee command in privileged EXEC mode. show command | tee [/append] url Syntax Description
Command ModesPrivileged EXEC Command History
Usage GuidelinesTo display all URL prefixes that are supported for this command, use the show command | tee ? command. The tee keyword was chosen to reflect that output is redirected to two locations; the terminal and a file (as a tee plumbing junction redirects water to two different pipes). ExamplesIn the following example, output from the show tech-support command is displayed on-screen while it is written to the file "showoutput.txt" at the host 172.16.101.101 using TFTP: The following example performs the same function as above, but in this case the output is added at the end of any existing data in the file "showoutput.txt": Related Commands
show (Flash file system)To display the layout and contents of a Flash memory file system, use the show flash-filesystem command in EXEC mode. Class A Flash File Systems show flash-filesystem: [all | chips | filesys] Class B Flash File Systems show flash-filesystem:[partition-number:] [all | chips | detailed | err | summary] Class C Flash File Systems show flash-filesystem: Syntax Description
Command ModesEXEC Command History
Usage GuidelinesIf Flash memory is partitioned, the command displays the requested output for each partition, unless you use the partition keyword. The command also specifies the location of the current image. To display the contents of boot Flash memory on Class A or B file systems, use the show bootflash: command as follows: Class A Flash file systems show bootflash: [all | chips | filesys] Class B Flash file systems show bootflash:[partition-number] [all | chips | detailed | err] To display the contents of internal Flash memory on Class A or B file systems, use the show flash: command as follows: Class A Flash file systems show flash: [all | chips | filesys] Class B Flash file systems show flash:[partition-number][all | chips | detailed | err | summary] The show (Flash file system) command replaces the show flash devices command. ExamplesThe output of the show command depends on the type of Flash file system you select. Types include flash:, bootflash:, slot0:, slot1:, slavebootflash:, slaveslot0:, and slaveslot1:. Examples of output from the show flash command are provided in the following sections: •Class A Flash File System •Class B Flash File Systems Although the examples use flash: as the Flash file system, you may also use the other Flash file systems listed. Class A Flash File System The following three examples show sample output for Class A Flash file systems. Table 49 describes the significant fields shown in the display. The following is sample output from the show flash: command.
The following is sample output from the show flash: chips command: The following is sample output from the show flash: filesys command: The following is sample output from the show flash: command: The following example shows detailed information about the second partition in internal Flash memory: Class B Flash File Systems Table 50 describes the significant fields shown in the displays.
The following is sample output from the show flash: all command: The following is sample output from the show flash: all command on a router with Flash memory partitioned: The following is sample output from the show flash: chips command: The following is sample output from the show flash: detailed command: The following is sample output from the show flash: err command: See Table 50 for a description of the fields. The show flash: err command also displays two extra fields: erase and write. The erase field indications the number of erase errors. The write field indicates the number of write errors. The following is sample output from the show flash summary command on a router with Flash memory partitioned. The partition in the Read Only state is the partition from which the Cisco IOS image is being executed. Related Commands
show aliasesTo display all alias commands, or the alias commands in a specified mode, use the show aliases command in EXEC mode. show aliases [mode] Syntax Description
Command ModesEXEC Command History
Usage GuidelinesWhen used without the mode argument, this command will display all aliases currently configured on the system. Use the mode argument to display only the aliases configured for the specified command mode. To display a list of the command mode keywords available for your system, use the show aliases ? command. The following is sample output from the show aliases exec commands. The aliases configured for commands in EXEC mode are displayed. Related Commands
show alignmentTo display alignment errors and spurious memory access errors, use the show alignment command in privileged EXEC mode. show alignment Syntax DescriptionThis command has no arguments or keywords. Command ModesPrivileged EXEC Command History
Usage GuidelinesAlignment Errors Alignment errors are caused by misaligned reads and writes. For example, a two-byte read where the memory address is not an even multiple of two bytes is an alignment error. Alignment errors are caused by a software defect. Alignment errors are reported in the system log and recorded by the router. Output from the show alignment command provides a record of these errors along with potentially useful traceback information. The traceback information for alignment errors can generally be decoded to reveal the function causing the alignment problems. Spurious Memory Access Errors Spurious memory access errors occur when a software process attempts to access memory in a restricted location. A read operation to this region of memory is usually caused when a nonexisting value is returned to a function in the software, or in other words, when a null pointer is passed to a function. Spurious memory access errors are counted and recorded, if possible, by the software. This information is displayed with the show alignment command. ExamplesThe following is sample output from the show alignment command when alignment detection is disabled. To enable alignment detection, use the enable command to enter privileged EXEC mode Router# The following is sample output from the show alignment command when there are no alignment or spurious memory errors: The following is sample output from the show alignment command when there are only alignment errors. The traceback information is necessary to determine the cause and the fix of the alignment errors. Table 51 describes the significant fields shown in the display.
The following is sample output from the show alignment command when there are only spurious memory access errors: Table 52 describes the significant fields shown in the display.
The following is sample output from the show alignment command when there are alignment errors and spurious memory access errors: Related Commands
show archiveTo display information about the files saved in the Cisco IOS configuration archive, use the show archive command in privileged EXEC mode. show archive Syntax DescriptionThis command has no arguments or keywords. Command ModesPrivileged EXEC Command History
ExamplesThe following is sample output from the show archive command: The following is sample output from the show archive command after several archive files of the running configuration have been saved. In this example, the maximum number of archive files to be saved is set to three. Table 53 describes the significant fields shown in the displays.
Related Commands
show archive config differencesTo perform a line-by-line comparison of any two configuration files (accessible through the Cisco IOS File System [IFS]) and generate a list of the differences between them, use the show archive config differences command in user EXEC or privileged EXEC mode. show archive config differences [filename1(path)[filename2(path)][ignorecase]] Syntax Description
Command DefaultIf the filename1(path) and filename2(path) arguments are not specified, the first configuration file is assumed to be the running configuration file and the second to be the startup configuration file. If only the filename1(path) argument is specified, the second configuration file is assumed to be the running configuration file. Command Modes User EXEC Command History
Usage GuidelinesInterpreting the output of the show archive config differences command is dependent on the order in which the two files are configured. Each entry in the generated output list is prefixed with a unique text symbol to indicate the type of difference found. The text symbols and their meanings are as follows: •A minus symbol (-) indicates that the configuration line exists in filename1(path) but not in filename2(path). •A plus symbol (+) indicates that the configuration line exists in filename2(path) but not in filename1(path). •An exclamation point (!) with descriptive comments is used to identify order-sensitive configuration lines whose location is different in filename1(path) than in filename2(path). ExamplesIn this example, a diff operation is performed on the running and startup configuration files. Table 54 shows the configuration files used for this example.
The following is sample output from the show archive config differences command. This sample output displays the results of the diff operation performed on the configuration files in Table 54. +ip subnet-zero +ip name-server 10.4.4.4 +voice dnis-map 1 +dnis 111 interface Ethernet1/0 +no ip address +shutdown +ip default-gateway 10.5.5.5 +ip classless +access-list 110 deny ip any host 10.1.1.1 +access-list 110 deny ip any host 10.1.1.2 +access-list 110 deny ip any host 10.1.1.3 +snmp-server community private RW -no ip subnet-zero interface Ethernet1/0 -ip address 10.7.7.7 255.0.0.0 -no ip classless -snmp-server community public RO Related Commands
show archive config incremental-diffsTo perform a line-by-line comparison of a specified configuration file to the running configuration file and generate a list of the configuration lines that do not appear in the running configuration file, use the show archive config incremental-diffs command in user EXEC or privileged EXEC mode. show archive config incremental-diffs file Syntax Description
Command Modes User EXEC Command History
Usage GuidelinesWhen an incremental diff operation is performed, a list of the configuration lines that do not appear in the running configuration file (in other words, configuration lines that only appear in the specified file that is being compared to the running configuration file) is generated as output. An exclamation point (!) with descriptive comments is used to identify order-sensitive configuration lines whose location is different in the specified configuration file than in the running configuration file. ExamplesIn this example, an incremental diff operation is performed on the startup and running configuration files. Table 55 shows the configuration files used for this example.
The following is sample output from the show archive config incremental-diffs command. This sample output displays the results of the incremental diff operation performed on the configuration files in Table 55. ip subnet-zero ip name-server 10.4.4.4 voice dnis-map 1 dnis 111 interface Ethernet1/0 no ip address shutdown ip default-gateway 10.5.5.5 ip classless access-list 110 deny ip any host 10.1.1.1 access-list 110 deny ip any host 10.1.1.2 access-list 110 deny ip any host 10.1.1.3 snmp-server community private RW Related Commands
show archive config rollback timerTo display settings of the timed rollback, use the show archive config rollback timer command in privileged EXEC mode. show archive config rollback timer Syntax DescriptionThis command has no arguments or keywords. Command ModesPrivileged EXEC (#) Command History
Usage GuidelinesUse the show archive config rollback timer command to display the timed rollback settings, such as the timer type (idle timer or absolute timer) and timer value, after a timed rollback is configured on a router. ExamplesThe following is sample output from the show archive config rollback timer command: Table 56 describes the significant fields shown in the display.
Related Commands
show archive log configTo display entries from the configuration log, use the show archive log config command in privileged EXEC mode. show archive log config {all | record-number [end-number] | user username [session session-number] record-number [end-number] | statistics} [provisioning] [contenttype {plaintext | xml}] [persistent] Syntax Description
Command ModesPrivileged EXEC Command History
Usage GuidelinesIf you do not specify the all keyword, you must specify a record number with the record-number argument. You can optionally specify an end record number with the end-number argument to display a range of records. If you use the end-number argument to specify a record number that does not exist, all records after the starting record number with a record number lower than that specified with the end-number argument are displayed. Specifying the provisioning keyword results in the display appearing as it would in a configuration file, rather than in tabular format. This output includes commands used to change configuration modes and logged configuration commands. This output can be used to set up another router if desired. ExamplesThe following is sample output from the show archive log config command, which displays configuration log entry numbers 1 and 2: Router# show archive log config 1 2 Table 57 describes the significant fields shown in the display.
The following example results in the display of all configuration log files as they would appear in a configuration file rather than in tabular format. In addition to displaying logged commands, the example shows the commands used to change configuration modes that are required to correctly apply the logged commands. The following example results in the display of memory usage statistics for the configuration log: The output is self-explanatory. The following example shows the contents of the archive log in XML format: show as5400To display the hardware details of an application server, use the show as5400 command in privileged EXEC mode. show as5400 Syntax DescriptionThis command has no arguments or keywords. Command ModesPrivileged EXEC (#) Command History
Usage GuidelinesThe show as5400 command provides complex troubleshooting information that pertains to the platform's shared references rather than to a specific interface. ExamplesThe following is sample output from the show as5400 command: Table 58 describes the significant fields shown in the display.
show async bootpTo display the extended BOOTP request parameters that have been configured for asynchronous interfaces, use the show async bootp command in privileged EXEC mode. show async bootp Syntax DescriptionThis command has no arguments or keywords. Command ModesPrivileged EXEC Command History
ExamplesThe following is sample output from the show async bootp command: Table 59 describes the significant fields shown in the display.
Related Commands
show autoupgrade configuration unknownTo display all of the unknown start-up configuration lines that the auto-upgraded Cisco IOS software image does not understand, use the show autoupgrade configuration unknown command in privileged EXEC mode. show autoupgrade configuration unknown Syntax DescriptionThis command has no arguments or keywords. Command ModesPrivileged EXEC (#) Command History
Usage GuidelinesUse the show autoupgrade configuration unknown command to view any invalid start-up configuration. This command prints invalid start-up configuration data only when run from an an image which was upgraded using the Auto-Upgrade Manager. This command output is useful when you are upgrading to an image with a different feature set. ExamplesThe following example shows how to view the invalid start-up configuration lines that the Cisco IOS software image, upgraded on the router using AUM, does not understand: Related Commands
show bcm560xTo display the BCM560x hardware table information, use the show bcm560X command in user EXEC or privileged EXEC mode. show bcm560x name {offset | all} [raw] Syntax Description
Command Modes User EXEC (>) Command History
ExamplesThe following is sample output from the show bcm560X all command: show bootflash:To display information about the bootflash: file system, use the show bootflash: command in user EXEC or privileged EXEC mode. show bootflash: [all | chips | filesys] Syntax Description
DefaultsThis command has no default settings. Command Modes User EXEC Command History
ExamplesThis example shows how to display information about the file system status: This example shows how to display image information: This example shows how to display all bootflash information: Related Commands
show bootvarTo display the contents of the BOOT variable, the name of the configuration file pointed to by the CONFIG_FILE variable, the contents of the BOOTLDR variable, and the configuration register setting, use the show bootvar command in user EXEC or privileged EXEC mode. show bootvar Syntax DescriptionThis command has no arguments or keywords. Command Modes User EXEC Command History
Usage GuidelinesSupported Platforms Other than the Cisco 7600 Series Router The show bootvar command replaces the show boot command. The show bootvar command allows you to view the current settings for the following variables: •BOOT •CONFIG_FILE •BOOTLDR The BOOT variable specifies a list of bootable images on various devices. The CONFIG_FILE variable specifies the configuration file used during system initialization. The BOOTLDR variable specifies the flash device and filename containing the rxboot image that ROM uses for booting. You set these variables with the boot system, boot config, and boot bootldr global configuration commands, respectively. When you use this command on a device with multiple Route Switch Processor (RSP) cards (Dual RSPs), this command also shows you the variable settings for both the master and slave RSP card. Cisco 7600 Series Router The show bootvar command displays information about the BOOT environmental variable. The command output depends on how you configure the boot statement as follows: •If you enter the boot system flash bootflash:sup720_image command in the boot configuration, then the show bootvar command output displays the bootflash information. •If you enter the boot system flash sup-bootflash:sup720_image command in the boot configuration, then the show bootvar command output displays the sup-bootflash information. This action is the correct way of configuring the boot statement. The show bootvar command is available from the switch processor command-line interface (CLI) and the route processor CLI. From the switch processor CLI, the display is always bootflash. With either the bootflash or the sup-bootflash boot statement, the switch boots correctly. You should use sup-bootflash in the boot configuration statement because the image is stored in the switch processor bootflash; the route processor sees the image as sup-bootflash. The number displayed after the image name (for example, c6sup12-js-mz.121-13.E,12) indicates the number of times that the Cisco 7600 series router tries to reboot the file before giving up. ExamplesSupported Platforms Other than the Cisco 7600 Series Router The following is sample output from the show bootvar command: In this example, the BOOT variable contains a null string; that is no bootable images are specified. The CONFIG_FILE variable points to the configuration file in NVRAM as the startup (initialization) configuration. The run-time value for the CONFIG_FILE variable points to the router-configuration file on the flash memory card inserted in the first slot of the RSP card. That is, during the run-time configuration, you have modified the CONFIG_FILE variable using the boot config command, but you have not saved the run-time configuration to the startup configuration. To save your run-time configuration to the startup configuration, use the copy system:running-config nvram:startup-config command. If you do not save the run-time configuration to the startup configuration, then the system reverts to the saved CONFIG_FILE variable setting for initialization information upon reload. In this sample, the system reverts to NVRAM for the startup configuration file. The BOOTLDR variable does not yet exist. That is, you have not created the BOOTLDR variable using the boot bootldr global configuration command. The following example is output from the show bootvar command for a Cisco 7513 router configured for high system availability (HSA): Table 60 describes the significant fields shown in the displays.
Cisco 7600 Series Router This example shows how to display information about the BOOT environment variable: The number displayed after the image name (for example, c6sup12-js-mz.121-13.E,12) indicates the number of times that the Cisco 7600 series router tries to reboot the file before giving up. Related Commands
show buffersTo display detailed information about the buffer pools on the network server when Cisco IOS, Cisco IOS Software Modularity, or Cisco IOS XE images are running, use the show buffers command in user EXEC or privileged EXEC mode. show buffers [{address hex-address | failures | pool pool-name | detailed | processes | {all | assigned [process-id] | free | old | input-interface interface-type interface-number} [pool pool-name]} [dump | header | packet | location pool-location]] Cisco Catalyst 4500e Series Switches running IOS XE software show buffers [detailed process id {address hex-address | all | assigned | failures | free | input-interface interface-type interface-number | old | pool pool-name}[dump | header | packet | location pool-location]] Syntax Description
Command DefaultIf no options are specified, all buffer pool information is displayed. Command Modes User EXEC (>) Command History
ExamplesExample output varies between Cisco IOS, Cisco IOS Software Modularity, and Cisco IOS XE software images. To view the appropriate output, choose one of the following sections: •Cisco IOS Software •Cisco IOS Software Modularity •Cisco Catalyst 4500e Series Switches running IOS XE software Cisco IOS Software The following is sample output from the show buffers command with no arguments, showing all buffer pool information: The following is sample output from the show buffers command with no arguments, showing onlybuffer pool information for Huge buffers. This output shows a highest total of five Huge buffers created five days and 18 hours before the command was issued. The following is sample output from the show buffers command with no arguments, showing only buffer pool information for Huge buffers. This output shows a highest total of 184 Huge buffers created one hour, one minute, and 15 seconds before the command was issued. The following is sample output from the show buffers command with an interface type and interface number: 16 max cache size, 16 in cache Table 61 describes the significant fields shown in the display.
Cisco IOS Software Modularity The following is sample output from the show buffers command using a Cisco IOS Modularity image from Cisco IOS Release 12.2(18)SXF4 and later releases. Two new output fields were introduced—Public buffer heads and Temporary buffer heads—and are shown within comments in the following sample output. Table 62 describes the significant fields shown in the display that are different from the fields in Table 61.
Cisco Catalyst 4500e Series Switches running IOS XE software The following is sample output from the show buffers command on a Cisco Catalyst 4500e switch, using a Cisco IOS image from Cisco IOS XE Release 3.1.0.SG and later releases. PDS Public buffers and Packet information was added—and are shown within comments in the following sample output. The following is sample shows how to run the show buffers detailed command on a Cisco Catalyst 4500e switch, using a Cisco IOS image from Cisco IOS XE Release 3.1.0.SG and later releases and the various keywords and arguments (Explained in the Syntax Description Table) available. show buffers summaryTo display the buffers usage summary for all caller and for all buffer pools, use the show buffers summary command in privileged EXEC mode. show buffers summary Syntax DescriptionThis command has no arguments or keywords. Command DefaultAll buffer usage summary information is displayed. Command ModesPrivileged EXEC (#) Command History
ExamplesThe following is sample output from the show buffers summary command: Table 61 describes the significant fields shown in the display.
Related Commands
show c2600To display information for troubleshooting the Cisco 2600 series router, use the show c2600 command in EXEC mode. show c2600 Syntax DescriptionThis command has no arguments or keywords. Command ModesEXEC Command History
Usage GuidelinesThe show c2600 command provides complex troubleshooting information that pertains to the platform's shared references rather than to a specific interface. ExamplesThe following is sample output from the show c2600 command: Table 64 describes the significant fields shown in the display.
Related Commands
show c7200To display information about the CPU and midplane for Cisco 7200 series routers, use the show c7200 command in EXEC mode. show c7200 Syntax DescriptionThis command has no arguments or keywords. Command ModesEXEC Command History
Usage GuidelinesYou can use the output of this command to determine whether the hardware version level and upgrade is current. The information is generally useful for diagnostic tasks performed by technical support only. ExamplesThe following is sample output from the show c7200 command: show catalyst6000To display the information about the Cisco 7600 series router, use the show catalyst6000 command in user EXEC or privileged EXEC mode. show catalyst6000 {all | chassis-mac-address | switching-clock | traffic-meter} Syntax Description
Defaultsall Command Modes User EXEC Command History
Usage GuidelinesIf you enter the switching-clock keywords, the Cisco 7600 series router displays whether switching of the redundant clock sources on the backplane is allowed if the active clock source fails. The Cisco 7600 series router has either 64 or 1024 MAC addresses that are available to support the software features. You can enter the show catalyst6000 chassis-mac-address command to display the MAC-address range on your chassis. ExamplesThis example shows how to display the MAC-address ranges and the current and peak traffic-meter readings: This example shows how to display the MAC-address ranges: This example shows how to display the current and peak traffic-meter readings: This example shows how to display the failure recovery mode of the switching clock: Related Commands
show clsTo display the current status of all Cisco link services (CLS) sessions on the router, use the show cls command in EXEC mode. show cls [brief] Syntax Description
DefaultsWithout the brief keyword, displays complete output. Command ModesEXEC Command History
Usage GuidelinesThe Cisco link service (CLS) is used as the interface between data link users (DLUs), such as DLSw, LAN Network Manager (LNM), downstream physical unit (DSPU), and SNASw, and their corresponding data link circuits (DLCs) such as Logic Link Control (LLC), VDLC, and Qualified Logic Link Control (QLLC). Each DLU registers a particular service access point (SAP) with CLS, and establishes circuits through CLS over the DLC. The show cls command displays the SAP values associated with the DLU and the circuits established through CLS. For further information about CLS, use the Release 12.2 Cisco IOS Bridging and IBM Networking Configuration Guide. ExamplesThe following is sample output from the show cls command: The following is sample output from the show cls brief command: Bridging VDLC VDLC650 The examples show two DLUs—SNASw and DLSw—active in the router. SNASw uses a SAP value of 0x04, and the associated DLC port is VDLC650. SNASw has a circuit established between MAC addresses 1234.4000.0001 and 1234.4000.0002 using source and destination SAPs 04 and 04. DLSw is a bridging protocol and uses VDLC1000 and VDLC650 ports. There are no circuits in place at this time. In the output from the show cls command (without the brief argument), the values of timers and counters applicable to this circuit are displayed. Related Commands
show config idThe configuration change tracking identifier (CTID) assigns a version number to each saved version of the running-config file. To display output about the versions, use the show config id command in privileged EXEC mode. show config id [detail] Syntax Description
Command DefaultThis command is disabled by default. If this command is not entered, the management system has to query the device for the current running-config file and then compare the results to the last known configuration to determine if a change has been made. Command ModesPrivileged EXEC (#) Command History
Usage GuidelinesThis configuration infrastructure command assigns a version number that is updated every time the running-config file is changed. This version number is called the configuration change tracking identifier or CTID. The CTID can be used to compare configuration files to track configuration changes and take appropriate actions (for example, a configuration rollback). Config Logger can also use the CTID to determine if there have been any changes to the running-config file. CTID makes the management system more efficient by presenting information that indicates a change has been made to the running-config file. Without CTID, the management system has to query the device for the current running-config file and then compare the results to the last known configuration to determine if a change has been made. ExamplesThe following example shows that the current running-config file is version 4 and that this file was saved on June 15, 2006 at 7.572 seconds after 3:02 p.m.: The following example shows that the current running-config file is version 9 and that this file was last saved on June 18, 2006 at 34.431 seconds after 6:34 p.m. The file was saved by the system and changed from Init: Field descriptions are self-explanatory. Related Commands
show configuration idTo display output about configuration versions, use the show configuration id command in privileged EXEC mode. show configuration id [detail] Syntax Description
Command DefaultThis command is disabled by default. If this command is not entered, the management system has to query the device for the current running-config file and then compare the results to the last known configuration to determine if a change has been made. Command ModesPrivileged EXEC (#) Command History
Usage GuidelinesThis configuration infrastructure command assigns a version number that is updated every time the running-config file is changed. This version number is called the configuration change tracking identifier (CTID). The CTID assigns a version number to each saved version of the running-config file. The CTID can be used to compare configuration files to track configuration changes and take appropriate actions (for example, a configuration rollback). Config Logger can also use the CTID to determine if there have been any changes to the running-config file. CTID makes the management system more efficient by presenting information that indicates a change has been made to the running-config file. Without CTID, the management system has to query the device for the current running-config file and then compare the results to the last known configuration to determine if a change has been made. ExamplesThe following example shows that the current running-config file is version 4 and that this file was saved on June 15, 2006 at 7.572 seconds after 3:02 p.m.: The following example shows that the current running-config file is version 9 and that this file was last saved on June 18, 2006 at 34.431 seconds after 6:34 p.m. The file was saved by the system and changed from Init. The field descriptions are self-explanatory. Related Commands
show configuration lockTo display information about the lock status of the running configuration file during a configuration replace operation, use the show configuration lock command in privileged EXEC mode. show configuration lock Syntax DescriptionThis command has no arguments or keywords. Command ModesPrivileged EXEC Command History
ExamplesThe following is sample output from the show configuration lock command when the running configuration file is locked by another user. Cisco IOS Release 12.2(25)S, Release 12.2(28)SB, Release 12.3(14)T, and Later Releases The following is sample output from the show configuration lock command when the running configuration file is not locked by another user. Cisco IOS Release 12.0(31)S, 12.2(33)SRA, and Later Releases Table 65 describes the significant fields shown in the displays.
The following example shows how to configure the configuration file for single user auto configuration mode (using the configuration mode exclusive auto command). Use the configure terminal command to enter global configuration mode and lock the configuration mode exclusively. Once the Cisco IOS configuration mode is locked exclusively, you can verify the lock using the show configuration lock command. Related Commands
show contextTo display information stored in NVRAM when an unexpected system reload (system exception) occurs, use the show context command in user EXEC or priviledged EXEC mode. show context [summary | all | slot slot-number [crash-index] [all] [debug]] Syntax Description
Command ModesUser EXEC Privileged EXEC Command History
Usage GuidelinesThe display from the show context command includes the following information: •Reason for the system reboot •Stack trace •Software version •The signal number, code, and router uptime information •All the register contents at the time of the crash Note This command is primarily for use by Cisco technical support representatives for analyzing unexpected system reloads. Output for this command will vary by platform. Context information is specific to processors and architectures. For example, context information for the Cisco 2600 series router differs from that for other router types because the Cisco 2600 runs with an M860 processor. ExamplesThe following is sample output from the show context command following a system failure: The following is sample output from the show context summary command on a Cisco 12012 router. The show context summary command displays a summary of all the crashes recorded for each slot (line card). The following is sample output from the show context command following an unexpected system reload on a Cisco 2600 series router. Table 66 describes the significant fields shown in the display.
Related Commands
show controllers (GRP image)To display information that is specific to the hardware, use the show controllers command in privileged EXEC mode. show controllers [atm slot-number | clock | csar [register] | csc-fpga | dp83800 | fab-clk | fia [register] | pos [slot-number] [details] | queues [slot-number] | sca | xbar] Syntax Description
Command ModesPrivileged EXEC Command History
Usage GuidelinesThis information provided by this command is intended for use only by technical support representatives in analyzing system failures in the field. ExamplesThe following is sample output from the show controllers pos command for a Cisco 12012: Related Commands
show controllers (line card image)To display information that is specific to the hardware on a line card, use the attach command in privileged EXEC mode to connect to the line card and then use the show controllers command in privileged EXEC mode or the execute-on command in privileged EXEC mode. show controllers atm [[port-number] [all | sar | summary]] show controllers fia [register] show controllers {frfab | tofab} {bma {microcode | ms-inst | register} | qelem start-queue-element [end-queue-element] | qnum start-queue-number [end-queue-number] | queues | statistics} show controllers io show controllers l3 show controllers pos {framers | queues | registers | rxsram port-number queue-start-address [queue-length] | txsram port-number queue-start-address [queue-length]} show controllers events [clear | punt-sniff [none | word1 | word2] | punt-verbose [all]] Syntax Description
Command ModesPrivileged EXEC Command History
Usage GuidelinesThis information displayed by this command is of use only to technical support representatives in analyzing unexpected system failures in the field. It is documented here in case you need to provide the displayed statistics to an technical support engineer. Cisco 10000 Series Router Usage Guidelines In releases prior to Cisco IOS Release 12.2(33)SB, when you configure the t1 loopback remote command on the local router, the command also displays in the running-config file of the far-end router. This is due to the route processor (RP) updating an incorrect parameter when it receives the loopback event message from the line card for loopback requests from the far end. In Cisco IOS Release 12.2(33)SB, the RP updates the correct parameter and the show controllers command correctly displays the loopback CLI commands applied on the local end and displays the loopback events and status received from the line card in response to loopback requests from the far end. This change in behavior affects the following line cards and is documented in the CSCsm84447 caveat: •4-port channelized STM1 •1-port channelized OC-12 •6-port channelized T3 •4-port half-height channelized T3 In Cisco IOS Release 12.2(33)SB, the output from the show controller command includes line code information for the 6-port channelized T3 line card and the 8-port E3/DS3 line card. However, because SONET line cards do not have a direct physical link at the T3 or E3 level, the output from the show controller t3 command does not include line code information. In Cisco IOS Release 12.2(31)SB, the output from the show controller command displays line code information. The output of the show controller t3 command for SONET-based T3 also includes line code information. Cisco 12000 Series Router Usage Guidelines The packets processed by a line card are either sent to a route processor or a line card in the form of Cisco cells. To track the packets sent to a route processor from a line card is essential for troubleshooting. The keywords punt-sniff and punt-verbose have been added for the command show controllers events to identify the packets sent to RP from LC. By default, the feature is enabled and packets punt to route processor are displayed using the command show controllers events punt-verbose. To view all the zero and non-zero punt counters use the command show controllers events punt-verbose all. To clear all the line card events and counters including resetting the packets to be sniffed to zero, executing the command show controllers events clear. Packets sent to route processor from line card can be sniffed by specifying the hexa-decimal value of the word. Packets can only be sniffed if the word along with the hexa-decimal value is specified. Specifying the location of the word, sniffs packets from the particular location. To reset the counters of packets to be sniffed to zero, execute the command show controllers events punt-sniff none. For example, use the command show controllers events punt-sniff word1 0x60000000 to sniff packets punt to RP with the hexa-decimal value 0x60000000. As the location is not specified, it searches the entire buffer for the value 0x60000000. Packets punt to RP can also be sniffed by specifying a particular location using the command show controllers events punt-sniff word1 0x60000000 34. ExamplesBecause you are executing this command on the line card, you must use the execute-on command to use the show command, or you must connect to the card using the attach command. All examples in this section use the execute-on command The following is partial sample output from the show controllers atm command: The following is partial sample output from the show controllers command: The following is partial sample output from the show controllers pos framers command: The following is partial sample output from the show controllers fia command: The following is a sample output from the show controllers events command: The following is a sample output from the show controllers events punt-verbose command: The following is a partial sample output from the show controllers events punt-verbose all command which displays the zero and non-zero value of packets punt to RP from LC: The following is a sample output from the show controllers events clear command: The following is a sample output from the show controllers events punt-sniff word1 0x60000000 command. This command is used to sniff a packet with a hexa-decimal value 0x60000000 from the start of the buffer header of the packet being punt to RP: The following is a sample output from the show controllers events punt-sniff word1 0x60000000 34 command. This command is used to sniff a packet with a hexa-decimal value 0x60000000 0 at the location 34 from the start of the buffer header of the packet being punt to RP: The following is a sample output from the show controllers events punt-sniff none command. This command is used to clear the counter of packets to be sniffed: Related Commands
show controllers loggingTo display logging information about a Versatile Interface Processor (VIP) card, use the show controllers logging command in privileged EXEC mode. show controllers vip slot-number logging Syntax Description
Command ModesPrivileged EXEC Command History
Usage GuidelinesThis command displays the state of syslog error and event logging, including host addresses, and whether console logging is enabled. When enabled, "trap logging" allows messages to be sent to a remote host (a syslog server). ExamplesThe following is sample output from the show controllers logging command: Table 67 describes the significant fields shown in the display.
Related Commands
show controllers tech-supportTo display general information about a Versatile Interface Processor (VIP) card when reporting a problem, use the show controllers tech-support command in privileged EXEC mode. show controllers vip slot-number tech-support Syntax Description
Command ModesPrivileged EXEC Command History
Usage GuidelinesUse this command to help collect general information about a VIP card when you are reporting a problem. This command displays the equivalent of the following show commands for the VIP card: •more system:running-config •show buffers •show controllers •show interfaces •show processes cpu •show processes memory •show stacks •show version For a sample display of the show controllers tech-support command output, refer to these show commands. Related Commands
show coverage historyTo display the system history table, use the show coverage history command in privileged EXEC mode. show coverage history [all | first number-of-entries | last number-of-entries | status] Syntax Description
Command ModesPrivileged EXEC (#) Command History
ExamplesThe following is sample output from the show coverage history command. The output is self-explanatory. Related Commands
show data-corruptionTo display data inconsistency errors of the present software version, use the show data-corruption command in user EXEC or privileged EXEC mode. show data-corruption Syntax DescriptionThis command has no arguments or keywords. Command Modes User EXEC (>) Command History
Usage GuidelinesUse this command to display all data inconsistency errors or the corrupt data. If there are no data errors, the "No data inconsistency errors have been recorded" message is displayed. ExamplesThe following is sample output from show data-corruption command. The fields are self-explanatory. show debuggingTo display information about the types of debugging that are enabled for your router, use the show debugging command in privileged EXEC mode. show debugging Syntax DescriptionThis command has no arguments or keywords. Command ModesPrivileged EXEC (#) Command History
ExamplesThe following is sample output from the show debugging command. In this example, the remote host is not configured or connected. The following is sample output from the show debugging command when user-group debugging is configured: ! Table 68 describes the significant fields in the output.
show declassifyTo display the state of the declassify function (enabled, in progress, and so forth) and the sequence of declassification steps that will be performed, use the show declassify command in global configuration mode. show declassify Syntax DescriptionThis command has no arguments or keywords. Note The show declassify command is supported on the Cisco 3200 series routers only. Command ModesGlobal configuration Command History
ExamplesThe following example is sample output for the show declassify command: Table 69 describes the significant fields shown in the display.
Related Commands
show derived-configTo display the composite results of all the configuration commands that apply to an interface, including commands that come from sources such as static templates, dynamic templates, dialer interfaces, and authentication, authorization, and accounting (AAA) per-user attributes, use the show derived-config command in privileged EXEC mode. show derived-config [interface type number] Syntax Description
Command ModesPrivileged EXEC Command History
Usage GuidelinesConfiguration commands can be applied to an interface from sources such as static templates, dynamic templates bound by resource pooling, dialer interfaces, AAA per-user attributes and the configuration of the physical interface. The show derived-config command displays all the commands that apply to an interface. The output for the show derived-config command is nearly identical to that of the show running-config command. It differs when the configuration for an interface is derived from a template, a dialer interface, or some per-user configuration. In those cases, the commands derived from the template, dialer interface, and so on, will be displayed for the affected interface. If the same command is configured differently in two different sources that apply to the same interface, the command coming from the source that has the highest precedence will appear in the display. ExamplesThe following examples show sample output for the show running-config and show derived-config commands for serial interface 0:23 and dialer interface 0. The output of the show running-config and show derived-config commands is the same for dialer interface 0 because none of the commands that apply to that interface are derived from any sources other than the configuration of the dialer interface. The output for the show running-config and show derived-config commands for serial interface 0:23 differs because some of the commands that apply to serial interface 0:23 come from dialer interface 0. Related Commands
show diagnostic cnsTo display the information about the CNS subject, use the show diagnostic cns command in user EXEC or privileged EXEC mode. show diagnostic cns {publish | subscribe} Syntax Description
DefaultsThis command has no default settings. Command Modes User EXEC Command History
Usage GuidelinesThis command is not supported on Cisco 7600 series routers that are configured with a Supervisor Engine 2. The CNS subsystem communicates with remote network applications through the CNS-event agent and follows the publish and subscribe model. An application sets itself up to receive events by subscribing to the approprate event subject name. ExamplesThis example shows how to display the subject with which the diagnostic results is published: This example shows how to display the subscribed subject: Related Commands
show diagnostic sanityTo display sanity check results, use the show diagnostic sanity command in privileged EXEC mode. show diagnostic sanity Syntax DescriptionThis command has no arguments or keywords. DefaultsDisplays information for all the Gigabit Ethernet WAN interfaces in the Cisco 7600 series router. Command ModesPrivileged EXEC Command History
Usage GuidelinesThe sanity check runs a set of predetermined checks on the configuration with a possible combination of certain system states to compile a list of warning conditions. The checks are designed to look for anything that seems out of place and are intended to serve as an aid to maintaining the system sanity. The following is a list of the checks that are run and the action taken when the condition is found: •Checks whether the default gateways are reachable. If so, the system stops pinging. •If a port auto-negotiates to half duplex, the system flags it. Trunking Checks •If a trunk port has the mode set to "on," the system flags it. •If a port is trunking and mode is auto, the system flags it. •If a trunk port is not trunking and the mode is desirable, the system flags it. •If a trunk port negotiates to half duplex, the system flags it. Channeling Checks •If a port has channeling mode set to on, the system flags it. •If a port is not channeling and the mode is set to desirable, the system flags it. •If a VLAN has a Spanning-Tree root of 32K (root is not set), the system flags it. Spanning-Tree VLAN Checks •If a VLAN has a max age on the Spanning-Tree root that is different than the default, the system flags it. •If a VLAN has a fwd delay on the Spanning-Tree root that is different than the default, the system flags it. •If a VLAN has a fwd delay on the bridge that is different than the default, the system flags it. •If a VLAN has a fwd delay on the bridge that is different than the default, the system flags it. •If a VLAN has a hello time on the bridge that is different than the default, the system flags it. Spanning-Tree Port Checks •If a port has a port cost that is different than the default, the system flags it. •If a port has a port priority that is different than the default, the system flags it. UDLD Checks •If a port has UDLD disabled, the system flags it. •If a port had UDLD shut down, the system flags it. •If a port had a UDLD undetermined state, the system flags it. Assorted Port Checks •If a port had receive flow control disabled, the system flags it. •If a trunk port had PortFast enabled, the system flags it. •If a inline power port has any of the following states: –denied –faulty –other –off The system flags it. •If a port has a native VLAN mismatch, the system flags it. •If a port has a duplex mismatch, the system flags it. Bootstring and Config Register Checks •The config register on the primary supervisor engine (and on the secondary supervisor engine if present) must be one of the following values: 0x2 , 0x102, or 0x2102. •The system verifies the bootstring on the primary supervisor engine (and on the secondary supervisor engine if present). The system displays a message if the bootstring is empty. •The system verifies that every file is specified in the bootstring. The system displays a message if the file is absent or shows up with a wrong checksum. If only device: is specified as a filename, then the system verifies that the first file is on the device. Assorted Checks •The system displays a message if IGMP snooping is disabled. •The system displays a message if any of the values of the snmp community access strings {RO,RW,RW-ALL} is the same as the default. •The system displays a message if any of the modules are in states other than "Ok." •The system displays a message that lists all the tests that failed (displayed as an "F") in the show test all command. •The system displays a message if *fast is not configured on the switch anywhere. •The system displays a message if there is enough room for the crashinfo file on the bootflash:. •The system displays a message if multicast routing is enabled globally but is not applied to all interfaces. •The system displays a message if IGMP snooping is disabled and RGMP is enabled. ExamplesThis example displays samples of the messages that could be displayed with the show diagnostic sanity command: show diskTo display flash or file system information for a disk, use the show disk command in user or privileged EXEC mode. show {disk0 | disk1} [all | filesys] Syntax Description
Command Modes User EXEC Command History
Usage GuidelinesThe show disk command is supported only on platforms that have a disk file system. Note The name of the ATA monlib file may contain a platform name that does not match the platform that you are using. Different platforms may have a similar or the same name for their ATA monlib file. ExamplesThe following example displays information about disk 0. The output is self-explanatory. show disk0:To display flash or file system information for a disk located in slot 0, use the show disk command in user EXEC or privileged EXEC mode. show disk0: [all | filesys] Syntax Description
Command Modes User EXEC Command History
Usage GuidelinesThe show disk0: command is supported only on platforms that have a disk file system located in slot 0. Use the show disk0: command to display details about the files in a particular ATA PCMCIA flash disk memory card. For more information regarding file systems and flash cards, access the PCMCIA Filesystem Compatibility Matrix and Filesystem Information document at the following URL: http://www.cisco.com/en/US/partner/products/hw/routers/ps341/products_tech_note09186a00800a7515.shtml Note The name of the ATA monlib file may contain a platform name that does not match the platform that you are using. Different platforms may have a similar name or the same name for their ATA monlib file. ExamplesThe following examples show displays of information about the flash disks or file system information for a disk. The output is self-explanatory. Related Commands
show disk1:To display flash or file system information for a disk located in slot 1, use the show disk1: command in user EXEC or privileged EXEC mode. show disk1: [all | filesys] Syntax Description
Command Modes User EXEC Command History
Usage GuidelinesThe show disk1: command is supported only on platforms that have a disk file system. Use the show disk01: command to display details about the files in a particular ATA PCMCIA flash disk memory card located in slot 1. For more information regarding file systems and flash cards, access the PCMCIA Filesystem Compatibility Matrix and Filesystem Information document at the following URL: http://www.cisco.com/en/US/partner/products/hw/routers/ps341/products_tech_note09186a00800a7515.shtml Note The name of the ATA monlib file may contain a platform name that does not match the platform that you are using. Different platforms may have a similar name or the same name for their ATA monlib file. ExamplesThe following examples show displays of information about the flash disks or file system information for a disk. The output is self-explanatory. Related Commands
show environmentTo display temperature, voltage, fan, and power supply information, use the show environment command in user EXEC or privileged EXEC mode. show environment [alarms | all | fans | hardware | last | leds | power-supply | table | temperature | voltages] Cisco 7000 Series, Cisco 7200 Series, Cisco 7304, and Cisco 7500 Series show environment [all | last | table] Cisco ASR 1000 Series show environment {all | counters | history sensor | location sensor | sensor sensor | table sensor} Syntax Description
Command DefaultIf no options are specified, the default is all. Command ModesUser EXEC (>) Privileged EXEC (#) Command History
Usage GuidelinesThe availability of keywords depends on your system and platform. The command does not support SPAs on the Cisco 7200 series and on the NPE-G2 in the Cisco 7200 VXR routers. A routine runs once a minute that reads environmental measurements from sensors and stores the output into a buffer. For shared port adapters (SPAs), the temperature and voltage sensors are read every few seconds to get environmental data. The environmental buffer is displayed on the console when you use the show environment command. If a measurement exceeds desired margins, but has not exceeded fatal margins, a warning message is printed to the system console. The system software queries the sensors for measurements once a minute, but warnings for a given test point are printed at most once every hour for sensor readings in the warning range and once every 5 minutes for sensor readings in the critical range. If a measurement is out of line within these time segments, an automatic warning message appears on the console. As noted, you can query the environmental status with the show environment command at any time to determine whether a measurement is at the warning or critical tolerance. A SPA is shut down when any of the SPA environment readings exceed the shutdown threshold. If a shutdown occurs because of detection of fatal environmental margins, the last measured value from each sensor is stored in internal nonvolatile memory. For environmental specifications, refer to the hardware installation and configuration publication for your individual chassis. For network processor engines (NPEs), network services engines (NSEs), line cards, and modular services cards (MSCs), environmental information is recorded in the CISCO-ENVMON-MIB. SPAs are not supported by the CISCO-ENVMON-MIB. In Cisco IOS Release 12.2(20)S2 and later, the CISCO-ENTITY-SENSOR-MIB supports environmental information for SPAs, as well as NPEs, NSEs, line cards, and MSCs. If the Cisco 12000 series GSR exceeds environmental conditions, a message similar to the following is displayed on the console: Note Blower temperatures that exceed environmental conditions do not generate a warning message. You can also enable Simple Network Management Protocol (SNMP) notifications (traps or informs) to alert a network management system (NMS) when environmental thresholds are reached using the snmp-server enable traps envmon and snmp-server host global configuration commands. Whenever Cisco IOS software detects a failure or recovery event from the DRPS unit, it sends an SNMP trap to the configured SNMP server. Unlike console messages, only one SNMP trap is sent when the failure event is first detected. Another trap is sent when the recovery is detected. Cisco AS5300 DRPS software reuses the MIB attributes and traps defined in CISCO-ENVMON-MIB and CISCO-ACCESS-ENVMON-MIB. CISCO-ENVMON-MIB is supported by all Cisco routers with RPS units, and CISCO-ACCESS-ENVMON-MIB is supported by the Cisco 3600 series routers. A power supply trap defined in CISCO-ENVMON-MIB is sent when a failure is detected and when a failure recovery occurs for the following events: input voltage fail, DC output voltage fail, thermal fail, and multiple failure events. A fan failure trap defined in CISCO-ENVMON-MIB is sent when a fan failure or recovery event is detected by Cisco IOS software. A temperature trap defined in CISCO-ACCESS-ENVMON-MIB is sent when a board over-temperature condition is detected by Cisco IOS software. CISCO-ACCESS-ENVMON-MIB also defines an over-voltage trap. A similar trap is defined in CISCO-ENVMON-MIB, but it requires the ciscoEnvMonVoltageStatusValue in varbinds. This value indicates the current value of the voltage in the RPS. With Cisco AS5300 RPS units, the current voltage value is not sent to the motherboard. CISCO-ENVMON-MIB is extended to add a new enumerated value, internalRedundant(5), for MIB attribute ciscoEnvMonSupplySource. This is used to identify a RPS unit. ExamplesCisco ASR 1000 Series Routers In the following example, the show environment all command displays system temperature, voltage, fan, and power supply conditions. (It does not display environmental information for SPAs.) The State column in show environment all output should show "Normal" except for fans where it indicates fan speed. A fan speed of 65% is normal. Table 70 describes the significant fields shown in the display.
Cisco 7000 Series Routers, Cisco 7200 Series Routers In the following example, the typical show environment display is shown when no warning conditions are in the system for the Cisco 7000 series and Cisco 7200 series routers. This information may vary slightly depending on the platform you are using. The date and time of the query are displayed, along with the data refresh information and a message indicating that there are no warning conditions. Table 71 describes the significant fields shown in the display.
NPE-G2 in Cisco 7200 VXR Routers In the following example, additional temperature and voltage readings for the NPE-G2 in the Cisco 7200 VXR router are displayed by the show environment all command. Power supplies 1 and 2 are on, and all monitored variables are within the normal operating range.
In the following example, the show environment last command displays the previously saved measurements (readings) from the last environmental reading before the router was shut down. The command also displays the reason why the router was shut down, which was "power supply shutdown" in this case.
In the following example, the show environment table command displays threshold levels in a table format of the environmental monitor parameters. It displays the high warning, high critical, and high shutdown temperature thresholds of the NPE inlet, NPE outlet, and CPU Die. It also displays the low and high critical voltage thresholds, and low and high shut down voltage thresholds for the power rails on the NPE-G2 in the Cisco 7200 VXR. Note The low range temperatures, such as the LowShut, LowCrit, and LowWarn temperature thresholds, are not checked and are not displayed on the NPE-G2. Also the warning voltage thresholds, such as LowWarn and HighWarn, are not checked and are not displayed on the NPE-G2.
Cisco 7000 Series Routers The following are examples of messages that display on the system console when a measurement has exceeded an acceptable margin: The system displays the following message if voltage or temperature exceed maximum margins: In the following example, there have been two intermittent power failures since a router was turned on, and the lower power supply is not functioning. The last intermittent power failure occurred on Monday, June 10, 1996, at 11:07 p.m. Table 75 describes the significant fields shown in the display.
The following example is for the Cisco 7000 series routers. The router retrieves the environmental statistics at the time of the last shutdown. In this example, the last shutdown was Friday, May 19, 1995, at 12:40 p.m., so the environmental statistics at that time are displayed. Table 76 describes the significant fields shown in the display.
The following example shows sample output for the current environmental status in tables that list voltage and temperature parameters. There are three warning messages: one each about the lower power supply, the airflow temperature, and the inlet temperature. In this example, voltage parameters are shown to be in the normal range, airflow temperature is at a critical level, and inlet temperature is at the warning level. Table 77 describes the significant fields shown in the display.
Cisco 7200 Series Routers The system displays the following message if the voltage or temperature enters the "Warning" range: The system displays the following message if the voltage or temperature enters the "Critical" range: The system displays the following message if the voltage or temperature exceeds the maximum margins: The following message is sent to the console if a power supply has been inserted or removed from the system. This message relates only to systems that have two power supplies. The following message is sent to the console if a power supply has been powered on or off. In the case of the power supply being shut off, this message can be due to the user shutting off the power supply or to a failed power supply. This message relates only to systems that have two power supplies. The following is sample output from the show environment all command on the Cisco 7200 series routers when there is a voltage warning condition in the system: Table 78 describes the significant fields shown in the display.
The following example is for the Cisco 7200 series routers. This example shows the measurements immediately before the last shutdown and the reason for the last shutdown (if appropriate). Table 79 describes the significant fields shown in the display.
The following example is for the Cisco 7200 series routers. This information lists the temperature and voltage shutdown thresholds for each sensor. Table 80 describes the significant fields shown in the display.
Cisco 7500 Series Routers The sample output for the Cisco 7500 series routers may vary depending on the specific model (for example, the Cisco 7513 router). The following is sample output from the show environment all command on the Cisco 7500 series routers: Table 81 describes the significant fields shown in the display.
The following example is for the Cisco 7500 series routers. This example shows the measurements immediately before the last shutdown. Table 82 describes the significant fields shown in the display.
The following example is for the Cisco 7500 series router. This information lists the temperature and voltage thresholds for each sensor. These thresholds indicate when error messages occur. There are two level of messages: warning and critical. Table 83 describes the significant fields shown in the display.
Cisco AS5300 Series Access Servers In the following example, keywords and options are limited according to the physical characteristics of the system is shown: Cisco 12000 Series GSRs The following examples are for the Cisco 12000 series GSRs. The following is sample output from the show environment command for a Cisco 12012 router. Slots 0 through 11 are the line cards, slots 16 and 17 are the clock and scheduler cards, slots 18 through 20 are the switch fabric cards, slots 24 through 26 are the power supplies, and slots 28 and 29 are the blowers. An "NA" in the table means that no values were returned. In some cases it is because the equipment is not supported for that environmental parameter (for example, the power supply and blowers in slots 24, 26, 28, and 29 do not have a 3V power supply, so an NA is displayed). Table 84 describes the significant fields shown and lists the equipment supported by each environmental parameter. "NA" indicates that the reading could not be obtained, so the command should be run again.
The following is sample output from the show environment all command for the Cisco 12008 router. Slots 0 through 7 are the line cards, slots 16 and 17 are the clock scheduler cards (the clock scheduler cards control the fans), slots 18 through 20 are the switch fabric cards, and slots 24 and 26 are the power supplies. The Cisco 12008 router does not support slots 25, 27, 28, and 29. An "NA" in the table means that no values were returned. In some cases it is because the equipment is not supported for that environmental parameter (for example, the power supplies in slots 24 and 26 do not have a hot sensor, so an NA is displayed). The following is sample output from the show environment table command for a Cisco 12012 router. The show environment table command lists the warning, critical, and shutdown limits on your system and includes the GRP card and line cards (slots 0 to 15), clock and scheduler cards (slots 16 and 17), switch fabric cards (slots 18 to 20), and blowers. The following is sample output from the show environment leds command for a Cisco 12012 router. The show environment leds command lists the status of the MBus LEDs on the clock, scheduler, and the switch fabric cards. Cisco 7304 Router The following is sample output from the show environment all command on a Cisco 7304 router with modular services cards (MSCs) and shared port adapters (SPAs) installed: The following is sample output from the show environment last command on a Cisco 7304 router with MSCs and SPAs installed and an NSE-100: The following is sample output from the show environment table command on a Cisco 7304 router with MSCs and SPAs installed: Table 85 describes the significant fields shown in the display.
Related Commands
show environment alarmTo display the information about the environmental alarm, use the show environment alarm command in user EXEC or privileged EXEC mode. show environment alarm [{status | threshold} [frutype]] Syntax Description
DefaultsIf you do not enter a frutype, all the information about the environmental alarm status is displayed. Command ModesUser EXEC Privileged EXEC Command History
Usage GuidelinesValid values for the frutype are as follows: •clock number—1 and 2. •earl slot—See the Note for valid values. •module slot—See the Note for valid values. •rp slot—See the Note for valid values. •power-supply number—1 and 2. •supervisor slot—See the Note for valid values. •vtt number—1 to 3. Note The slot argument designates the module and port number. Valid values for slot depend on the chassis and module that are used. For example, if you have a 48-port 10/100BASE-T Ethernet module that is installed in a 13-slot chassis, valid values for the slot number are from 1 to 13 and valid values for the port number are from 1 to 48. ExamplesThis example shows how to display all the information about the status of the environmental alarm: Related Commands
show environment coolingTo display the information about the cooling parameter, use the show environment cooling command in user EXEC or privileged EXEC mode. show environment cooling Syntax DescriptionThis command has no arguments or keywords. DefaultsThis command has no default settings. Command Modes User EXEC Command History
Usage GuidelinesThis command is not supported in Cisco 7600 series routers that are configured with a Supervisor Engine 2. ExamplesThis example shows how to display the information about the cooling parameter: Related Commands
show environment statusTo display the information about the operational FRU status, use the show environment status command in user EXEC or privileged EXEC mode. show environment status [frutype] Syntax Description
DefaultsIf you do not enter a frutype, all FRU status information is displayed. Command Modes User EXEC Command History
Usage GuidelinesValid values for the frutype are as follows: •all—No arguments. •backplane—No arguments. •clock number—1 and 2. •earl slot—See the Note for valid values. •fan-tray—No arguments. •module slot—See the Note for valid values. •power-supply number—1 and 2. •rp slot—See the Note for valid values. •supervisor slot—See the Note for valid values. •vtt number—1 to 3. Note The slot argument designates the module and port number. Valid values for slot depend on the chassis and module that are used. For example, if you have a 48-port 10/100BASE-T Ethernet module that is installed in a 13-slot chassis, valid values for the slot number are from 1 to 13 and valid values for the port number are from 1 to 48. ExamplesThis example shows how to display the information about the environmental status: This example shows how to display the information about the high-capacity power supplies: Table 86 describes the fields that are shown in the example.
Related Commands
show environment temperatureTo display the current temperature readings, use the show environment temperature command in user EXEC or privileged EXEC mode. show environment temperature [frutype] Syntax Description
DefaultsIf you do not enter a frutype, the module and EARL temperature readings are displayed. Command Modes User EXEC Command History
Usage GuidelinesValid values for the frutype are as follows: •earl slot—See the Note below for valid values. •module slot—See the Note below for valid values. •rp slot—See the the Note below for valid values. •vtt number—1 to 3. •clock number—1 and 2. Note The slot argument designates the module and port number. Valid values for slot depend on the chassis and module that are used. For example, if you have a 48-port 10/100BASE-T Ethernet module that is installed in a 13-slot chassis, valid values for the slot number are from 1 to 13 and valid values for the port number are from 1 to 48. The show environment temperature module command output includes the updated information after an SCP response is received. In the output display, the following applies: •N/O means not operational—The sensor is broken, returning impossible values. •N/A means not available—The sensor value is presently not available; try again later. •VTT 1, 2, and 3 refer to the power monitors that are located on the chassis backplane under the rear cover. ExamplesThis example shows how to display the temperature information for a specific module: This example shows how to display the temperature readings for all modules: Table 87 describes the fields that are shown in the example.
Related Commands
show errdisable detectTo display the error-disable detection status, use the show errdisable detect command in user EXEC or privileged EXEC mode. show errdisable detect Syntax DescriptionThis command has no arguments or keywords. DefaultsThis command has no default settings. Command Modes User EXEC Command History
ExamplesThis example shows how to display the error-disable detection status: Related Commands
show errdisable recoveryTo display the information about the error-disable recovery timer, use the show errdisable recovery command in EXEC mode. show errdisable recovery Syntax DescriptionThis command has no arguments or keywords. DefaultsThis command has no default settings. Command ModesEXEC Command History
ExamplesThis example shows how to display the information about the error-disable recovery timer: Related Commands
show fastblkTo display fast block memory information, use the show fastblk command in privileged EXEC mode. show fastblk [detailed] Syntax Description
Command ModesPrivileged EXEC (#) Command History
Usage GuidelinesUse this command to display allocated fast block memory pool details. When no memory pools are allocated, the "no fastblk memory pools allocated" message is displayed. ExamplesThe following is sample output from the show fastblk command using the detailed keyword. The fields are self-explanatory. show file descriptorsTo display a list of open file descriptors, use the show file descriptors command in EXEC mode. show file descriptors Syntax DescriptionThis command has no arguments or keywords. Command ModesEXEC Command History
Usage GuidelinesFile descriptors are the internal representations of open files. You can use this command to learn if another user has a file open. ExamplesThe following is sample output from the show file descriptors command: Table 88 describes the fields shown in the display.
show file informationTo display information about a file, use the show file information command in EXEC mode. show file information file-url Syntax Description
Command ModesEXEC Command History
ExamplesThe following is sample output from the show file information command: Table 89 describes the possible file types.
show file systemsTo list available file systems, use the show file systems command in privileged EXEC mode. show file systems Syntax DescriptionThis command has no arguments or keywords. Command ModesPrivileged EXEC Command History
Usage GuidelinesUse this command to learn the alias names, the Prefixes column in the output of the file systems that your router supports. ExamplesThe following is sample output from the show file systems command: Table 90 describes the significant fields shown in the display.
show flh-logThe show flh-log command has been replaced by the more flh:logfile command. See the description of the more flh:logfile command for more information. show fm inspectTo display the list and status of the access control lists (ACLs) and ports on which context based access control (CBAC) is configured, use the show fm inspect command in user EXEC or privileged EXEC mode. show fm inspect [detail | interface type mod/port] Syntax Description
DefaultsThis command has no default settings. Command Modes User EXEC Command History
Usage GuidelinesIf you can configure a VLAN access control list (VACL) on the port before you configure CBAC, the status displayed is INACTIVE; otherwise, it is ACTIVE. If policy feature card (PFC) resources are exhausted, the command displays BRIDGE and is followed by the number of failed currently active NetFlow requests that have been sent to the MSFC2 for processing. The show fm inspect command output includes this information: •interface:—Interface on which the internet protocol (IP) inspect feature is enabled •(direction)—Direction in which the IP inspect feature is enabled (IN or OUT) •acl name:—Name that is used to identify packets being inspected •status:—(ACTIVE or INACTIVE) displays if HW-assist is provided for this interface+direction (ACTIVE=hardware assisted or INACTIVE) The optional detail keyword displays the ACEs that are part of the ACL that is used for IP inspect on the given interface direction. ExamplesThis example shows how to display the list and status of CBAC-configured ACLs and ports: Related Commands
show fm interfaceTo display the detailed information about the feature manager on a per-interface basis, use the show fm interface command in user EXEC or privileged EXEC mode. show fm interface {interface type mod/port | null interface-number | port-channel number | vlan vlan-id} Syntax Description
DefaultsThis command has no default settings. Command Modes User EXEC Command History
Usage GuidelinesThe pos, atm, and ge-wan keywords are supported on Cisco 7600 series routers that are configured with a Supervisor Engine 2. The interface-number argument designates the module and port number. Valid values for interface-number depend on the specified interface type and the chassis and module that are used. For example, if you specify a Gigabit Ethernet interface and have a 48-port 10/100BASE-T Ethernet module that is installed in a 13-slot chassis, valid values for the module number are from 1 to 13 and valid values for the port number are from 1 to 48. The port-channel number values from 257 to 282 are supported on the CSM and the FWSM only. ExamplesThis example shows how to display the detailed information about the feature manager on a specified interface: This example shows how to display the detailed information about the feature manager on a specific VLAN: Related Commands
show fm reflexiveTo display the information about the reflexive entry for the dynamic feature manager, use the show fm reflexive command in privileged EXEC mode. show fm reflexive Syntax DescriptionThis command has no arguments or keywords. DefaultsThis command has no default settings. Command ModesPrivileged EXEC Command History
ExamplesThis example shows how to display the information about the reflexive entry for the dynamic feature manager: show fm summaryTo display a summary of feature manager information, use the show fm summary command in user EXEC or privileged EXEC mode. show fm summary Syntax DescriptionThis command has no arguments or keywords. DefaultsThis command has no default settings. Command Modes User EXEC Command History
ExamplesThis example shows how to display a summary of feature manager information: Related Commands
show funiTo display the frame-based user-network interface information, use the show funi command in user EXEC or privileged EXEC mode. show funi {arp-server [atm atm-interface-number] | class-links {vpi/vci-value | vci-value | connection-name} | ilmi-configuration | ilmi-status [atm atm-interface-number] | map | pvc [vpi/vci-value | vci-value | connection-name | dbs | ppp] | route | traffic | vp [atm-vpi-number] | vc [atm-vcd-number | connection-name | detail [prefix {interface | vc_name | vcd | vpi/vci}] | interface atm atm-interface-number [connection-name | detail [prefix {interface | vc_name | vcd | vpi/vci}]] | range lower-vcd-limit upper-vcd-limit [connection-name | detail [prefix {interface | vc_name | vcd | vpi/vci}]] | interface atm atm-interface-number [connection-name | detail [prefix {interface | vc_name | vcd | vpi/vci}]] | summary [atm atm-interface-number]]} Syntax Description
Command Modes User EXEC (>) Command History
Usage GuidelinesUse this command to display the frame-based user-network interface information with the available keywords and arguments. ExamplesThe following is sample output from the show funi traffic command. The fields are self-explanatory: The following is sample out from the show funi vc detail prefix interface command. The fields are self-explanatory: The following is sample out from the show funi vc detail prefix vc_name command. The fields are self-explanatory: The following is sample out from the show funi vc detail prefix pvi/vci command. The fields are self-explanatory: show identity policyTo display identity policy information in a tabular form, use the show identity policy command in privileged EXEC mode. show identity policy [name] Syntax Description
Command ModesPrivileged EXEC (#) Command History
ExamplesThe following is output from the show identity policy command: The following is output for the policy named p2: Related Commands
show identity profileTo display identity profile information in a tabular form, use the show identity profile command in privileged EXEC mode. show identity profile [ default | dot1x | eapoudp] Syntax Description
Command ModesPrivileged EXEC (#) Command History
ExamplesThe following is output from the show identity profile command: Related Commands
|
What is the effect of using the router copy running-config startup config command on a router the contents?
Related Posts
Copyright © 2024 SignalDuo Inc.
