Table Of Contents
show
show <command> append
show <command> begin
show <command> exclude
show <command> include
show <command> redirect
show <command> section
show <command> tee
show (Flash file system)
show aliases
show alignment
show archive
show archive config differences
show archive config incremental-diffs
show archive log config
show async bootp
show autoupgrade configuration unknown
show bootflash:
show bootvar
show buffers
show buffers summary
show c2600
show c7200
show catalyst6000
show cls
show config id
show configuration lock
show context
show controllers (GRP image)
show controllers (line card image)
show controllers logging
show controllers tech-support
show debugging
show declassify
show derived-config
show diagnostic cns
show diagnostic sanity
show disk
show disk0:
show disk1:
show environment
show environment alarm
show environment cooling
show environment status
show environment temperature
show errdisable detect
show errdisable recovery
show file descriptors
show file information
show file systems
show flh-log
show fm inspect
show fm interface
show fm reflexive
show fm summary
show identity policy
show identity profile
show
To verify the Multiple Spanning Tree (MST) configuration, use the show command. in MST configuration submode.
show [current | pending]
Syntax Description
current
|
(Optional) Displays the current configuration that is used to run MST.
|
pending
|
(Optional) Displays the edited configuration that will replace the current configuration.
|
Defaults
This command has no default settings.
Command Modes
MST configuration submode
Command History
Release
|
Modification
|
12.2(14)SX
|
Support for this command was introduced on the Supervisor Engine 720.
|
12.2(17d)SXB
|
Support for this command on the Supervisor Engine 2 was extended to Release 12.2(17d)SXB.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
Usage Guidelines
The 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.
Examples
This example shows how to display the edited configuration:
Router(config-mst)# show pending
Pending MST configuration
-------- ---------------------------------------------------------------------
2 1010, 1020, 1030, 1040, 1050, 1060, 1070, 1080, 1090, 1100, 1110
3 1-1009, 1011-1019, 1021-1029, 1031-1039, 1041-1049, 1051-1059
1061-1069, 1071-1079, 1081-1089, 1091-1099, 1101-1109, 1111-1119
------------------------------------------------------------------------------
This example shows how to display the current configuration:
Router(config-mst)# show current
Current MST configuration
-------- ---------------------------------------------------------------------
-------------------------------------------------------------------------------
Related Commands
Command
|
Description
|
instance
|
Maps a VLAN or a set of VLANs to an MST instance.
|
name (MST configuration submode)
|
Sets the name of an MST region.
|
revision
|
Sets the revision number for the MST configuration.
|
show spanning-tree mst
|
Displays the information about the MST protocol.
|
spanning-tree mst configuration
|
Enters MST-configuration submode.
|
show <command> append
To 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
|
Any Cisco IOS show command.
|
| append url
|
The addition of this syntax redirects the command output to the file location specified in the Universal Resource Locator (URL). The pipe (|) is required.
The Cisco IOS File System (IFS) uses URLs to specify the location of a file system, directory, and file. Typical URL elements include:
prefix:[directory/]filename
Prefixes can be local file locations, such as flash: or disk0:. Alternatively, you can specify network locations using the following syntax:
ftp:[[//[username[:password]@]location]/directory]/filename
tftp:[[//location]/directory]/filename
The rcp: prefix is not supported.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.0(21)S
|
This command was introduced.
|
12.2(13)T
|
This command was integrated into Cisco IOS Release 12.2(13)T.
|
Usage Guidelines
To 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.
Examples
In 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.
Router# show tech-support | append disk1:showoutput.txt
Related Commands
Command
|
Description
|
show <command> redirect
|
Redirects the output of any show command to a specified file.
|
show <command> tee
|
Copies the show command output to a file while displaying it on the terminal.
|
show <command> begin
To 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
|
Any supported show command.
|
|
|
A vertical bar (the "pipe" symbol) indicates that an output processing specification follows.
|
regular-expression
|
Any regular expression found in show command output. The show output will begin from the first instance of this string (output prior to this string will not be printed to the screen). The string is case-sensitive. Use parenthesis to indicate a literal use of spaces.
|
/
|
Specifies a search at a --More-- prompt that begins unfiltered output with the first line that contains the regular expression.
|
-
|
Specifies a filter at a --More-- prompt that only displays output lines that do not contain the regular expression.
|
+
|
Specifies a filter at a --More-- prompt that only displays output lines that contain the regular expression.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
8.3
|
The show command was introduced.
|
12.0(1)T
|
This extension of the show command was introduced..
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
Usage Guidelines
The 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.
Examples
The 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."
Router# show interface | begin Ethernet
Ethernet0 is up, line protocol is up
Hardware is Lance, address is 0060.837c.6399 (bia 0060.837c.6399)
Description: ip address is 172.1.2.14 255.255.255.0
Internet address is 172.1.2.14/24
0 lost carrier, 0 no carrier
0 output buffer failures, 0 output buffers swapped out
Serial1 is up, line protocol is up
Serial2 is up, line protocol is up
Serial3 is up, line protocol is down
Serial4 is down, line protocol is down
Serial5 is up, line protocol is up
Serial6 is up, line protocol is up
Serial7 is up, line protocol is up
Related Commands
Command
|
Description
|
more <url> begin
|
Begins unfiltered output of the more command with the first line that contains the regular expression you specify.
|
more <url> exclude
|
Filters more command output so that it excludes lines that contain a particular regular expression.
|
more <url> include
|
Filters more command output so that it displays only lines that contain a particular regular expression.
|
show <command> exclude
|
Filters show command output so that it excludes lines that contain a particular regular expression.
|
show <command> include
|
Filters show command output so that it displays only lines that contain a particular regular expression.
|
show <command> exclude
To 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
|
Any supported show command.
|
|
|
A vertical bar (the "pipe" symbol) indicates that an output processing specification follows.
|
regular-expression
|
Any regular expression found in show command output.
|
/
|
Specifies a search at a --More-- prompt that begins unfiltered output with the first line that contains the regular expression.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
12.0(1)T
|
This command was introduced.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
Usage Guidelines
The regular-expression argument is case sensitive and allows for complex matching requirements.
You can specify a new search at every --More-- prompt. To search the remaining output of the 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.
Examples
The 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."
Router# show buffers | exclude 0 misses
398 in free list (500 max allowed)
Small buffers, 104 bytes (total 50, permanent 50):
50 in free list (20 min, 150 max allowed)
551 hits, 3 misses, 0 trims, 0 created
Big buffers, 1524 bytes (total 50, permanent 50):
49 in free list (5 min, 150 max allowed)
Very Big buffers, 4520 bytes (total 10, permanent 10):
Huge buffers, 18024 bytes (total 0 permanent 0):
0 in free list (0 min, 4 max allowed)
Serial0 buffers, 1543 bytes (total 64, permanent 64):
16 in free list (0 min, 64 max allowed)
Related Commands
Command
|
Description
|
more <url> begin
|
Begins unfiltered output of the more command with the first line that contains the regular expression you specify.
|
more <url> exclude
|
Filters more command output so that it excludes lines that contain a particular regular expression.
|
more <url> include
|
Filters more command output so that it displays only lines that contain a particular regular expression.
|
show <command> begin
|
Searches the output of any show command and displays the output from the first instance of a specified string.
|
show <command> include
|
Filters show command output so that it displays only lines that contain a particular regular expression.
|
show <command> include
To 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
|
Any supported show command.
|
|
|
A vertical bar (the "pipe" symbol) indicates that an output processing specification follows.
|
regular-expression
|
Any regular expression found in show command output. Use parenthesis to include spaces in the expression.
|
/
|
Specifies a search at a --More-- prompt that begins unfiltered output with the first line that contains the regular expression.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
12.0(1)T
|
This command was introduced.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
Usage Guidelines
The regular-expression argument is case sensitive and allows for complex matching requirements.
You can specify a new search at every --More-- prompt. To search the remaining output of the 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.
Examples
The 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".
Router# show interface | include ( is )
ATM0 is administratively down, line protocol is down
Hardware is ATMizer BX-50
Dialer1 is up (spoofing), line protocol is up (spoofing)
DTR is pulsed for 1 seconds on reset
Ethernet0 is up, line protocol is up
Hardware is Lance, address is 0060.837c.6399 (bia 0060.837c.6399)
Internet address is 172.21.53.199/24
Ethernet1 is up, line protocol is up
Hardware is Lance, address is 0060.837c.639c (bia 0060.837c.639c)
Internet address is 5.5.5.99/24
Serial0:0 is down, line protocol is down
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."
Serial0:13 is down, line protocol is down
Internet address is 11.0.0.2/8
0 output errors, 0 collisions, 2 interface resets
Timeslot(s) Used:14, Transmitter delay is 0 flags
Related Commands
Command
|
Description
|
more <url> begin
|
Begins unfiltered output of the more command with the first line that contains the regular expression you specify.
|
more <url> exclude
|
Filters more command output so that it excludes lines that contain a particular regular expression.
|
more <url> include
|
Filters more command output so that it displays only lines that contain a particular regular expression.
|
show <command> begin
|
Searches the output of any show command and displays the output from the first instance of a specified string.
|
show <command> exclude
|
Filters show command output so that it excludes lines that contain a particular regular expression.
|
show <command> redirect
To 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
|
Any Cisco IOS show command.
|
| redirect url
|
The addition of this syntax redirects the command output to the file location specified in the Universal Resource Locator (URL). The pipe (|) is required.
The Cisco IOS File System (IFS) uses URLs to specify the location of a file system, directory, and file. Typical URL elements include:
prefix:[directory/]filename
Prefixes can be local file locations, such as flash: or disk0:. Alternatively, you can specify network locations using the following syntax:
ftp:[[//[username[:password]@]location]/directory]/filename
tftp:[[//location]/directory]/filename
The rcp: prefix is not supported.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.0(21)S
|
This command was introduced.
|
12.2(13)T
|
This command was integrated into Cisco IOS Release 12.2(13)T.
|
Usage Guidelines
To 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.
Examples
In 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:
Router# show tech | redirect
ftp://USER:MYPASSWORD@172.16.101.101//tftpboot/docs/showtech.txt
Related Commands
Command
|
Description
|
show <command> append
|
Redirects and appends show command output to the end of an existing file.
|
show <command> tee
|
Copies the show command output to a file while displaying it on the terminal.
|
show <command> section
To 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
|
Any Cisco IOS show command.
|
include
|
(Optional) Includes only the lines that contain a particular regular expression. This is the default keyword when none is specified.
|
exclude
|
(Optional) Excludes any lines that contain a particular regular expression.
|
regular-expression
|
Any regular expression or plain text string found in show command output. The syntax of the regular expression conforms to that of Bell V8 regexp(3).
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.3(2)T
|
This command was introduced.
|
12.2(33)SRE
|
This command was integrated into Cisco IOS release 12.(33)SRE.
|
Usage Guidelines
In 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.
Examples
The 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.
Router# show running-config | include interface
interface Ethernet0/0
interface Ethernet1/0
interface Serial2/0
interface Serial3/0
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.
Router# show running-config | section include interface
interface Ethernet0/0
shutdown
no cdp enable
interface Ethernet1/0
shutdown
no cdp enable
interface Serial2/0
shutdown
no cdp enable
interface Serial3/0
shutdown
no cdp enable
Related Commands
Command
|
Description
|
show <command> append
|
Redirects the output of any show command and adds it to the end of an existing file.
|
show <command> exclude
|
Filters show command output so that it excludes lines that contain a particular regular expression.
|
show <command> include
|
Filters show command output so that it displays only lines that contain a particular regular expression.
|
show <command> redirect
|
Redirects the output of any show command to a specified file.
|
show <command> tee
To 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
|
Any Cisco IOS show command.
|
| tee url
|
The addition of this syntax copies the command output to the file location specified in the Universal Resource Locator (URL). The pipe (|) is required.
The Cisco IOS File System (IFS) uses URLs to specify the location of a file system, directory, and file. Typical URL elements include:
prefix:[directory/]filename
Prefixes can be local file locations, such as flash: or disk0:. Alternatively, you can specify network locations using the following syntax:
ftp:[[//[username[:password]@]location]/directory]/filename
tftp:[[//location]/directory]/filename
The rcp: prefix is not supported.
|
/append
|
(Optional) Adds the show command output to the end of an existing file.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.0(21)S
|
This command was introduced.
|
12.2(13)T
|
This command was integrated into Cisco IOS Release 12.2(13)T.
|
Usage Guidelines
To 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).
Examples
In 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:
Router# show tech-support | tee tftp://172.16.101.101/docs/showoutput.txt
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":
Router# show tech-support | tee /append tftp://172.16.101.101/docs/showoutput.txt
Related Commands
Command
|
Description
|
show <command> append
|
Redirects the output of any show command and adds it to the end of existing file.
|
show <command> redirect
|
Redirects the output of any show command to a specified file.
|
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
flash-filesystem:
|
Flash memory file system, followed by a colon. The availablity of Flash file system keywords will vary by platform. Valid flash file system keywords inlude:
• bootflash
• flash
• slot0
• slot1
• slavebootflash
• slaveslot0
• slaveslot1
|
all
|
(Optional) On Class B Flash file systems, all keyword displays complete information about Flash memory, including information about the individual ROM devices in Flash memory and the names and sizes of all system image files stored in Flash memory, including those that are invalid.
On Class A Flash file systems, the all keyword displays the following information:
• The information displayed when no keywords are used.
• The information displayed by the filesys keyword.
• The information displayed by the chips keyword.
|
chips
|
(Optional) Displays information per partition and per chip, including which bank the chip is in, plus its code, size, and name.
|
filesys
|
(Optional) Displays the Device Info Block, the Status Info, and the Usage Info.
|
partition-number
|
(Optional) Displays output for the specified partition number. If you do not specify a partition in the command, the router displays output for all partitions. You can use this keyword only when Flash memory has multiple partitions.
|
detailed
|
(Optional) Displays detailed file directory information per partition, including file length, address, name, Flash memory checksum, computer checksum, bytes used, bytes available, total bytes, and bytes of system Flash memory.
|
err
|
(Optional) Displays write or erase failures in the form of number of retries.
|
summary
|
(Optional) Displays summary information per partition, including the partition size, bank size, state, and method by which files can be copied into a particular partition. You can use this keyword only when Flash memory has multiple partitions.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
11.3 AA
|
This command was introduced.
|
12.3
|
A timestamp that shows the offset from Coordinated Universal Time (UTC) was added to the show command display.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
Usage Guidelines
If 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.
Examples
The 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 48 describes the significant fields shown in the display.
The following is sample output from the show flash: command.
-#- ED --type-- --crc--- -seek-- nlen -length- -----date/time------ name
1 .. unknown 317FBA1B 4A0694 24 4720148 Dec 15 2003 17:49:36 -08:00
hampton/nitro/c7200-j-mz
2 .. unknown 9237F3FF 92C574 11 4767328 Jan 02 2004 18:42:53 -08:00 c7200-js-mz
3 .D unknown 71AB01F1 10C94E0 10 7982828 Jan 02 2004 18:48:14 -08:00 rsp-jsv-mz
4 .D unknown 96DACD45 10C97E0 8 639 Jan 03 2004 12:09:17 -08:00 the_time
5 .. unknown 96DACD45 10C9AE0 3 639 Jan 03 2004 12:09:32 -08:00 the_time
6 .D unknown 96DACD45 10C9DE0 8 639 Jan 03 2004 12:37:01 -08:00 the_time
7 .. unknown 96DACD45 10CA0E0 8 639 Jan 03 2004 12:37:13 -08:00 the_time
3104544 bytes available (17473760 bytes used)
Table 48 show (Class A Flash File System) Field Descriptions
Field
|
Description
|
#
|
Index number for the file.
|
ED
|
Whether the file contains an error (E) or is deleted (D).
|
type
|
File type (1 = configuration file, 2 = image file). The software displays these values only when the file type is certain. When the file type is unknown, the system displays "unknown" in this field.
|
crc
|
Cyclic redundant check for the file.
|
seek
|
Offset into the file system of the next file.
|
nlen
|
Name length—Length of the filename.
|
length
|
Length of the file itself.
|
date/time
|
Date and time the file was created. In the example, -08:00 indicates that the given date and time is 8 hours behind Coordinated Universal Time (UTC).
|
name
|
Name of the file.
|
The following is sample output from the show flash: chips command:
RouterA# show flash: chips
******** Intel Series 2+ Status/Register Dump ********
ATTRIBUTE MEMORY REGISTERS:
Config Option Reg (4000): 2
Config Status Reg (4002): 0
Card Status Reg (4100): 1
Write Protect Reg (4104): 4
Voltage Cntrl Reg (410C): 0
Rdy/Busy Mode Reg (4140): 2
COMMON MEMORY REGISTERS: Bank 0
Intelligent ID Code : 8989A0A0
Compatible Status Reg: 8080
0 : B0B0 B0B0 B0B0 B0B0 B0B0 B0B0 B0B0 B0B0
8 : B0B0 B0B0 B0B0 B0B0 B0B0 B0B0 B0B0 B0B0
16 : B0B0 B0B0 B0B0 B0B0 B0B0 B0B0 B0B0 B0B0
24 : B0B0 B0B0 B0B0 B0B0 B0B0 B0B0 B0B0 B0B0
COMMON MEMORY REGISTERS: Bank 1
Intelligent ID Code : 8989A0A0
Compatible Status Reg: 8080
0 : B0B0 B0B0 B0B0 B0B0 B0B0 B0B0 B0B0 B0B0
8 : B0B0 B0B0 B0B0 B0B0 B0B0 B0B0 B0B0 B0B0
16 : B0B0 B0B0 B0B0 B0B0 B0B0 B0B0 B0B0 B0B0
24 : B0B0 B0B0 B0B0 B0B0 B0B0 B0B0 B0B0 B0B0
COMMON MEMORY REGISTERS: Bank 2
Intelligent ID Code : 8989A0A0
Compatible Status Reg: 8080
0 : B0B0 B0B0 B0B0 B0B0 B0B0 B0B0 B0B0 B0B0
8 : B0B0 B0B0 B0B0 B0B0 B0B0 B0B0 B0B0 B0B0
16 : B0B0 B0B0 B0B0 B0B0 B0B0 B0B0 B0B0 B0B0
24 : B0B0 B0B0 B0B0 B0B0 B0B0 B0B0 B0B0 B0B0
COMMON MEMORY REGISTERS: Bank 3
Intelligent ID Code : 8989A0A0
Compatible Status Reg: 8080
0 : B0B0 B0B0 B0B0 B0B0 B0B0 B0B0 B0B0 B0B0
8 : B0B0 B0B0 B0B0 B0B0 B0B0 B0B0 B0B0 B0B0
16 : B0B0 B0B0 B0B0 B0B0 B0B0 B0B0 B0B0 B0B0
24 : B0B0 B0B0 B0B0 B0B0 B0B0 B0B0 B0B0 B0B0
COMMON MEMORY REGISTERS: Bank 4
Intelligent ID Code : 8989A0A0
Compatible Status Reg: 8080
0 : B0B0 B0B0 B0B0 B0B0 B0B0 B0B0 B0B0 B0B0
8 : B0B0 B0B0 B0B0 B0B0 B0B0 B0B0 B0B0 B0B0
16 : B0B0 B0B0 B0B0 B0B0 B0B0 B0B0 B0B0 B0B0
24 : B0B0 B0B0 B0B0 B0B0 B0B0 B0B0 B0B0 B0B0
The following is sample output from the show flash: filesys command:
RouterA# show flash: filesys
-------- F I L E S Y S T E M S T A T U S --------
Magic Number = 6887635 File System Vers = 10000 (1.0)
Length = 1400000 Sector Size = 20000
Programming Algorithm = 4 Erased State = FFFFFFFF
File System Offset = 20000 Length = 13A0000
MONLIB Offset = 100 Length = C730
Bad Sector Map Offset = 1FFEC Length = 14
Squeeze Log Offset = 13C0000 Length = 20000
Squeeze Buffer Offset = 13E0000 Length = 20000
Bytes Used = 10AA0E0 Bytes Available = 2F5F20
Bad Sectors = 0 Spared Sectors = 0
OK Files = 4 Bytes = 90C974
Deleted Files = 3 Bytes = 79D3EC
Files w/Errors = 0 Bytes = 0
The following is sample output from the show flash: command:
1 4137888 c3640-c2is-mz.Feb24
[4137952 bytes used, 12639264 available, 16777216 total]
16384K bytes of processor board System flash (Read/Write)\
The following example shows detailed information about the second partition in internal Flash memory:
System flash directory, partition 2:
1 1711088 dirt/images/c3600-i-mz
[1711152 bytes used, 15066064 available, 16777216 total]
16384K bytes of processor board System flash (Read/Write)
Class B Flash File Systems
Table 49 describes the significant fields shown in the displays.
Table 49 show (Class B Flash File System) all Fields
Field
|
Description
|
addr
|
Address of the file in Flash memory.
|
available
|
Total number of bytes available in Flash memory.
|
Bank
|
Bank number.
|
Bank-Size
|
Size of bank in bytes.
|
bytes used
|
Total number of bytes used in Flash memory.
|
ccksum
|
Computed checksum.
|
Chip
|
Chip number.
|
Code
|
Code number.
|
Copy-Mode
|
Method by which the partition can be copied to:
• RXBOOT-MANUAL indicates a user can copy manually by reloading to the boot ROM image.
• RXBOOT-FLH indicates user can copy via Flash load helper.
• Direct indicates user can copy directly into Flash memory.
• None indicates that it is not possible to copy into that partition.
|
fcksum
|
Checksum recorded in Flash memory.
|
File
|
Number of the system image file. If no filename is specified in the boot system flash command, the router boots the system image file with the lowest file number.
|
Free
|
Number of bytes free in partition.
|
Length
|
Size of the system image file (in bytes).
|
Name
|
Name of chip manufacturer and chip type.
|
Name/status
|
Filename and status of a system image file. The status [invalidated] appears when a file has been rewritten (recopied) into Flash memory. The first (now invalidated) copy of the file is still present within Flash memory, but it is rendered unusable in favor of the newest version. The [invalidated] status can also indicate an incomplete file that results from the user abnormally terminating the copy process, a network timeout, or a Flash memory overflow.
|
Partition
|
Partition number in Flash memory.
|
Size
|
Size of partition (in bytes) or size of chip.
|
State
|
State of the partition. It can be one of the following values:
• Read-Only indicates the partition that is being executed from.
• Read/Write is a partition that can be copied to.
|
System flash directory
|
Flash directory and its contents.
|
total
|
Total size of Flash memory (in bytes).
|
Used
|
Number of bytes used in partition.
|
The following is sample output from the show flash: all command:
Partition Size Used Free Bank-Size State Copy Mode
1 16384K 4040K 12343K 4096K Read/Write Direct
1 4137888 c3640-c2is-mz.Feb24
[4137952 bytes used, 12639264 available, 16777216 total]
16384K bytes of processor board System flash (Read/Write)
1 1 01D5 1024KB AMD 29F080
2 1 01D5 1024KB AMD 29F080
3 1 01D5 1024KB AMD 29F080
4 1 01D5 1024KB AMD 29F080
1 2 01D5 1024KB AMD 29F080
2 2 01D5 1024KB AMD 29F080
3 2 01D5 1024KB AMD 29F080
4 2 01D5 1024KB AMD 29F080
1 3 01D5 1024KB AMD 29F080
2 3 01D5 1024KB AMD 29F080
3 3 01D5 1024KB AMD 29F080
4 3 01D5 1024KB AMD 29F080
1 4 01D5 1024KB AMD 29F080
2 4 01D5 1024KB AMD 29F080
3 4 01D5 1024KB AMD 29F080
4 4 01D5 1024KB AMD 29F080
The following is sample output from the show flash: all command on a router with Flash memory partitioned:
System flash partition information:
Partition Size Used Free Bank-Size State Copy-Mode
1 4096K 3459K 637K 4096K Read Only RXBOOT-FLH
2 4096K 3224K 872K 4096K Read/Write Direct
System flash directory, partition 1:
1 3459720 master/igs-bfpx.100-4.3
[3459784 bytes used, 734520 available, 4194304 total]
4096K bytes of processor board System flash (Read ONLY)
1 1 89A2 1024KB INTEL 28F008SA
2 1 89A2 1024KB INTEL 28F008SA
3 1 89A2 1024KB INTEL 28F008SA
4 1 89A2 1024KB INTEL 28F008SA
Executing current image from System flash [partition 1]
System flash directory, partition2:
[3224072 bytes used, 970232 available, 4194304 total]
4096K bytes of processor board System flash (Read/Write)
1 2 89A2 1024KB INTEL 28F008SA
2 2 89A2 1024KB INTEL 28F008SA
3 2 89A2 1024KB INTEL 28F008SA
4 2 89A2 1024KB INTEL 28F008SA
The following is sample output from the show flash: chips command:
RouterB> show flash: chips
16384K bytes of processor board System flash (Read/Write)
1 1 01D5 1024KB AMD 29F080
2 1 01D5 1024KB AMD 29F080
3 1 01D5 1024KB AMD 29F080
4 1 01D5 1024KB AMD 29F080
1 2 01D5 1024KB AMD 29F080
2 2 01D5 1024KB AMD 29F080
3 2 01D5 1024KB AMD 29F080
4 2 01D5 1024KB AMD 29F080
1 3 01D5 1024KB AMD 29F080
2 3 01D5 1024KB AMD 29F080
3 3 01D5 1024KB AMD 29F080
4 3 01D5 1024KB AMD 29F080
1 4 01D5 1024KB AMD 29F080
2 4 01D5 1024KB AMD 29F080
3 4 01D5 1024KB AMD 29F080
4 4 01D5 1024KB AMD 29F080
The following is sample output from the show flash: detailed command:
RouterB> show flash: detailed
1 4137888 c3640-c2is-mz.Feb24
[4137952 bytes used, 12639264 available, 16777216 total]
16384K bytes of processor board System flash (Read/Write)
The following is sample output from the show flash: err command:
1 4137888 c3640-c2is-mz.Feb24
[4137952 bytes used, 12639264 available, 16777216 total]
16384K bytes of processor board System flash (Read/Write)
Chip Bank Code Size Name erase write
1 1 01D5 1024KB AMD 29F080 0 0
2 1 01D5 1024KB AMD 29F080 0 0
3 1 01D5 1024KB AMD 29F080 0 0
4 1 01D5 1024KB AMD 29F080 0 0
1 2 01D5 1024KB AMD 29F080 0 0
2 2 01D5 1024KB AMD 29F080 0 0
3 2 01D5 1024KB AMD 29F080 0 0
4 2 01D5 1024KB AMD 29F080 0 0
1 3 01D5 1024KB AMD 29F080 0 0
2 3 01D5 1024KB AMD 29F080 0 0
3 3 01D5 1024KB AMD 29F080 0 0
4 3 01D5 1024KB AMD 29F080 0 0
1 4 01D5 1024KB AMD 29F080 0 0
2 4 01D5 1024KB AMD 29F080 0 0
3 4 01D5 1024KB AMD 29F080 0 0
4 4 01D5 1024KB AMD 29F080 0 0
See Table 49 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.
Router# show flash summary
System flash partition information:
Partition Size Used Free Bank-Size State Copy-Mode
1 4096K 2048K 2048K 2048K Read Only RXBOOT-FLH
2 4096K 2048K 2048K 2048K Read/Write Direct
Related Commands
Command
|
Description
|
more
|
Displays the contents of any file in the Cisco IOS File System.
|
show aliases
To 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
mode
|
(Optional) Name of a specific command or configuration mode. Specifies that only aliases configured for this mode should be displayed.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
10.3
|
This command was introduced.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
Usage Guidelines
When 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.
Router> show aliases exec
Related Commands
Command
|
Description
|
alias
|
Creates a command alias.
|
show alignment
To display alignment errors and spurious memory access errors, use the show alignment command in privileged EXEC mode.
show alignment
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.3(7)T
|
This command was introduced.
|
12.2(22)S
|
This command was integrated into Cisco IOS Release 12.2(22)S.
|
12.2(18)SXE
|
This command was integrated into Cisco IOS Release 12.2(18)SXE.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
Usage Guidelines
Alignment 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.
Examples
The 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
Unaligned handler is disabled
Router#
The following is sample output from the show alignment command when there are no alignment or spurious memory errors:
No alignment data has been recorded.
No spurious memory references have been recorded.
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.
Total Corrections 134, Recorded 1, Reads 134, Writes 0
Address Count Access Type Traceback
1A014C5 134 32bit read 0x6012F538 0x601338F8 0x601344D8 0x6022D528
No spurious memory references have been recorded.
Table 50 describes the significant fields shown in the display.
Table 50 show alignment Field Descriptions
Field
|
Description
|
Total Corrections
|
Total number of alignment corrections made.
|
Recorded
|
Number of alignment entries.
|
Reads
|
Number of misaligned reads.
|
Writes
|
Number of misaligned writes.
|
Initial Address
|
Address of where the alignment error occurred.
|
Count
|
Number of times the alignment occurred at this address.
|
Initial Access
|
Address of where the alignment error occurred.
|
Type
|
Type of alignment error: read or write.
|
Traceback
|
The traceback address information necessary to determine the cause of the misalignment.
|
The following is sample output from the show alignment command when there are only spurious memory access errors:
No alignment data has been recorded.
Total Spurious Accesses 50, Recorded 3
E 10 0x605351A0 0x603CA084 0x606C4060 0x606D6368 0x60743284 0x60743270
E 20 0x605351A0 0x6036EE7C 0x606C4060 0x606D6368 0x60743284 0x60743270
E 20 0x605351A0 0x603C998C 0x606D53EC 0x606C4060 0x606D6368 0x60743284
Table 51 describes the significant fields shown in the display.
Table 51 show alignment Field Descriptions for Spurious Memory Access Errors
Field
|
Description
|
Total Spurious Accesses
|
Total number of spurious memory accesses made.
|
Recorded
|
Number of recorded spurious memory access entries.
|
Address
|
Address at which the spurious memory access error occurred.
|
Count
|
Number of times the spurious memory access occurred at each address. The sum equals the Total Spurious Accesses.
|
Traceback
|
The traceback address information necessary to determine the cause of the misalignment.
|
The following is sample output from the show alignment command when there are alignment errors and spurious memory access errors:
Total Corrections 134, Recorded 1, Reads 134, Writes 0
Address Count Access Type Traceback
1A014C5 134 32bit read 0x6012F538 0x601338F8 0x601344D8 0x6022D528
Total Spurious Accesses 50, Recorded 3
E 10 0x605351A0 0x603CA084 0x606C4060 0x606D6368 0x60743284 0x60743270
E 20 0x605351A0 0x6036EE7C 0x606C4060 0x606D6368 0x60743284 0x60743270
E 20 0x605351A0 0x603C998C 0x606D53EC 0x606C4060 0x606D6368 0x60743284 x60743270
Related Commands
Command
|
Description
|
enable
|
To enter privileged EXEC mode, or any other security level set by a system administrator, use the enable command in user EXEC or privileged EXEC mode.
|
show archive
To display information about the files saved in the Cisco IOS configuration archive, use the show archive command in privileged EXEC mode.
show archive
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.3(7)T
|
This command was introduced.
|
12.2(25)S
|
This command was integrated into Cisco IOS Release 12.2(25)S.
|
12.2(28)SB
|
This command was integrated into Cisco IOS Release 12.2(28)SB.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
12.2(31)SB2
|
This command was implemented on the Cisco 10000 series.
|
12.2(33)SB
|
This command was integrated into Cisco IOS Release 12.2(33)SB and implemented on the Cisco 10000 series.
|
Examples
The following is sample output from the show archive command:
There are currently 1 archive configurations saved.
The next archive file will be named disk0:myconfig-2
1 disk0:myconfig-1 <- Most Recent
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.
There are currently 3 archive configurations saved.
The next archive file will be named disk0:myconfig-8
7 disk0:myconfig-7 <- Most Recent
Table 52 describes the significant fields shown in the displays.
Table 52 show archive Field Descriptions
Field
|
Description
|
Archive #
|
Indicates the number of the running configuration file saved to the Cisco IOS configuration archive. You can set the maximum number of archive files of the running configuration to be saved in the configuration archive. The most recent archive file is the last one shown in the display.
|
Name
|
Indicates the name of the running configuration file saved to the Cisco IOS configuration archive.
|
Related Commands
Command
|
Description
|
archive config
|
Saves a copy of the current running configuration to the Cisco IOS configuration archive.
|
configure confirm
|
Confirms replacement of the current running configuration with a saved Cisco IOS configuration file.
|
configure replace
|
Replaces the current running configuration with a saved Cisco IOS configuration file.
|
maximum
|
Sets the maximum number of archive files of the running configuration to be saved in the Cisco IOS configuration archive.
|
path
|
Specifies the location and filename prefix for the files in the Cisco IOS configuration archive.
|
time-period
|
Sets the time increment for automatically saving an archive file of the current running configuration in the Cisco IOS configuration archive.
|
show archive config differences
To 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
filename1(path)
|
(Optional) The filename (path) of the first configuration file. Can be files in the following locations: bootflash:, cns:, fpd:, ftp:, harddisk:, http:, https:, null:, nvram:, obfl:, pram:, rcp:, revrcsf:, scp:, stby-bootflash:, stby-harddisk:, stby-nvram:, stby-obfl:, stby-rcsf:, stby-usb0:, stby-usb1:, system:, tar:, tftp:, tmpsys:, usb0:
|
filename2(path)
|
(Optional) The filename of the second configuration file. Can be files in the following locations: bootflash:, cns:, fpd:, ftp:, harddisk:, http:, https:, null:, nvram:, obfl:, pram:, rcp:, revrcsf:, scp:, stby-bootflash:, stby-harddisk:, stby-nvram:, stby-obfl:, stby-rcsf:, stby-usb0:, stby-usb1:, system:, tar:, tftp:, tmpsys:, usb0:
|
ignorecase
|
(Optional) Indicates that the case of the filenames should be ignored.
|
Command Default
If 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
Privileged EXEC
Command History
Release
|
Modification
|
12.3(4)T
|
This command was introduced.
|
12.2(25)S
|
This command was integrated into Cisco IOS Release 12.2(25)S.
|
12.2(27)SBC
|
This command was integrated into Cisco IOS Release 12.2(27)SBC.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
12.2(33)SB
|
This command was integrated into Cisco IOS Release 12.2(33)SB and implemented on the Cisco 10000 series.
|
Usage Guidelines
Interpreting 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).
Examples
In this example, a diff operation is performed on the running and startup configuration files. Table 53 shows the configuration files used for this example.
Table 53 Configuration Files Used for the Diff Operation Example
Running Configuration File
|
Startup Configuration File
|
no ip subnet-zero
ip cef
interface Ethernet1/0
ip address 10.7.7.7 255.0.0.0
no ip route-cache
no ip mroute-cache
duplex half
no ip classless
snmp-server community public RO
|
ip subnet-zero
ip cef
ip name-server 10.4.4.4
voice dnis-map 1
dnis 111
interface Ethernet1/0
no ip address
no ip route-cache
no ip mroute-cache
shutdown
duplex half
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
|
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 53.
Router# show archive config differences running-config startup-config
+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
Command
|
Description
|
more nvram:startup-config
|
Displays the startup configuration file contained in NVRAM or specified by the CONFIG_FILE environment variable.
|
more system:running-config
|
Displays the contents of the currently running configuration file.
|
show archive config incremental-diffs
|
Performs a line-by-line comparison of a specified configuration file to the running configuration file and generates a list of the configuration lines that do not appear in the running configuration file.
|
show archive config incremental-diffs
To 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
file
|
The filename of the configuration file to be compared to the running configuration file.
|
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
12.3(4)T
|
This command was introduced.
|
12.2(25)S
|
This command was integrated into Cisco IOS Release 12.2(25)S.
|
12.2(27)SBC
|
This command was integrated into Cisco IOS Release 12.2(27)SBC.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
12.2(33)SB
|
This command was integrated into Cisco IOS Release 12.2(33)SB and implemented on the Cisco 10000 series.
|
Usage Guidelines
When 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.
Examples
In this example, an incremental diff operation is performed on the startup and running configuration files. Table 54 shows the configuration files used for this example.
Table 54 Configuration Files Used for the Incremental Diff Operation Example
Startup Configuration File
|
Running Configuration File
|
ip subnet-zero
ip cef
ip name-server 10.4.4.4
voice dnis-map 1
dnis 111
interface Ethernet1/0
no ip address
no ip route-cache
no ip mroute-cache
shutdown
duplex half
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
ip cef
interface Ethernet1/0
ip address 10.7.7.7 255.0.0.0
no ip route-cache
no ip mroute-cache
duplex half
no ip classless
snmp-server community public RO
|
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 54.
Router# show archive config incremental-diffs nvram:startup-config
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
Command
|
Description
|
more nvram:startup-config
|
Displays the startup configuration file contained in NVRAM or specified by the CONFIG_FILE environment variable.
|
more system:running-config
|
Displays the contents of the currently running configuration file.
|
show archive config differences
|
Performs a line-by-line comparison of any two configuration files (accessible through the IFS) and generates a list of the differences between them.
|
show archive log config
To 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
all
|
Displays all configuration log entries.
|
record-number [end-number]
|
Displays the log entry by record number. If you specify a record number for the optional end-number argument, all log entries with record numbers between the values entered for the record-number and end-number arguments are displayed. Valid values for the record-number and end-number arguments range from 1 to 2147483647.
|
user username
|
Displays log entries attributed to a particular user.
|
session session-number
|
(Optional) Displays log entries attributed to a particular session. Valid values for the session-number argument range from 1 to 1000.
|
statistics
|
Displays memory usage information for the configuration log.
|
provisioning
|
(Optional) Displays configuration log file information as it would appear in a configuration file, rather than in tabular format.
|
contenttype
|
(Optional) Specifies the format for the display of configuration change results.
|
plaintext
|
Specifies that the configuration change results will be formatted as plain text. This keyword appears only if the contenttype keyword has been entered.
|
xml
|
Specifies that the configuration change results will be in eXtensible Markup Language (XML) format. This keyword appears only if the contenttype keyword has been entered.
|
persistent
|
(Optional) Displays the persistent configuration changes in a configlet format.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.3(4)T
|
This command was introduced.
|
12.2(25)S
|
This command was integrated into Cisco IOS Release 12.2(25)S.
|
12.2(27)SBC
|
This command was integrated into Cisco IOS Release 12.2(27)SBC.
|
12.2(33)SRA
|
The contenttype, plaintext, xml, and persistent keywords were added.
|
12.4(11)T
|
This command was integrated into Cisco IOS Release 12.4(11)T.
|
12.2(33)SXH
|
This command was integrated into Cisco IOS Release 12.2(33)SXH.
|
12.2(33)SB
|
This command with syntax updated in 12.2(33)SRA was integrated into Cisco IOS Release 12.2(33)SB. This command was implemented on the Cisco 10000 series.
|
Usage Guidelines
If 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.
Examples
The 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
idx sess user@line Logged command
1 1 user1@console logging enable
2 1 user1@console logging size 200
Table 55 describes the significant fields shown in the display.
Table 55 show archive log config Field Descriptions
Field
|
Description
|
idx
|
The record number of the configuration log entry.
|
sess
|
The session number associated with the configuration log entry.
|
user@line
|
The username of the user who executed the command that generated the configuration log entry.
|
Logged command
|
The command that was executed.
|
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.
Router# show archive log config all provisioning
The following example results in the display of memory usage statistics for the configuration log:
Router# show archive log config statistics
Number of sessions being tracked: 1
Memory being held: 3910 bytes
Total memory allocated for session tracking: 3910 bytes
Total memory freed from session tracking: 0 bytes
Config Log log-queue Info:
Number of entries in the log-queue: 3
Memory being held in the log-queue: 671 bytes
Total memory allocated for log entries: 671 bytes
Total memory freed from log entries:: 0 bytes
The output is self-explanatory.
The following example shows the contents of the archive log in XML format:
Router# show archive log config all contenttype xml
<?xml version="1.0" encoding="UTF-8"?>
<configLoggerMsg version="1.0">
<absoluteTime>2003-04-23T20:25:19.847Z</absoluteTime>
<logComment>begin test test1</logComment>
<absoluteTime>2003-04-23T20:27:19.847Z</absoluteTime>
<change>PRC_CHANGE</change>
<absoluteTime>2003-04-23T20:28:19.847Z</absoluteTime>
<context><cli>interface e0</cli></context>
<cli>ip address 10.1.1.1 255.255.255.0</cli>
<change>PRC_CHANGE</change>
<cli>ip address 10.1.1.1 255.255.255.0</cli>
<absoluteTime>2003-04-23T20:29:19.847Z</absoluteTime>
<logComment>end test test1</logComment>
show async bootp
To 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 Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
Examples
The following is sample output from the show async bootp command:
The following extended data will be sent in BOOTP responses:
bootfile (for address 192.168.1.1) "pcboot"
bootfile (for address 172.16.1.111) "dirtboot"
Table 56 describes the significant fields shown in the display.
Table 56 show async bootp Field Descriptions
Field
|
Description
|
bootfile... "pcboot"
|
Boot file for address 192.168.1.1 is named pcboot.
|
subnet-mask 255.255.0.0
|
Subnet mask.
|
time-offset -3600
|
Local time is one hour (3600 seconds) earlier than UTC time.
|
time-server 192.168.1.1
|
Address of the time server for the network.
|
Related Commands
Command
|
Description
|
async-bootp
|
Configures extended BOOTP requests for asynchronous interfaces as defined in RFC 1084.
|
show autoupgrade configuration unknown
To 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 Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC (#)
Command History
Release
|
Modification
|
12.4(15)T
|
This command was introduced.
|
Usage Guidelines
Use 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.
Examples
The 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:
Router# show autoupgrade configuration unknown
! Config Lines not understood by the current image:
crypto pki trustpoint aum_cisco_ca
crypto pki certificate chain aum_cisco_ca
certificate ca 40DCB71E54EE24CBE5326F8006BBA4F6 nvram:SecureServer#A4F6CA.cer
transport output lat pad telnet rlogin lapb-ta mop udptn v120 ssh
Total 9 Invalid Config Lines
Related Commands
Command
|
Description
|
upgrade automatic abortversion
|
Cancels a scheduled reloading of the device with a new Cisco IOS software image.
|
upgrade automatic getversion
|
Downloads a Cisco IOS software image directly from www.cisco.com or from a non-Cisco server.
|
upgrade automatic runversion
|
Reloads the device with a new Cisco IOS software image.
|
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
all
|
(Optional) Displays all possible Flash information.
|
chips
|
(Optional) Displays information about the Flash chip.
|
filesys
|
(Optional) Displays information about the file system.
|
Defaults
This command has no default settings.
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
12.2(14)SX
|
Support for this command was introduced on the Supervisor Engine 720.
|
12.2(17d)SXB
|
Support for this command on the Supervisor Engine 2 was extended to Release 12.2(17d)SXB.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
Examples
This example shows how to display information about the file system status:
Router> show bootflash: filesys
-------- F I L E S Y S T E M S T A T U S --------
DEVICE INFO BLOCK: bootflash
Magic Number = 6887635 File System Vers = 10000 (1.0)
Length = 1000000 Sector Size = 40000
Programming Algorithm = 39 Erased State = FFFFFFFF
File System Offset = 40000 Length = F40000
MONLIB Offset = 100 Length = C628
Bad Sector Map Offset = 3FFF8 Length = 8
Squeeze Log Offset = F80000 Length = 40000
Squeeze Buffer Offset = FC0000 Length = 40000
Bytes Used = 917CE8 Bytes Available = 628318
Bad Sectors = 0 Spared Sectors = 0
OK Files = 2 Bytes = 917BE8
Deleted Files = 0 Bytes = 0
Files w/Errors = 0 Bytes = 0
This example shows how to display image information:
-#- ED --type-- --crc--- -seek-- nlen -length- -----date/time------ name
1 .. image 8C5A393A 237E3C 14 2063804 Aug 23 1999 16:18:45 c6msfc-boot-mz
2 .. image D86EE0AD 957CE8 9 7470636 Sep 20 1999 13:48:49 rp.halley
This example shows how to display all bootflash information:
Router> show bootflash: all
-#- ED --type-- --crc--- -seek-- nlen -length- -----date/time------ name
1 .. image 8C5A393A 237E3C 14 2063804 Aug 23 1999 16:18:45 c6msfc-boot-
2 .. image D86EE0AD 957CE8 9 7470636 Sep 20 1999 13:48:49 rp.halley
6456088 bytes available (9534696 bytes used)
-------- F I L E S Y S T E M S T A T U S --------
DEVICE INFO BLOCK: bootflash
Magic Number = 6887635 File System Vers = 10000 (1.0)
Length = 1000000 Sector Size = 40000
Programming Algorithm = 39 Erased State = FFFFFFFF
File System Offset = 40000 Length = F40000
MONLIB Offset = 100 Length = C628
Bad Sector Map Offset = 3FFF8 Length = 8
Squeeze Log Offset = F80000 Length = 40000
Squeeze Buffer Offset = FC0000 Length = 40000
Bytes Used = 917CE8 Bytes Available = 628318
Bad Sectors = 0 Spared Sectors = 0
OK Files = 2 Bytes = 917BE8
Deleted Files = 0 Bytes = 0
Files w/Errors = 0 Bytes = 0
Related Commands
Command
|
Description
|
delete
|
Marks files on bootflash for deletion.
|
squeeze
|
Removes files from bootflash that have been marked for deletion.
|
show bootvar
To 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 Description
This command has no arguments or keywords.
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
11.3 AA
|
This command was introduced.
|
12.2(14)SX
|
Support for this command was implemented on the Supervisor Engine 720.
|
12.2(17d)SXB
|
Support for this command on the Supervisor Engine 2 was integrated into Release 12.2(17d)SXB.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
Usage Guidelines
Supported 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.
Examples
Supported Platforms Other than the Cisco 7600 Series Router
The following is sample output from the show bootvar command:
CONFIG_FILE variable = nvram:
Current CONFIG_FILE variable = slot0:router-config
BOOTLDR variable not exist
Configuration register is 0x0
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):
Current CONFIG_FILE variable =
BOOTLDR variable does not exist
Configuration register is 0x0
current slave is in slot 7
BOOTLDR variable does not exist
Configuration register is 0x0
Table 57 describes the significant fields shown in the displays.
Table 57 show bootvar Field Descriptions
Field
|
Description
|
BOOT variable
|
Displays a list of specified bootable images.
|
CONFIG_FILE variable
|
Indicates where to locate the startup (initialization) configuration file.
|
Current CONFIG_FILE variable
|
Identifies the run-time configuration file.
|
BOOTLDR variable
|
Identifies the location of the boot image that ROM uses for booting, if it is specified.
|
Configuration register
|
Specifies router behavior, such as how the router boots, options while booting, and console speed (baud rate for a terminal emulation session).
|
current slave is in slot 7
|
Indicates the slot where the redundant system is located in HSA configurations.
|
Cisco 7600 Series Router
This example shows how to display information about the BOOT environment variable:
BOOT variable = sup-bootflash:c6sup12-js-mz.121-13.E,12
BOOTLDR variable = bootflash:c6msfc2-boot-mz.121-13.E.bin
Configuration register is 0x2102
Standby has 112640K/18432K bytes of memory.
Standby BOOT variable = bootflash:c6sup12-js-mz.121-13.E,12
Standby CONFIG_FILE variable =
Standby BOOTLDR variable = bootflash:c6msfc2-boot-mz.121-13.E.bin
Standby Configuration register is 0x2102
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
Command
|
Description
|
boot bootldr
|
Specifies the location of the boot image that ROM uses for booting.
|
boot bootstrap
|
Configures the filename that is used to boot a secondary bootstrap image.
|
boot config
|
Specifies the device and filename of the configuration file from which the router configures itself during initialization (startup).
|
boot system
|
Specifies the system image that the router loads at startup.
|
copy
|
Copies a file from source to a destination.
|
show version
|
Displays the configuration of the system hardware, the software version, the names and sources of configuration files, and the boot images.
|
show buffers
To display statistics for the buffer pools on the network server when Cisco IOS or Cisco IOS Software Modularity images are running, use the show buffers command in user EXEC or privileged EXEC mode.
show buffers [{address hex-address | failures | pool pool-name | processes | {all | assigned
[process-id] | free | old | input-interface interface-type interface-number} [pool pool-name]}
[dump | header | packet]]
Syntax Description
address
|
(Optional) Displays buffers at a specified address.
|
hex-address
|
(Optional) Address in hexadecimal notation.
|
failures
|
(Optional) Displays buffer allocation failures.
|
pool
|
(Optional) Displays buffers in a specified buffer pool.
|
pool-name
|
(Optional) Name of buffer pool.
|
processes
|
(Optional) For Cisco IOS Software Modularity images only. Displays buffers connected to Packet Manager.
|
all
|
(Optional) Displays all buffers.
|
assigned
|
(Optional) Displays the buffers in use.
|
process-id
|
(Optional) For Cisco IOS Software Modularity images only. POSIX process identifier.
|
free
|
(Optional) Displays the buffers available for use.
|
old
|
(Optional) Displays buffers older than one minute.
|
input-interface
|
(Optional) Displays interface pool information. If an interface type is specified and this interface has its own buffer pool, information for that pool is displayed.
|
interface-type
|
(Optional) Interface type.
|
interface-number
|
(Optional) Interface number.
|
dump
|
(Optional) Displays the buffer header and all data.
|
header
|
(Optional) Displays the buffer header only.
|
packet
|
(Optional) Displays the buffer header and packet data.
|
Command Default
If no options are specified, all buffer pool information is displayed.
Command Modes
User EXEC (>)
Privileged EXEC (#)
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
12.3
|
The option to filter display output based on specific buffer pools was expanded.
|
12.2(18)SXF4
|
Two additional fields were added to the output to support Cisco IOS Software Modularity.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
Examples
Example output varies between Cisco IOS software images and Cisco IOS Software Modularity software images. To view the appropriate output, choose one of the following sections:
•
Cisco IOS Software
•
Cisco IOS Software Modularity
Cisco IOS Software
The following is sample output from the show buffers command with no arguments, showing all buffer pool information:
398 in free list (500 max allowed)
1266 hits, 0 misses, 0 created
Small buffers, 104 bytes (total 50, permanent 50):
50 in free list (20 min, 150 max allowed)
551 hits, 0 misses, 0 trims, 0 created
Middle buffers, 600 bytes (total 25, permanent 25):
25 in free list (10 min, 150 max allowed)
39 hits, 0 misses, 0 trims, 0 created
Big buffers, 1524 bytes (total 50, permanent 50):
49 in free list (5 min, 150 max allowed)
27 hits, 0 misses, 0 trims, 0 created
VeryBig buffers, 4520 bytes (total 10, permanent 10):
10 in free list (0 min, 100 max allowed)
0 hits, 0 misses, 0 trims, 0 created
Large buffers, 5024 bytes (total 0, permanent 0):
0 in free list (0 min, 10 max allowed)
0 hits, 0 misses, 0 trims, 0 created
Huge buffers, 18024 bytes (total 0, permanent 0):
0 in free list (0 min, 4 max allowed)
0 hits, 0 misses, 0 trims, 0 created
Ethernet0 buffers, 1524 bytes (total 64, permanent 64):
16 in free list (0 min, 64 max allowed)
16 max cache size, 16 in cache
Ethernet1 buffers, 1524 bytes (total 64, permanent 64):
16 in free list (0 min, 64 max allowed)
16 max cache size, 16 in cache
Serial0 buffers, 1524 bytes (total 64, permanent 64):
16 in free list (0 min, 64 max allowed)
16 max cache size, 16 in cache
Serial1 buffers, 1524 bytes (total 64, permanent 64):
16 in free list (0 min, 64 max allowed)
16 max cache size, 16 in cache
TokenRing0 buffers, 4516 bytes (total 48, permanent 48):
0 in free list (0 min, 48 max allowed)
16 max cache size, 16 in cache
TokenRing1 buffers, 4516 bytes (total 32, permanent 32):
32 in free list (0 min, 48 max allowed)
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.
Huge buffers, 18024 bytes (total 5, permanent 0, peak 5 @ 5d18h):
4 in free list (3 min, 104 max allowed)
0 hits, 1 misses, 101 trims, 106 created
0 failures (0 no memory)
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.
Huge buffers, 65280 bytes (total 4, permanent 2, peak 184 @ 01:01:15):
4 in free list (0 min, 4 max allowed)
32521 hits, 143636 misses, 14668 trims, 14670 created
143554 failures (0 no memory)
The following is sample output from the show buffers command with an interface type and interface number:
Router# show buffers Ethernet 0
Ethernet0 buffers, 1524 bytes (total 64, permanent 64):
16 in free list (0 min, 64 max allowed)
16 max cache size, 16 in cache
Table 58 describes the significant fields shown in the display.
Table 58 show buffers (Cisco IOS Software) Field Descriptions
Field
|
Description
|
Buffer elements
|
Small structures used as placeholders for buffers in internal operating system queues. Used when a buffer may need to be on more than one queue.
|
free list
|
Total number of the currently unallocated buffer elements.
|
max allowed
|
Maximum number of buffers that are available for allocation.
|
hits
|
Count of successful attempts to allocate a buffer when needed.
|
misses
|
Count of buffer allocation attempts that resulted in growing the buffer pool to allocate a buffer.
|
created
|
Count of new buffers created to satisfy buffer allocation attempts when the available buffers in the pool have already been allocated.
|
Public Buffer Pools
|
Small buffers
|
Buffers that are 104 bytes long.
|
Middle buffers
|
Buffers that are 600 bytes long.
|
Big buffers
|
Buffers that are 1524 bytes long.
|
VeryBig buffers
|
Buffers that are 4520 bytes long.
|
Large buffers
|
Buffers that are 5024 bytes long.
|
Huge buffers
|
Buffers that are 18,024 bytes long.
|
total
|
Total number of this type of buffer.
|
permanent
|
Number of these buffers that are permanent.
|
peak
|
Maximum number of buffers created (highest total) and the time when that peak occurred. Formats include weeks, days, hours, minutes, and seconds. Not all systems report a peak value, which means this field may not display in output.
|
free list
|
Number of available or unallocated buffers in that pool.
|
min
|
Minimum number of free or unallocated buffers in the buffer pool.
|
max allowed
|
Maximum number of free or unallocated buffers in the buffer pool.
|
hits
|
Count of successful attempts to allocate a buffer when needed.
|
misses
|
Count of buffer allocation attempts that resulted in growing the buffer pool in order to allocate a buffer.
|
trims
|
Count of buffers released to the system because they were not being used. This field is displayed only for dynamic buffer pools, not interface buffer pools, which are static.
|
created
|
Count of new buffers created in response to misses. This field is displayed only for dynamic buffer pools, not interface buffer pools, which are static.
|
Interface Buffer Pools
|
total
|
Total number of this type of buffer.
|
permanent
|
Number of these buffers that are permanent.
|
free list
|
Number of available or unallocated buffers in that pool.
|
min
|
Minimum number of free or unallocated buffers in the buffer pool.
|
max allowed
|
Maximum number of free or unallocated buffers in the buffer pool.
|
hits
|
Count of successful attempts to allocate a buffer when needed.
|
fallbacks
|
Count of buffer allocation attempts that resulted in falling back to the public buffer pool that is the smallest pool at least as big as the interface buffer pool.
|
max cache size
|
Maximum number of buffers from the pool of that interface that can be in the buffer pool cache of that interface. Each interface buffer pool has its own cache. These are not additional to the permanent buffers; they come from the buffer pools of the interface. Some interfaces place all of their buffers from the interface pool into the cache. In this case, it is normal for the free list to display 0.
|
failures
|
Total number of times a buffer creation failed. The failure may have occurred because of a number of different reasons, such as low processor memory, low IOMEM, or no buffers in the pool when called from interrupt context.
|
no memory
|
Number of times there has been low memory during buffer creation. Low or no memory during buffer creation may not necessarily mean that buffer creation failed; memory can be obtained from an alternate resource such as a fallback pool.
|
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.
500 in free list (500 max allowed)
106586 hits, 0 misses, 0 created
Small buffers, 104 bytes (total 50, permanent 50, peak 54 @ 1d13h):
49 in free list (20 min, 150 max allowed)
54486 hits, 0 misses, 4 trims, 4 created
Middle buffers, 600 bytes (total 25, permanent 25, peak 27 @ 1d13h):
25 in free list (10 min, 150 max allowed)
20 hits, 0 misses, 2 trims, 2 created
Big buffers, 1536 bytes (total 50, permanent 50):
50 in free list (40 min, 150 max allowed)
6 hits, 0 misses, 0 trims, 0 created
VeryBig buffers, 4520 bytes (total 10, permanent 10):
10 in free list (0 min, 100 max allowed)
0 hits, 0 misses, 0 trims, 0 created
Large buffers, 5024 bytes (total 0, permanent 0):
0 in free list (0 min, 10 max allowed)
0 hits, 0 misses, 0 trims, 0 created
Huge buffers, 18024 bytes (total 1, permanent 0, peak 1 @ 1d13h):
0 in free list (0 min, 4 max allowed)
1 hits, 0 misses, 0 trims, 0 created
! Start of Cisco IOS Software Modularity fields
Header buffers, 880 bytes (total 1000, peak 142 @ 1d13h):
864 in permanent free list
Temporary buffer headers:
Header buffers, 896 bytes (total 0):
0 hits, 0 misses, 0 trims, 0 created
! End of Cisco IOS Software Modularity fields
Logger Pool buffers, 600 bytes (total 150, permanent 150):
150 in free list (150 min, 150 max allowed)
Table 59 describes the significant fields shown in the display that are different from the fields in Table 58.
Table 59 show buffers (Cisco IOS Software Modularity) Field Descriptions
Field
|
Description
|
Public Buffer Headers
|
Header buffers
|
Buffers that are 880 bytes long.
|
total
|
Total number of this type of buffer.
|
permanent free list
|
Number of available or unallocated permanent header buffers.
|
hits
|
Count of successful attempts to allocate a header buffer when needed.
|
misses
|
Count of buffer allocation attempts that resulted in growing the buffer pool in order to allocate a buffer.
|
Temporary Buffer Headers
|
Header buffers
|
Buffers that are 896 bytes long.
|
total
|
Total number of this type of buffer.
|
free list
|
Number of available or unallocated header buffers in that pool.
|
hits
|
Count of successful attempts to allocate a buffer when needed.
|
misses
|
Count of buffer allocation attempts that resulted in growing the buffer pool in order to allocate a buffer.
|
trims
|
Count of buffers released to the system because they were not being used. This field is displayed only for dynamic buffer pools, not interface buffer pools, which are static.
|
created
|
Count of new buffers created in response to misses. This field is displayed only for dynamic buffer pools, not interface buffer pools, which are static.
|
failures
|
Total number of allocation requests that have failed because no buffer was available for allocation; the datagram was lost. Such failures normally occur at interrupt level.
|
show buffers summary
To 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 Description
This command has no arguments or keywords.
Command Default
All buffer usage summary information is displayed.
Command Modes
Privileged EXEC (#)
Command History
Release
|
Modification
|
12.2(33)SXI
|
This command was introduced.
|
Examples
The following is sample output from the show buffers summary command:
Router# show buffers summary
Non-aligned packet(s): 25
pc = 0x40612F74 count = 37
pc = 0x418D77FC count = 24
pc = 0x418571E0 count = 1
pc = 0x41860488 count = 1
Non-aligned packet(s): 39
pc = 0x418D77FC count = 38
pc = 0x41860488 count = 1
pc = 0x40612F74 count = 23
Non-aligned packet(s): 333
pc = 0x418D77FC count = 333
pc = 0x40612F74 count = 2
pc = 0x4049FFD8 count = 3
Non-aligned packet(s): 32078
pc = 0x418D77FC count = 32006
pc = 0x4065FD40 count = 7
pc = 0x409E915C count = 1
pc = 0x40652A58 count = 65
Non-aligned packet(s): 10
pc = 0x418D77FC count = 10
pc = 0x418D77FC count = 8
pc = 0x418D77FC count = 2
Table 58 describes the significant fields shown in the display.
Table 60 show buffers summary Field Descriptions
Field
|
Description
|
Non-alligned
|
Indicates the number of packets not alligned to 32 bits
|
PC
|
Specifies who allocated buffer from this pool, for example, small buffer pool, middle buffer pool and so on.
|
Public Buffer Pools
|
Small buffers
|
Buffers that are 104 bytes long.
|
Middle buffers
|
Buffers that are 600 bytes long.
|
Big buffers
|
Buffers that are 1524 bytes long.
|
VeryBig buffers
|
Buffers that are 4520 bytes long.
|
Large buffers
|
Buffers that are 5024 bytes long.
|
Huge buffers
|
Buffers that are 18,024 bytes long.
|
| |
Related Commands
Command
|
Description
|
show buffers
|
Displays statistics for the buffer pools on the network server.
|
show c2600
To display information for troubleshooting the Cisco 2600 series router, use the show c2600 command in EXEC mode.
show c2600
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Release
|
Modification
|
11.3 XA
|
This command was introduced.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
Usage Guidelines
The show c2600 command provides complex troubleshooting information that pertains to the platform's shared references rather than to a specific interface.
Examples
The following is sample output from the show c2600 command:
C2600 Platform Information:
Vect Handler # of Ints Name
00 801F224C 00000000 Xilinx bridge error interrupt
01 801DE768 0D3EE155 MPC860 TIMER INTERRUPT
02 801E94E0 0000119E 16552 Con/Aux Interrupt
04 801F0D94 00000000 PA Network Management Int Handler
05 801E6C34 00000000 Timebase Reference Interrupt
06 801F0DE4 00002C1A PA Network IO Int Handler
07 801F0EA0 0000015D MPC860 CPM INTERRUPT
14 801F224C 00000000 Xilinx bridge error interrupt
SIU_IRQ_MASK = FFFFFFFF SIEN = EF02xxxx Current Level = 00
Spurious IRQs = 00000000 SIPEND = 0000xxxx
Throttle Count = 00000000 Timer Count = 00000000
Netint usec = 00000000 Netint Mask usec = 000003E8
Active = 0 Configured = 0
Requests = 00000349 Drops = 00000000
Complete = 00000349 Post Coalesce Frames = 00000349
Available Blocks = 256/256
Version string burned in chip: "A986122997"
New version after next program operation: "B018020998"
Table 61 describes the significant fields shown in the display.
Table 61 show c2600 Field Descriptions
Field
|
Description
|
Interrupts
|
Denotes that the next section describes the status of the interrupt services.
|
Assigned Handlers
|
Denotes a subsection of the Interrupt section that displays data about the interrupt handlers.
|
Vect
|
The processor vector number.
|
Handler
|
The execution address of the handler assigned to this vector.
|
# of Ints
|
The number of times this handler has been called.
|
Name
|
The name of the handler assigned to this vector.
|
IOS Priority Masks
|
Denotes the subsection of the Interrupt section that displays internal Cisco IOS priorities. Each item in this subsection indicates a Cisco IOS interrupt level and the bit mask used to mask out interrupt sources when that Cisco IOS level is being processed. Used exclusively for debugging.
|
SIU_IRQ_MASK
|
For engineering level debug only.
|
Spurious IRQs
|
For engineering level debug only.
|
Interrupt Throttling:
|
This subsection describes the behavior of the Interrupt Throttling mechanism on the platform.
|
Throttle Count
|
Number of times throttle has become active.
|
Timer Count
|
Number of times throttle has deactivated because the maximum masked out time for network interrupt level has been reached.
|
Netint usec
|
Maximum time network level is allowed to run (in microseconds).
|
Netint Mask usec
|
Maximum time network level interrupt is masked out to allow process level code to run (in microseconds).
|
Active
|
Indicates that the network level interrupt is masked or that the router is in interrupt throttle state.
|
Configured
|
Indicates that throttling is enabled or configured when set to 1.
|
Longest IRQ
|
Duration of longest network level interrupt (in microseconds).
|
IDMA Status
|
Monitors the activity of the Internal Direct Memory Access (IDMA) hardware and software. Used to coalesce packets (turn particularized packets into non particularized packets) for transfer to the process level switching mechanism.
|
Requests
|
Number of times the IDMA engine is asked to coalesce a packet.
|
Drops
|
Number of times the coalescing operation was aborted.
|
Complete
|
Number of times the operation was successful.
|
Post Coalesce Frames
|
Number of Frames completed post coalesce processing.
|
Giant
|
Number of packets too large to coalesce.
|
Available Blocks
|
Indicates the status of the request queue, in the format N/M where N is the number of empty slots in queue and M is the total number of slots; for example, 2/256 indicates that the queue has 256 entries and can accept two more requests before it is full.
|
ISP Status
|
Provides status of In-System-Programmable (ISP) hardware.
|
Version string burned in chip
|
Current version of ISP hardware.
|
New version after next program operation
|
Version of ISP hardware after next ISP programming operation.
|
ISP family type
|
Device family number of ISP hardware.
|
ISP chip ID
|
Internal ID of ISP hardware as designated by the chip manufacturer.
|
Device is programmable
|
"Yes" or "No." Indicates if an ISP operation is possible on this board.
|
Related Commands
Command
|
Description
|
show context
|
Displays information stored in NVRAM when the router crashes.
|
show c7200
To display information about the CPU and midplane for Cisco 7200 series routers, use the show c7200 command in EXEC mode.
show c7200
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Release
|
Modification
|
11.2
|
This command was introduced.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
Usage Guidelines
You 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.
Examples
The following is sample output from the show c7200 command:
C7200 Network IO Interrupt Throttling:
throttle count=0, timer count=0
netint usec=3999, netint mask usec=200
Hardware revision 1.2 Board revision A0
Serial number 2863311530 Part number 170-43690-170
Test history 0xAA RMA number 170-170-170
MAC=0060.3e28.ee00, MAC Size=1024
EEPROM format version 1, Model=0x6
0x20: 01 06 01 02 AA AA AA AA AA AA AA AA 00 60 3E 28
0x30: EE 00 04 00 AA AA AA AA AA AA AA 50 AA AA AA AA
Hardware revision 2.0 Board revision A0
Serial number 3509953 Part number 73-1536-02
Test history 0x0 RMA number 00-00-00
0x20: 01 15 02 00 00 35 8E C1 49 06 00 02 00 00 00 00
0x30: 50 00 00 00 FF FF FF FF FF FF FF FF FF FF FF FF
show catalyst6000
To 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
all
|
Displays the MAC-address ranges and the current and peak traffic-meter reading.
|
chassis-mac-address
|
Displays the MAC-address range.
|
switching-clock
|
Displays the failure recovery mode of the switching clock.
|
traffic-meter
|
Displays the percentage of the backplane (shared bus) utilization.
|
Defaults
all
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
12.2(14)SX
|
Support for this command was introduced on the Supervisor Engine 720.
|
12.2(17d)SXB
|
Support for this command on the Supervisor Engine 2 was extended to Release 12.2(17d)SXB.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
Usage Guidelines
If 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.
Examples
This example shows how to display the MAC-address ranges and the current and peak traffic-meter readings:
Router> show catalyst6000 all
chassis MAC addresses: 64 addresses from 0001.6441.60c0 to 0001.6441.60ff
traffic meter = 0% Never cleared
peak = 0% reached at 08:14:38 UTC Wed Mar 19 2003
switching-clock: clock switchover and system reset is allowed
This example shows how to display the MAC-address ranges:
Router# show catalyst6000 chassis-mac-address
chassis MAC addresses: 1024 addresses from 00d0.004c.1800 to 00d0.004c.1c00
This example shows how to display the current and peak traffic-meter readings:
Router> show catalyst6000 traffic-meter
traffic meter = 0% peak = 0% at 09:57:58 UTC Mon Nov 6 2000
This example shows how to display the failure recovery mode of the switching clock:
Router> show catalyst6000 switching-clock
switching-clock: clock switchover and system reset is allowed
Related Commands
Command
|
Description
|
show environment alarm
|
Displays the information about the environmental alarm.
|
show fm summary
|
Displays a summary of FM Information.
|
show environment status
|
Displays the information about the operational FRU status.
|
show cls
To 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
brief
|
(Optional) Displays a brief version of the output.
|
Defaults
Without the brief keyword, displays complete output.
Command Modes
EXEC
Command History
Release
|
Modification
|
11.0
|
This command was introduced in a release prior to Cisco IOS Release 11.0.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
Usage Guidelines
The 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.
Examples
The following is sample output from the show cls command:
DTE:1234.4000.0001 1234.4000.0002 04 04
T1 timer:0 T2 timer:0 Inact timer:0
max out:0 max in:0 retry count:10
XID retry:10 XID timer:5000 I-Frame:0
flow:0 DataIndQ:0 DataReqQ:0
The following is sample output from the show cls brief command:
IBD-4500B# show cls brief
DTE:1234.4000.0001 1234.4000.0002 04 04
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
Command
|
Description
|
stun peer-name
|
Enables STUN for an IP address and uses Cisco Link Services (CLS) to access the Frame Relay network.
|
show config id
The 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
detail
|
(Optional) Expands the output of the command to include the ID of the last user to make a configuration change and the process in which the changes were made.
|
Command Default
This 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 Modes
Privileged EXEC (#)
Command History
Release
|
Modification
|
12.2(33)SRC
|
This command was introduced.
|
12.2(33)SB
|
This command was integrated into Cisco IOS Release 12.2(33)SB and implemented on the Cisco 10000 series.
|
12.4(20)T
|
This command was integrated into Cisco IOS Release 12.4(20)T.
|
Usage Guidelines
This 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.
Examples
The 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.:
version:4 time:2006-06-15T15:02:07.572Z
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:
Router# show config id detail
Configuration version : 9
Last change time : 2006-06-18T18:34:34.431Z
Changed from process : Init
Field descriptions are self-explanatory.
Related Commands
Command
|
Description
|
copy running-config startup-config
|
Copies the current running-config file (source) to the startup-config file (destination).
|
show running-config
|
Displays the contents of the currently running configuration file or the configuration for a specific class map, interface, map class, policy map, or virtual-circuit class.
|
show configuration lock
To 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 Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.2(25)S
|
This command was introduced.
|
12.3(14)T
|
This command was integrated into Cisco IOS Release 12.3(14)T.
The output of this command was updated to display the configuration locking class.
|
12.0(31)S
|
The command output was enhanced.
|
12.2(28)SB
|
This command was integrated into Cisco IOS Release 12.2(28)SB.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
12.2(31)SB2
|
This command was implemented on the Cisco 10000 series.
|
12.2(33)SXH
|
This command was integrated into Cisco IOS Release 12.2(33)SXH.
|
12.2(33)SB
|
This command was integrated into Cisco IOS Release 12.2(33)SB and implemented on the Cisco 10000 series.
|
Examples
The 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
Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# configuration mode exclusive ?
auto Lock configuration mode automatically
manual Lock configuration mode on-demand
Router(config)# configuration mode exclusive auto
Router# show running-config | include configuration
configuration mode exclusive auto
Router# configure terminal !<----------- Acquires the lock
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# show configuration lock
Parser Configure Lock
---------------------
Owner PID : 3
User : unknown
TTY : 0
Type : EXCLUSIVE
State : LOCKED
Class : EXPOSED
Count : 1
Pending Requests : 0
User debug info : configure terminal
Router(config)#
Router(config)# end ! <------------ Releases the lock
The following is sample output from the show configuration lock command when the running configuration file is not locked by another user.
Router# show configuration lock
Parser Configure Lock
---------------------
Owner PID : -1
User : unknown
TTY : -1
Type : NO LOCK
State : FREE
Class : unknown
Count : 0
Pending Requests : 0
User debug info :
Cisco IOS Release 12.0(31)S, 12.2(33)SRA, and Later Releases
Router# show configuration lock
------------------------------------------------------
User debug info : configure terminal
Session idle state : TRUE
No of exec cmds getting executed : 0
No of exec cmds blocked : 0
Config wait for show completion : FALSE
Remote ip address : Unknown
Lock active time (in Sec) : 6
Lock Expiration timer (in Sec) : 593
Table 62 describes the significant fields shown in the displays.
Table 62 show configuration lock Field Descriptions
Field
|
Description
|
Owner PID
|
Process identifier (PID) of the process that owns the lock.
|
User
|
Owner's username.
|
TTY
|
Owner's terminal number.
|
Type
|
Lock type (EXCLUSIVE/COUNTER/NO LOCK).
|
State
|
State of the lock (FREE/LOCKED).
|
Class
|
Classification of users of the lock (EXPOSED/ROLLBACK). Processes other than ROLLBACK belong to the EXPOSED class.
|
Count
|
In the case of a counter lock, total number of processes holding the lock.
|
Pending Requests
|
Total number of processes blocked by the lock.
|
User debug info
|
Any string given by the process (used for debugging only).
|
Session idle state
|
Indicates whether the user in an access session locking session is idle. Displays TRUE or FALSE.
|
No of exec cmds getting executed
|
Total number of EXEC commands (show and clear) being executed simultaneously from different sessions.
|
No of exec cmds blocked
|
Total number of EXEC commands (show and clear) waiting for the configuration command (running from the access session locking session) to complete its execution.
|
Config wait for show completion
|
Indicates whether a configuration command executed in an access session locking session is waiting for the completion of the show command being executed simultaneously from a different session. Displays TRUE or FALSE.
|
Remote ip address
|
IP address of the terminal from which the user telneted to the router.
|
Lock active time (in Sec)
|
Amount of time, in seconds, that elapsed since the lock was acquired.
|
Lock Expiration timer (in Sec)
|
The amount of time, in seconds, that expires before the lock is automatically released.
|
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.
Router# configure terminal
Router(config)# configuration mode exclusive auto
Router# configure terminal
Router(config)# show configuration lock
Related Commands
Command
|
Description
|
configuration mode exclusive
|
Enables single-user (exclusive) access functionality for the Cisco IOS CLI.
|
configure replace
|
Replaces the current running configuration with a saved Cisco IOS configuration file.
|
debug configuration lock
|
Enables debugging of the Cisco IOS configuration lock.
|
show context
To 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
summary
|
Displays a summary of all the crashes recorded.
|
all
|
Displays all crashes for all the slots. When optionally used with the slot keyword, displays crash information for the specified slot.
|
slot slot-number [crash-index]
|
Displays information for a particular line card. Slot numbers range from 0 to 11 for the Cisco 12012 router and from 0 to 7 for the Cisco 12008. The index number allows you to look at previous crash contexts. Contexts from the last 24 line card crashes are saved on the GRP card. If the GRP reloads, the last 24 line card crash contexts are lost. For example, show context slot 3 2 shows the second most recent crash for line card in slot 3. Index numbers are displayed by the show context summary command.
|
debug
|
(Optional) Displays crash information as a hex record dump in addition to one of the options listed.
|
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
10.3
|
This command was introduced.
|
11.2 GS
|
The slot slot-number [crash-index] [all] [debug] syntax was added for Cisco 12000 series routers.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
Usage Guidelines
The 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.
Examples
The following is sample output from the show context command following a system failure:
System was restarted by error - a Software forced crash, PC 0x60189354
GS Software (RSP-PV-M), Experimental Version 11.1(2033) [ganesh 111]
Compiled Mon 31-Mar-97 13:21 by ganesh
Image text-base: 0x60010900, data-base: 0x6073E000
Stack trace from system failure:
FP: 0x60AEA798, RA: 0x60189354
FP: 0x60AEA798, RA: 0x601853CC
FP: 0x60AEA7C0, RA: 0x6015E98C
FP: 0x60AEA7F8, RA: 0x6011AB3C
FP: 0x60AEA828, RA: 0x601706CC
FP: 0x60AEA878, RA: 0x60116340
FP: 0x60AEA890, RA: 0x6011632C
GS Software (RSP-PV-M), Experimental Version 11.1(2033) [ganesh 111]
Compiled Mon 31-Mar-97 13:21 by ganesh
Signal = 23, Code = 0x24, Uptime 00:04:19
$0 : 00000000, AT : 60930120, v0 : 00000032, v1 : 00000120
a0 : 60170110, a1 : 6097F22C, a2 : 00000000, a3 : 00000000
t0 : 60AE02A0, t1 : 8000FD80, t2 : 34008F00, t3 : FFFF00FF
t4 : 00000083, t5 : 3E840024, t6 : 00000000, t7 : 11010132
s0 : 00000006, s1 : 607A25F8, s2 : 00000001, s3 : 00000000
s4 : 00000000, s5 : 00000000, s6 : 00000000, s7 : 6097F755
t8 : 600FABBC, t9 : 00000000, k0 : 30408401, k1 : 30410000
gp : 608B9860, sp : 60AEA798, s8 : 00000000, ra : 601853CC
EPC : 60189354, SREG : 3400EF03, Cause : 00000024
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).
Router# show context summary
1 - crash at 18:06:41 UTC Tue Nov 5 1996
2 - crash at 12:14:55 UTC Mon Nov 4 1996
The following is sample output from the show context command following an unexpected system reload on a Cisco 2600 series router.
S/W Version: Cisco IOS Software
Cisco IOS (tm) c2600 Software (c2600-JS-M), Released Version 11.3(19980115:184921]
Copyright (c) 1986-2003 by Cisco Systems, Inc.
Compiled Thu 15-Jan-98 13:49 by mmagno
Exception occurred at: 00:02:26 UTC Mon Mar 1 1993
Exception type: Data TLB Miss (0x1200)
PC = 0x80109964 MSR = 0x00009030 CR = 0x55FFFD35 LR = 0x80109958
CTR = 0x800154E4 XER = 0xC000BB6F DAR = 0x00000088 DSISR = 0x00000249
DEC = 0x7FFFDFCA TBU = 0x00000000 TBL = 0x15433FCF IMMR = 0x68010020
R0 = 0x80000000 R1 = 0x80E80BD0 R2 = 0x80000000 R3 = 0x00000000
R4 = 0x80E80BC0 R5 = 0x40800000 R6 = 0x00000001 R7 = 0x68010000
R8 = 0x00000000 R9 = 0x00000060 R10 = 0x00001030 R11 = 0xFFFFFFFF
R12 = 0x00007CE6 R13 = 0xFFF379E8 R14 = 0x80D50000 R15 = 0x00000000
R16 = 0x00000000 R17 = 0x00000000 R18 = 0x00000000 R19 = 0x00000000
R20 = 0x00000000 R21 = 0x00000001 R22 = 0x00000010 R23 = 0x00000000
R24 = 0x00000000 R25 = 0x80E91348 R26 = 0x01936010 R27 = 0x80E92A80
R28 = 0x00000001 R29 = 0x019BA920 R30 = 0x00000000 R31 = 0x00000018
Frame 00: SP = 0x80E80BD0 PC = 0x80109958
Frame 01: SP = 0x80E80C28 PC = 0x8010A720
Frame 02: SP = 0x80E80C40 PC = 0x80271010
Frame 03: SP = 0x80E80C50 PC = 0x8025EE64
Frame 04: SP = 0x80DEE548 PC = 0x8026702C
Frame 05: SP = 0x80DEE558 PC = 0x8026702C
Table 63 describes the significant fields shown in the display.
Table 63 show context Field Descriptions
Field
|
Description
|
S/W Version
|
Standard Cisco IOS version string as displayed.
|
Exception occurred at
|
Router real time when exception occurred. The router must have the clock time properly configured for this to be accurate.
|
Exception type
|
Technical reason for exception. For engineering analysis.
|
CPU Register Context
|
Technical processor state information. For engineering analysis.
|
Stack trace
|
Technical processor state information. For engineering analysis.
|
Related Commands
Command
|
Description
|
show processes
|
Displays information about the active processes.
|
show stacks
|
Monitors the stack usage of processes and interrupt routines.
|
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
atm slot-number
|
(Optional) Displays the ATM controllers. Number is slot-number/ port-number (for example, 4/0). Slot numbers range from 0 to 11 for the Cisco 12012 router and from 0 to 7 for the Cisco 12008 router.
|
clock
|
(Optional) Displays the clock card configuration.
|
csar [register]
|
(Optional) Displays the Cisco Cell Segmentation and Reassembly (CSAR) information. CSAR is the name of the chip on the card that handles traffic between the GRP and the switch fabric interface ASICs.
|
csc-fpga
|
(Optional) Displays the clock and scheduler card register information in the field programmable gate array (FPGA).
|
dp83800
|
(Optional) Displays the Ethernet information on the GRP card.
|
fab-clk
|
(Optional) Display the switch fabric clock register information. The switch fabric clock FPGA is a chip that monitors the incoming fabric clock generated by the switch fabric. This clock is needed by each card connecting to the switch fabric to properly communicate with it. Two switch fabric clocks arrive at each card; only one can be used. The FPGA monitors both clocks and selects which one to use if only one of them is running.
|
fia [register]
|
(Optional) Displays the fabric interface ASIC information and optionally displays the register information.
|
pos [slot-number] [details]
|
(Optional) Displays the POS framer state and optionally displays all the details for the interface. Number is slot-number/port-number (for example, 4/0). Slot numbers range from 0 to 11 for the Cisco 12012 router and from 0 to 7 for the Cisco 12008 router.
|
queues [slot-number]
|
(Optional) Displays the SDRAM buffer carve information and optionally displays the information for a specific line card. The SDRAM buffer carve information displayed is suggested carve information from the GRP card to the line card. Line cards might change the shown percentages based on SDRAM available. Slot numbers range from 0 to 11 for the Cisco 12012 router and from 0 to 7 for the Cisco 12008.
|
sca
|
(Optional) Displays the SCA register information. The SCA is an ASIC that arbitrates among the line cards requests to use the switch fabric.
|
xbar
|
(Optional) Displays the crossbar register information. The XBAR is an ASIC that switches the data as it passes through the switch fabric.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
11.2 GS
|
This command was introduced to support the Cisco 12000 series routers.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
Usage Guidelines
This information provided by this command is intended for use only by technical support representatives in analyzing system failures in the field.
Examples
The following is sample output from the show controllers pos command for a Cisco 12012:
Router# show controllers pos 7/0
LOF = 2 LOS = 0 BIP(B1) = 5889
AIS = 2 RDI = 2 FEBE = 146 BIP(B2) = 2106453
AIS = 2 RDI = 4 FEBE = 63 BIP(B3) = 3216
LOP = 0 PSE = 8 NSE = 3 NEWPTR = 2
State: PSBF_state = False
Rx(K1/K2): F0/15 Tx(K1/K2): 00/00
PATH TRACE BUFFER : STABLE
Remote interface: POS10/0
Remote IP addr : 10.201.101.2
Remote Rx(K1/K2): F0/15 Tx(K1/K2): 00/00
Related Commands
Command
|
Description
|
clear controllers
|
Resets the T1 or E1 controller.
|
show controllers (line card image)
|
Displays information that is specific to the hardware on a line card.
|
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]}
Syntax Description
atm
|
Displays the ATM controller information.
|
port-number
|
(Optional) Displays request for the physical interface on the ATM card. The range of choices is from 0 to 3.
|
all
|
(Optional) Lists all details.
|
sar
|
(Optional) Lists SAR interactive command.
|
summary
|
(Optional) Lists SAR status summary.
|
fia
|
Displays the fabric interface ASIC information.
|
register
|
(Optional) Displays the register information.
|
frfab
|
(Optional) Displays the "from" (transmit) fabric information.
|
tofab
|
(Optional) Displays the "to" (receive) fabric information.
|
bma
|
For the frfab or tofab keywords, displays microcode, micro sequencer, or register information for the silicon queuing engine (SQE), also known as the buffer management ASIC (BMA).
|
microcode
|
Displays SQE information for the microcode bundled in the line card and currently running version.
|
mis-inst
|
Displays SQE information for the micro sequencer instruction.
|
register
|
Displays silicon queuing engine (SQE) information for the register.
|
qelem
|
For the frfab or tofab keywords, displays the SDRAM buffer pool queue element summary information.
|
start-queue-element
|
Specifies the start queue element number from 0 to 65535.
|
end-queue-element
|
(Optional) Specifies the end queue element number from 0 to 65535).
|
qnum
|
For the frfab or tofab keywords, displays the SDRAM buffer pool queue detail information.
|
start-queue-number
|
Specifies the start free queue number (from 0 to 127).
|
end-queue-number
|
(Optional) Specifies the end free queue number (from 0 to 127).
|
queues
|
For the frfab or tofab keywords, displays the SDRAM buffer pool information.
|
statistics
|
For the frfab or tofab keywords, displays the BMA counters.
|
io
|
Displays input/output registers.
|
l3
|
Displays Layer 3 ASIC information.
|
pos
|
Displays packet-over-sonic (POS) information for framer registers, framer queues, and ASIC registers.
|
framers
|
Displays the POS framer registers.
|
queues
|
Displays the POS framer queue information.
|
registers
|
Displays the ASIC registers.
|
rxsram
|
Displays the receive queue SRAM.
|
port-number
|
Specifies a port number (valid range is from 0 to 3).
|
queue-start-address
|
Specifies the queue SRAM logical starting address.
|
queue-length
|
(Optional) Specifies the queue SRAM length.
|
txsram
|
Displays the transmit queue SRAM.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
11.2 GS
|
This command was added to support the Cisco 12000 series Gigabit Switch Routers.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
Usage Guidelines
This 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.
Examples
Because 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:
Router# execute-on slot 4 show controllers atm 0
TX SAR (Beta 1.0.0) is Operational;
RX SAR (Beta 1.0.0) is Operational;
Interface Configuration Mode:
Active Maker Channels: total # 6
VCID ChnnlID Type OutputInfo InPkts InOAMs MacString
1 0888 UBR 0C010010 0 0 08882000AAAA030000000800
2 0988 VBR 04010020 0 0 09882000
3 8BC8 UBR 0C010030 0 0 8BC82000AAAA030000000800
4 0E08 UBR 0C010040 0 0 0E082000AAAA030000000800
10 1288 VBR 040100A0 0 0 12882000
11 8BE8 VBR 0C0100B0 0 0 8BE82000AAAA030000000800
total_tx_idle_cells 215267 total_tx_paks 0 total_tx_abort_paks 0
total_rx_paks 0 total_rx_drop_paks 0 total_rx_discard_cells 15
total_rx_crc_err_paks 0 total_rx_giant_paks 0
total_rx_abort_paks 0 total_rx_crc10_cells 0
total_rx_tmout_paks 0 total_rx_unknown_paks 0
total_rx_out_buf_paks 0 total_rx_unknown_vc_paks 0
BATMAN Asic Register Values:
hi_addr_reg 0x8000, lo_addr_reg 0x000C, boot_msk_addr 0x0780,
rmcell_msk_addr 0x0724, rmcnt__msk_addr 0x07C2, txbuf_msk_addr 0x070C,
CM622 SAR Boot Configuration:
txind_q_addr 0x14000 txcmd_q_addr 0x20000
SUNI-622 Framer Register Values:
Master Rst and Ident/Load Meters Reg (#0x0): 0x10
Master Configuration Reg (#0x1): 0x1F
Master Interrupt Status Reg (#0x2): 0x00
PISO Interrupt Reg (#0x3): 0x04
Master Auto Alarm Reg (#0x4): 0x03
Master Auto Alarm Reg (#0x5): 0x07
Parallel Output Port Reg (#0x6): 0x02
BERM Line BIP Threshold LSB Reg (#0x74): 0x00
BERM Line BIP Threshold MSB Reg (#0x75): 0x00
The following is partial sample output from the show controllers command:
Router# execute-on slot 6 show controllers
lcpos_instance struct 60311B40
RX POS ASIC addr space 12000000
TX POS ASIC addr space 12000100
SUNI framer addr space 12000400
CRC32 enabled, HDLC enc, int clock
lcpos_instance struct 603142E0
RX POS ASIC addr space 12000000
TX POS ASIC addr space 12000100
SUNI framer addr space 12000600
CRC32 enabled, HDLC enc, int clock
The following is partial sample output from the show controllers pos framers command:
Router# execute-on slot 6 show controllers pos framers
Framer 0, addr=0x12000400:
master config 1F rrate sts3c trate sts3c fixptr
TACP control status 04 hcsadd
RSOP cntrl intr enable 00
TPOP path sig lbl (c2) 13
Framer 1, addr=0x12000600:
master config 1F rrate sts3c trate sts3c fixptr
TACP control status 04 hcsadd
RSOP cntrl intr enable 00
TPOP path sig lbl (c2) 13
Framer 2, addr=0x12000800:
master config 1F rrate sts3c trate sts3c fixptr
TACP control status 04 hcsadd
RSOP cntrl intr enable 00
TPOP path sig lbl (c2) 13
The following is partial sample output from the show controllers fia command:
Router# execute-on slot 7 show controllers fia
========= Line Card (Slot 7) =======
Fabric configuration: Full bandwidth redundant
Master Scheduler: Slot 17
redund fifo parity 0 redund overflow 0 cell drops 0
crc32 lkup parity 0 cell parity 0 crc32 0
-------- -------- -------- -------- --------
sca not pres 0 req error 0 uni fifo overflow 0
grant parity 0 multi req 0 uni fifo undrflow 0
cntrl parity 0 uni req 0 crc32 lkup parity 0
multi fifo 0 empty dst req 0 handshake error 0
Related Commands
Command
|
Description
|
clear controllers
|
Resets the T1 or E1 controller.
|
show controllers logging
To 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
vip slot-number
|
VIP slot number.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
11.2
|
This command was introduced.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
Usage Guidelines
This 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).
Examples
The following is sample output from the show controllers logging command:
Router# show controllers vip 1 logging
show logging from Slot 1:
Syslog logging:enabled (0 messages dropped, 1 messages rate-limited, 0 flushes, 0
overruns)
Console logging: disabled
Monitor logging: level debugging, 0 messages logged
Buffer logging: level debugging, 24 messages logged
Trap logging: level informational, 266 messages logged.
Logging to 209.165.202.129
Exception Logging size: 4096 bytes
Count and timestamp logging messages:disabled
smallest_local_pool_entries = 256, global particles = 5149
highest_local_visible_bandwidth = 155000
00:00:05:%SYS-5-RESTART:System restarted --
Table 64 describes the significant fields shown in the display.
Table 64 show controllers logging Field Descriptions
Field
|
Description
|
Syslog logging
|
Shows general state of system logging (enabled or disabled), and status of logged messages (number of messages dropped, rate-limited, or flushed).
|
Console logging
|
Logging to the console port. Shows "disabled" or, if enabled, the severity level limit and number of messages logged.
Enabled using the logging console command.
|
Monitor logging
|
Logging to the monitor (all TTY lines). Shows "disabled" or, if enabled, the severity level limit and number of messages logged.
Enabled using the logging monitor command.
|
Buffer logging
|
Logging to the standard syslog buffer. Shows "disabled" or, if enabled, the severity level limit and number of messages logged.
Enabled using the logging buffered command.
|
Trap logging
|
Logging to a remote host (syslog host). Shows "disabled" or, if enabled, the severity level limit and number of messages logged.
(The word "trap" means a trigger in the system software for sending error messages to a remote host.)
Enabled using the logging host command. The severity level limit is set using the logging trap command.
|
Related Commands
Command
|
Description
|
show logging
|
Displays the state of logging (syslog).
|
show controllers tech-support
To 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
vip slot-number
|
VIP slot number.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
11.2
|
This command was introduced.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
Usage Guidelines
Use 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
Command
|
Description
|
more system:running-config
|
Displays the running configuration.
|
show buffers
|
Displays statistics for the buffer pools on the network server.
|
show controllers
|
Displays information that is specific to the hardware.
|
show interfaces
|
Uses the show interfaces EXEC command to display ALC information.
|
show processes
|
Displays information about the active processes.
|
show processes memory
|
Displays memory used.
|
show stacks
|
Monitors the stack usage of processes and interrupt routines.
|
show tech-support
|
Displays general information about the router when reporting a problem.
|
show version
|
Displays the configuration of the system hardware, the software version, the names and sources of configuration files, and the boot images.
|
show debugging
To 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 Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC (#)
Command History
Release
|
Modification
|
11.1
|
This command was introduced.
|
12.3(7)T
|
The output of this command was enhanced to show TCP Explicit Congestion Notification (ECN) configuration.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
12.2(31)SB2
|
This command was integrated into Cisco IOS Release 12.2(31)SB2.
|
12.2SX
|
This command is supported in the Cisco IOS Release 12.2SX train. Support in a specific 12.2SX release of this train depends on your feature set, platform, and platform hardware.
|
12.4(20)T
|
The output of this command was enhanced to show the user-group debugging configuration.
|
Examples
The following is sample output from the show debugging command. In this example, the remote host is not configured or connected.
TCP Packet debugging is on
Router# telnet 10.1.25.234
00:02:48: 10.1.25.31:11001 <---> 10.1.25.234:23 out ECN-setup SYN
00:02:48: tcp0: O CLOSED 10.1.25.234:11001 10.1.25.31:23 seq 1922220018
OPTS 4 ECE CWR SYN WIN 4128
00:02:50: 10.1.25.31:11001 <---> 10.1.25.234:23 congestion window changes
00:02:50: cwnd from 1460 to 1460, ssthresh from 65535 to 2920
00:02:50: tcp0: R SYNSENT 10.1.25.234:11001 10.1.25.31:23 seq 1922220018
OPTS 4 ECE CWR SYN WIN 4128
00:02:54: 10.1.25.31:11001 <---> 10.1.25.234:23 congestion window changes
00:02:54: cwnd from 1460 to 1460, ssthresh from 2920 to 2920
00:02:54: tcp0: R SYNSENT 10.1.25.234:11001 10.1.25.31:23 seq 1922220018
OPTS 4 ECE CWR SYN WIN 4128
00:03:02: 10.1.25.31:11001 <---> 10.1.25.234:23 congestion window changes
00:03:02: cwnd from 1460 to 1460, ssthresh from 2920 to 2920
00:03:02: tcp0: R SYNSENT 10.1.25.234:11001 10.1.25.31:23 seq 1922220018
OPTS 4 ECE CWR SYN WIN 4128
00:03:18: 10.1.25.31:11001 <---> 10.1.25.234:23 SYN with ECN disabled
00:03:18: 10.1.25.31:11001 <---> 10.1.25.234:23 congestion window changes
00:03:18: cwnd from 1460 to 1460, ssthresh from 2920 to 2920
00:03:18: tcp0: O SYNSENT 10.1.25.234:11001 10.1.25.31:23 seq 1922220018
00:03:20: 10.1.25.31:11001 <---> 10.1.25.234:23 congestion window changes
00:03:20: cwnd from 1460 to 1460, ssthresh from 2920 to 2920
00:03:20: tcp0: R SYNSENT 10.1.25.234:11001 10.1.25.31:23 seq 1922220018
00:03:24: 10.1.25.31:11001 <---> 10.1.25.234:23 congestion window changes
00:03:24: cwnd from 1460 to 1460, ssthresh from 2920 to 2920
00:03:24: tcp0: R SYNSENT 10.1.25.234:11001 10.1.25.31:23 seq 1922220018
00:03:32: 10.1.25.31:11001 <---> 10.1.25.234:23 congestion window changes
00:03:32: cwnd from 1460 to 1460, ssthresh from 2920 to 2920
00:03:32: tcp0: R SYNSENT 10.1.25.234:11001 10.1.25.31:23 seq 1922220018
!Connection timed out; remote host not responding
The following is sample output from the show debugging command when user-group debugging is configured:
Usergroup Deletions debugging is on
Usergroup Additions debugging is on
Usergroup Database debugging is on
Usergroup API debugging is on
!
Table 65 describes the significant fields in the output.
Table 65 show debugging Field Descriptions
Field
|
Description
|
OPTS 4
|
Bytes of TCP expressed as a number. In this case, the bytes are 4.
|
ECE
|
Echo congestion experience.
|
CWR
|
Congestion window reduced.
|
SYN
|
Synchronize connections—Request to synchronize sequence numbers, used when a TCP connection is being opened.
|
WIN 4128
|
Advertised window size, in bytes. In this case, the bytes are 4128.
|
cwnd
|
Congestion window (cwnd)—Indicates that the window size has changed.
|
ssthresh
|
Slow-start threshold (ssthresh)—Variable used by TCP to determine whether or not to use slow-start or congestion avoidance.
|
usergroup
|
Statically defined usergroup to which source IP addresses are associated.
|
show declassify
To 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 Description
This command has no arguments or keywords.
Note
The show declassify command is supported on the Cisco 3200 series routers only.
Command Modes
Global configuration
Command History
Release
|
Modification
|
12.3(8)YD
|
This command was introduced.
|
12.4(2)T
|
This command was integrated into Cisco IOS Release 12.4(2)T.
|
Examples
The following example is sample output for the show declassify command:
Declassify facility: Enabled=Yes In Progress=No
Erase flash=Yes Erase nvram=Yes
Declassify Console and Aux Ports
Declassify Communications Processor Module
Declassify RAM, D-Cache, and I-Cache
Table 66 describes the significant fields shown in the display.
Table 66 show declassify Field Descriptions
Field
|
Description
|
Enabled
|
A "Yes" value indicates that zeroization is enabled.
A "No" value indicates that zeroization is disabled.
|
In Progress
|
A "Yes" value indicates that zeroization is currently in progress.
A "No" value indicates that zeroization is currently not in progress.
|
Erase flash
|
A "Yes" value indicates that erasure of Flash memory is enabled.
A "No" value indicates that the erasure of Flash memory is disabled.
|
Erase nvram
|
A "Yes" value indicates that the erasure of NVRAM is enabled.
A "No" value indicates that the erasure of NVRAM is disabled.
|
Obtain memory size
|
Obtain the main memory size in order to understand how much of the memory is to be scrubbed.
|
Shutdown Interfaces
|
Shut down any and all network interfaces.
|
Declassify Console and AUX Ports
|
Remove potentially sensitive information from console and AUX port FIFOs.
|
Erase flash
|
Erase Flash memory.
|
Declassify NVRAM
|
Erase NVRAM.
|
Declassify Communications Processor Module
|
Erase the memory in the Communications Processor Module (CPM).
|
Declassify RAM, D-Cache, and I-Cache
|
Scrub the main memory, erase the Data Cache (D-Cache), and erase the Instruction Cache (I-Cache).
|
Related Commands
Command
|
Description
|
service declassify
|
Invokes declassification.
|
show derived-config
To 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
interface type number
|
(Optional) Displays the derived configuration for a specific interface. If you use the interface keyword, you must specify the interface type and the interface number (for example, interface ethernet 0).
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.1
|
This command was introduced.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
Usage Guidelines
Configuration 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.
Examples
The 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.
Router# show running-config interface Serial0:23
Building configuration...
Current configuration :296 bytes
description PRI to ADTRAN (#4444150)
isdn switch-type primary-dms100
isdn incoming-voice modem
isdn calling-number 4444150
peer default ip address pool old_pool
Router# show running-config interface Dialer0
Building configuration...
Current configuration :257 bytes
peer default ip address pool new_pool
ppp authentication pap chap callin
Router# show derived-config interface Serial0:23
Building configuration...
Derived configuration :332 bytes
description PRI to ADTRAN (#4444150)
isdn switch-type primary-dms100
isdn incoming-voice modem
isdn calling-number 4444150
peer default ip address pool new_pool
ppp authentication pap chap callin
Router# show derived-config interface Dialer0
Building configuration...
Derived configuration :257 bytes
peer default ip address pool new_pool
ppp authentication pap chap callin
Related Commands
Command
|
Description
|
show running-config
|
Displays the contents of the currently running configuration file or the configuration for a specific interface.
|
show diagnostic cns
To 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
publish
|
Displays the subject with which the diagnostic results is published.
|
subscribe
|
Displays the subscribed subjects.
|
Defaults
This command has no default settings.
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
12.2(14)SX
|
Support for this command was introduced on the Supervisor Engine 720.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
Usage Guidelines
This 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.
Examples
This example shows how to display the subject with which the diagnostic results is published:
Router# show diagnostic cns publish
Subject: cisco.cns.device.diag_results
This example shows how to display the subscribed subject:
Router# show diagnostic cns subscribe
Subject: cisco.cns.device.diag_get_results
Related Commands
Command
|
Description
|
diagnostic cns
|
Configures the CNS diagnostics.
|
show diagnostic sanity
To display sanity check results, use the show diagnostic sanity command in privileged EXEC mode.
show diagnostic sanity
Syntax Description
This command has no arguments or keywords.
Defaults
Displays information for all the Gigabit Ethernet WAN interfaces in the Cisco 7600 series router.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.2(18)SXE
|
Support for this command was introduced on the Supervisor Engine 720.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.2(33)SRA.
|
Usage Guidelines
The 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
–