Table Of Contents
service slave-log
service tcp-keepalives-in
service tcp-keepalives-out
service tcp-small-servers
service telnet-zero-idle
service timestamps
service udp-small-servers
set (EEM)
set memory debug incremental starting-time
setup
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 bootvar
show buffers
show buffers leak
show buffers tune
show buffers usage
show c2600
show c7200
show calendar
show cdp
show cdp entry
show cdp interface
show cdp neighbors
show cdp traffic
show clock
show cls
show cns config connections
show cns config outstanding
show cns config stats
show cns config status
show cns event connections
show cns event gateway
show cns event stats
show cns event status
show cns event subject
show cns image connections
show cns image inventory
show cns image status
show <command> append
show <command> begin
show <command> exclude
show <command> include
show <command> redirect
show <command> section
show <command> tee
service slave-log
To allow slave Versatile Interface Processor (VIP) cards to log important error messages to the console, use the service slave-log command in global configuration mode. To disable slave logging, use the no form of this command.
service slave-log
no service slave-log
Syntax Description
This command has no arguments or keywords.
Defaults
This command is enabled by default.
Command Modes
Global configuration
Command History
Release
|
Modification
|
11.1
|
This command was introduced.
|
Usage Guidelines
This command allows slave slots to log error messages of level 2 or higher (critical, alerts, and emergencies).
Examples
In the following example, the router is configured to log important messages from the slave cards to the console:
Router(config)# service slave-log
The following is sample output generated when this command is enabled:
%IPC-5-SLAVELOG: VIP-SLOT2:
IPC-2-NOMEM: No memory available for IPC system initialization
The first line indicates which slot sent the message. The second line contains the error message.
service tcp-keepalives-in
To generate keepalive packets on idle incoming network connections (initiated by the remote host), use the service tcp-keepalives-in command in global configuration mode. To disable the keepalives, use the no form of this command.
service tcp-keepalives-in
no service tcp-keepalives-in
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Global configuration
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
Examples
In the following example, keepalives on incoming TCP connections are generated:
Router(config)# service tcp-keepalives-in
Related Commands
Command
|
Description
|
service tcp-keepalives-out
|
Generates keepalive packets on idle outgoing network connections (initiated by a user).
|
service tcp-keepalives-out
To generate keepalive packets on idle outgoing network connections (initiated by a user), use the service tcp-keepalives-out command in global configuration mode. To disable the keepalives, use the no form of this command.
service tcp-keepalives-out
no service tcp-keepalives-out
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Global configuration
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
Examples
In the following example, keepalives on outgoing TCP connections are generated:
Router(config)# service tcp-keepalives-out
Related Commands
Command
|
Description
|
service tcp-keepalives-in
|
Generates keepalive packets on idle incoming network connections (initiated by the remote host).
|
service tcp-small-servers
To access minor TCP/IP services available from hosts on the network, use the service tcp-small-servers command in global configuration mode. To disable these services, use the no form of the command.
service tcp-small-servers
no service tcp-small-servers
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Global configuration
Command History
Release
|
Modification
|
11.1
|
This command was introduced.
|
Usage Guidelines
By default, the TCP servers for Echo, Discard, Chargen, and Daytime services are disabled.
When the minor TCP/IP servers are disabled, access to the Echo, Discard, Chargen, and Daytime ports cause the Cisco IOS software to send a TCP RESET packet to the sender and discard the original incoming packet.
Examples
The following example enables minor TCP/ IP services available from the network:
Router(config)# service tcp-small-servers
service telnet-zero-idle
To set the TCP window to zero (0) when the Telnet connection is idle, use the service telnet-zero-idle command in global configuration mode. To disable this service, use the no form of this command.
service telnet-zero-idle
no service telnet-zero-idle
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Global configuration
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
Usage Guidelines
Normally, data sent to noncurrent Telnet connections is accepted and discarded. When the service telnet-zero-idle command is enabled, if a session is suspended (that is, some other connection is made active or the EXEC is sitting in command mode), the TCP window is set to zero. This action prevents the remote host from sending any more data until the connection is resumed. Use this command when it is important that all messages sent by the host be seen by the users and the users are likely to use multiple sessions.
Do not use this command if your host will eventually time out and log out a TCP user whose window is zero.
Examples
The following example sets the TCP window to zero when the Telnet connection is idle:
Router(config)# service telnet-zero-idle
Related Commands
Command
|
Description
|
resume
|
Switches to another open Telnet, rlogin, LAT, or PAD session.
|
service timestamps
To configure the system to time-stamp debugging or system logging messages, use one of the service timestamps commands in global configuration mode. To disable this service, use the no form of this command.
service timestamps [debug | log] [ uptime | datetime [msec] [localtime] [show-timezone] [year] ]
no service timestamps [debug | log]
Syntax Description
debug
|
Indicates that the timestamp should be applied to debugging messages.
|
log
|
Indicates that the timestamp should be applied to system logging messages.
|
uptime
|
Time stamp with the time since the system was rebooted. The time stamp format for uptime is HHHH:MM:SS.
|
datetime
|
Time stamp with the date and time. The time stamp format for datetime is MMM DD HH:MM:SS.
|
msec
|
(Optional) Include milliseconds in the time stamp.
|
localtime
|
(Optional) Time stamp relative to the local time zone.
|
year
|
Include the year in the datetime format.
|
show-timezone
|
(Optional) Include the time zone name in the time stamp.
|
Defaults
No time-stamping.
If the service timestamps command is specified with no arguments or keywords, the default is service timestamps debug uptime.
The default for the service timestamps type datetime command is to format the time in Coordinated Universal Time (UTC), with no milliseconds and no time zone name.
The no service timestamps command by itself disables time stamps for both debug and log messages.
To set the local timezone, use the clock timezone zone hours-offset command in global configuration mode.
Command Modes
Global configuration
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
12.2(15)T
|
The year keyword was added.
|
Usage Guidelines
Time stamps can be added to either debugging or logging messages independently. The uptime form of the command adds time stamps in the format HHHH:MM:SS, indicating the time since the system was rebooted. The datetime form of the command adds time stamps in the format MMM DD HH:MM:SS, indicating the date and time according to the system clock.
The timestamp will be preceeded by an asterisk or period if the time is potentially inaccurate. Table 61 describes the symbols that proceed the timestamp.
Table 61 Timestamping Symbols for syslog Messages
Symbol
|
Description
|
Example
|
(blank)
|
Time is authoritative: the software clock is in sync or has just been set manually
|
15:29:03.158 UTC Tue Feb 25 2003:
|
*
|
Time is not authoritative: the software clock has not been set, or is not in sync with configured Network Time Protocol (NTP) servers.
|
*15:29:03.158 UTC Tue Feb 25 2003:
|
.
|
Time is authoritative, but the Network Time Protocol (NTP) is not synchronized: the software clock was in sync, but has since lost contact with all configured NTP servers.
|
.15:29:03.158 UTC Tue Feb 25 2003:
|
Examples
In the following example, the user enables time stamps on debugging messages, showing the time since reboot:
service timestamps debug uptime
In the following example, the user enables time stamps on logging messages, showing the current time and date relative to the local time zone, with the time zone name included:
! The following line shows timestamp with uptime.
1w0d: %SYS-5-CONFIG_I: Configured from console by console
Router(config)# service timestamps log datetime localtime show-timezone
! The following line shows timestamp with datetime.
.Mar 22 23:13:25 UTC: %SYS-5-CONFIG_I: Configured from console by console
The following example shows the change from UTC to local time:
.Mar 22 23:23:10 UTC: %SYS-5-CONFIG_I: Configured from console by console
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# clock timezone PST -8
.Mar 22 15:28:02 PST: %SYS-5-CONFIG_I: Configured from console by console
Related Commands
Command
|
Description
|
clock set
|
Manually sets the system clock.
|
ntp
|
Controls access to the system's NTP services.
|
service sequence-numbers
|
Stamps system logging messages with a sequence number.
|
service udp-small-servers
To access minor User Datagram Protocol (UDP) services available from hosts on the network, use the service udp-small-servers command in global configuration mode. To disable these services, use the no form of this command.
service udp-small-servers
no service udp-small-servers
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Global configuration
Command History
Release
|
Modification
|
11.2
|
This command was introduced.
|
Usage Guidelines
By default the UPD servers for Echo, Discard, and Chargen services are disabled.
When the servers are disabled, access to Echo, Discard, and Chargen ports causes the Cisco IOS software to send an "ICMP port unreachable" message to the sender and discard the original incoming packet.
Examples
In the following example, the UDP server (UDP services) is enabled:
Router(config)# service udp-small-servers
set (EEM)
To set the value of a local Embedded Event Manager (EEM) applet variable, use the set command in applet configuration mode. To remove the value of an EEM applet variable, use the no form of this command.
set label _exit_status exit-value
no set label _exit_status exit-value
Syntax Description
label
|
Unique identifier that can be any string value. Actions are sorted and run in ascending alphanumeric key sequence using the label as the sort key. If the string contains embedded blanks, enclose it in double quotation marks.
|
_exit_status
|
Specifies the EEM applet variable name. Currently only the _exit_status variable is supported.
• exit-value—Integer value that represents the exit status for the applet. Zero represents an exit status of success, and a nonzero value represents an exit status of failure.
|
Defaults
No EEM applet variable values are set.
Command Modes
Applet configuration
Command History
Release
|
Modification
|
12.3(14)T
|
This command was introduced.
|
Usage Guidelines
In EEM applet configuration mode, three types of configuration statements are supported. The event commands are used to specify the event criteria to trigger the applet to run, the action commands are used to specify an action to perform when the EEM applet is triggered, and the set command is used to set the value of an EEM applet variable. Currently only the _exit_status variable is supported for the set command.
Examples
The following example shows how to set the _exit_status variable to represent a success status after an event has occurred three times and an action has been performed.
Router(config)# event manager applet cli-match
Router(config-applet)# event cli pattern {.*interface loopback*} sync yes occurs 3
Router(config-applet)# action 1.0 cli command "no shutdown"
Router(config-applet)# set 1.0 _exit_status 0
Related Commands
Command
|
Description
|
event manager applet
|
Registers an event applet with the Embedded Event Manager and enters applet configuration mode.
|
set memory debug incremental starting-time
To set the current time as the starting time for incremental analysis, use the set memory debug incremental starting-time command in privileged EXEC mode.
set memory debug incremental starting-time [none]
Syntax Description
none
|
(Optional) Resets the defined start time for incremental analysis.
|
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.3(8)T1
|
This command was introduced.
|
12.2(25)S
|
This command was integrated into Cisco IOS Release 12.2(25)S.
|
Usage Guidelines
For incremental analysis, a starting point can be defined by using the set memory debug incremental starting-time command. When a starting time is set, only memory allocated after that starting time will be considered for reporting as leaks.
Examples
The following example shows the command used to set the starting time for incremental analysis to the time when the command was issued:
Router# set memory debug incremental starting-time
Related Commands
Command
|
Description
|
show memory debug incremental allocation
|
Displays all memory blocks that were allocated after the issue of the set memory debug incremental starting-time command.
|
show memory debug incremental leaks
|
Displays only memory that was leaked after the issue of the set memory debug incremental starting-time command.
|
show memory debug incremental leaks lowmem
|
Forces incremental memory leak detection to work in low memory mode. Displays only memory that was leaked after the issue of the set memory debug incremental starting-time command.
|
show memory debug incremental status
|
Displays if the starting point of incremental analysis has been defined and the time elapsed since then.
|
show memory debug leaks
|
Displays detected memory leaks.
|
setup
To enter Setup mode, use the setup command in privileged EXEC mode.
setup
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
11.1
|
This command was introduced.
|
Usage Guidelines
Setup mode gives you the option of configuring your system without using the Cisco IOS Command Line Interface (CLI). For some tasks, you may find it easier to use Setup than to enter Cisco IOS commands individually. For example, you might want to use Setup to add a protocol suite, to make major addressing scheme changes, or to configure a newly installed interface. Although you can use the CLI to make these changes, Setup provides you with a high-level view of the configuration and guides you through the configuration process.
If you are not familiar with Cisco products and the CLI, Setup is a particularly valuable tool because it prompts you for the specific information required to configure your system.
Note
If you use the Setup mode to modify a configuration because you have added or modified the hardware, be sure to verify the physical connections using the show version EXEC command. Also, verify the logical port assignments using the show running-config EXEC command to ensure that you configure the correct port. Refer to the hardware documentation for your platform for more information on physical and logical port assignments.
Before using the Setup mode, you should have the following information so that you can configure the system properly:
•
Which interfaces you want to configure
•
Which routing protocols you wish to enable
•
Whether the router is to perform bridging
•
Network addresses for the protocols being configured
•
Password strategy for your environment
When you enter the setup EXEC command after first-time startup, an interactive dialog called the System Configuration Dialog appears on the system console screen. The System Configuration Dialog guides you through the configuration process. It prompts you first for global parameters and then for interface parameters. The values shown in brackets next to each prompt reflect either the default settings or the last configured setting.
The prompts and the order in which they appear on the screen vary depending on the platform and the interfaces installed in the device.
You must progress through the System Configuration Dialog until you come to the item that you intend to change. To accept default settings for items that you do not want to change, press the Return or Enter key. The default choice is indicated by square brackets (for example, [yes]) before the prompt colon (:).
To exit Setup mode and return to privileged EXEC mode without making changes and without progressing through the entire System Configuration Dialog, press Ctrl-C.
The facility also provides help text for each prompt. To access help text, press the question mark (?) key at a prompt.
When you complete your changes, the system will automatically display the configuration file that was created during the Setup session. It also asks you if you want to use this configuration. If you answer Yes, the configuration is saved to NVRAM as the startup configuration file. If you answer No, the configuration is not saved and the process begins again. There is no default for this prompt; you must answer either Yes or No.
Examples
The following example displays the setup command facility to configure serial interface 0 and to add ARAP and IP/IPX PPP support on the asynchronous interfaces:
--- System Configuration Dialog ---
At any point you may enter a question mark '?' for help.
Use ctrl-c to abort configuration dialog at any prompt.
Default settings are in square brackets '[]'.
Continue with configuration dialog? [yes]:
First, would you like to see the current interface summary? [yes]:
Interface IP-Address OK? Method Status Protocol
Ethernet0 172.16.72.2 YES manual up up
Serial0 unassigned YES not set administratively down down
Serial1 172.16.72.2 YES not set up up
Configuring global parameters:
Enter host name [Router]:
The enable secret is a one-way cryptographic secret used
instead of the enable password when it exists.
Enter enable secret [<Use current secret>]:
The enable password is used when there is no enable secret
and when using older software and some boot images.
Enter enable password [ww]:
Enter virtual terminal password [ww]:
Configure SNMP Network Management? [yes]:
Community string [public]:
Configure AppleTalk? [yes]:
Multizone networks? [no]: yes
Configure IGRP routing? [yes]:
Your IGRP autonomous system number [15]:
Configure Async lines? [yes]:
Async line speed [9600]: 57600
Configure for HW flow control? [yes]:
Configure for modems? [yes/no]: yes
Configure for default chat script? [yes]: no
Configure for Dial-in IP SLIP/PPP access? [no]: yes
Configure for Dynamic IP addresses? [yes]: no
Configure Default IP addresses? [no]: yes
Configure for TCP Header Compression? [yes]: no
Configure for routing updates on async links? [no]:
Configure for Async IPX? [yes]:
Configure for Appletalk Remote Access? [yes]:
AppleTalk Network for ARAP clients [1]: 20
Zone name for ARAP clients [ARA Dialins]:
Configuring interface parameters:
Configuring interface Ethernet0:
Is this interface in use? [yes]:
Configure IP on this interface? [yes]:
IP address for this interface [172.16.72.2]:
Number of bits in subnet field [8]:
Class B network is 172.16.0.0, 8 subnet bits; mask is /24
Configure AppleTalk on this interface? [yes]:
Extended AppleTalk network? [yes]:
AppleTalk starting cable range [1]:
AppleTalk ending cable range [1]:
AppleTalk zone name [Sales]:
AppleTalk additional zone name:
Configure IPX on this interface? [yes]:
Configuring interface Serial0:
Is this interface in use? [no]: yes
Configure IP on this interface? [no]: yes
Configure IP unnumbered on this interface? [no]: yes
Assign to which interface [Ethernet0]:
Configure AppleTalk on this interface? [no]: yes
Extended AppleTalk network? [yes]:
AppleTalk starting cable range [2]: 3
AppleTalk ending cable range [3]: 3
AppleTalk zone name [myzone]: ZZ Serial
AppleTalk additional zone name:
Configure IPX on this interface? [no]: yes
IPX network number [2]: 3
Configuring interface Serial1:
Is this interface in use? [yes]:
Configure IP on this interface? [yes]:
Configure IP unnumbered on this interface? [yes]:
Assign to which interface [Ethernet0]:
Configure AppleTalk on this interface? [yes]:
Extended AppleTalk network? [yes]:
AppleTalk starting cable range [2]:
AppleTalk ending cable range [2]:
AppleTalk zone name [ZZ Serial]:
AppleTalk additional zone name:
Configure IPX on this interface? [yes]:
Configuring interface Async1:
Default client IP address for this interface [none]: 172.16.72.4
Configuring interface Async2:
Default client IP address for this interface [172.16.72.5]:
Configuring interface Async3:
Default client IP address for this interface [172.16.72.6]:
Configuring interface Async4:
Default client IP address for this interface [172.16.72.7]:
Configuring interface Async5:
Default client IP address for this interface [172.16.72.8]:
Configuring interface Async6:
Default client IP address for this interface [172.16.72.9]:
Configuring interface Async7:
Default client IP address for this interface [172.16.72.10]:
Configuring interface Async8:
Default client IP address for this interface [172.16.72.11]:
Configuring interface Async9:
Default client IP address for this interface [172.16.72.12]:
Configuring interface Async10:
Default client IP address for this interface [172.16.72.13]:
Configuring interface Async11:
Default client IP address for this interface [172.16.72.14]:
Configuring interface Async12:
Default client IP address for this interface [172.16.72.15]:
Configuring interface Async13:
Default client IP address for this interface [172.16.72.16]:
Configuring interface Async14:
Default client IP address for this interface [172.16.72.17]:
Configuring interface Async15:
Default client IP address for this interface [172.16.72.18]:
Configuring interface Async16:
Default client IP address for this interface [172.16.72.19]:
The following configuration command script was created:
enable secret 5 $1$krIg$emfYm/1OwHVspDuS8Gy0K1
snmp-server community public
arap network 20 ARA Dialins
! Turn off IPX to prevent network conflicts.
ip address 172.16.72.2 255.255.255.0
appletalk cable-range 1-1 1.204
appletalk cable-range 3-3
appletalk cable-range 2-2 2.2
peer default ip address 172.16.72.4
peer default ip address 172.16.72.5
peer default ip address 172.16.72.6
peer default ip address 172.16.72.7
peer default ip address 172.16.72.8
peer default ip address 172.16.72.9
peer default ip address 172.16.72.10
peer default ip address 172.16.72.11
peer default ip address 172.16.72.12
peer default ip address 172.16.72.13
peer default ip address 172.16.72.14
peer default ip address 172.16.72.15
peer default ip address 172.16.72.16
peer default ip address 172.16.72.17
peer default ip address 172.16.72.18
peer default ip address 172.16.72.19
Use this configuration? [yes/no]: yes
Building configuration...
Use the enabled mode 'configure' command to modify this configuration.
Related Commands
Command
|
Description
|
erase nvram:
|
Erases a file system.
|
show running-config
|
Displays the running configuration file. Command alias for the more system:running-config command.
|
show startup-config
|
Displays the startup configuration file. Command alias for the more system:startup-config command.
|
show version
|
Displays the configuration of the system hardware, the software version, the names and sources of configuration files, and the boot images.
|
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 availability of Flash file system keywords will vary by platform. Valid flash file system keywords include:
• 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.
|
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 62 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 62 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 63 describes the significant fields shown in the displays.
Table 63 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 63 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.
|
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. For a list of command modes, refer to the "Cisco IOS Command Modes" appendix in the Cisco IOS Configuration Fundamentals Configuration Guide.
Examples
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.
|
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 64 describes the significant fields shown in the display.
Table 64 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 65 describes the significant fields shown in the display.
Table 65 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.
|
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
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 [file1 [file2]]
Syntax Description
file1
|
(Optional) The filename of the first configuration file.
|
file2
|
(Optional) The filename of the second configuration file.
|
Defaults
If the file1 and file2 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 file1 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.
|
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 file1 but not in file2.
•
A plus symbol (+) indicates that the configuration line exists in file2 but not in file1.
•
An exclamation point (!) with descriptive comments is used to identify order-sensitive configuration lines whose location is different in file1 than in file2.
Examples
In this example, a diff operation is performed on the running and startup configuration files. Table 66 shows the configuration files used for this example.
Table 66 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 7.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 4.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 5.5.5.5
ip classless
access-list 110 deny ip any host 1.1.1.1
access-list 110 deny ip any host 1.1.1.2
access-list 110 deny ip any host 1.1.1.3
snmp-server community private RW
|
The following sample output is from the show archive config differences command. This sample output displays the results of the diff operation performed on the configuration files in Table 66.
Router# show archive config differences running-config startup-config
+ip subnet-zero
+ip name-server 4.4.4.4
+voice dnis-map 1
+dnis 111
interface Ethernet1/0
+no ip address
+shutdown
+ip default-gateway 5.5.5.5
+ip classless
+access-list 110 deny ip any host 1.1.1.1
+access-list 110 deny ip any host 1.1.1.2
+access-list 110 deny ip any host 1.1.1.3
+snmp-server community private RW
-no ip subnet-zero
interface Ethernet1/0
-ip address 7.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.
|
Defaults
No default behavior or values.
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.
|
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 67 shows the configuration files used for this example.
Table 67 Configuration Files Used for the Incremental Diff Operation Example
Startup Configuration File
|
Running Configuration File
|
ip subnet-zero
ip cef
ip name-server 4.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 5.5.5.5
ip classless
access-list 110 deny ip any host 1.1.1.1
access-list 110 deny ip any host 1.1.1.2
access-list 110 deny ip any host 1.1.1.3
snmp-server community private RW
|
no ip subnet-zero
ip cef
interface Ethernet1/0
ip address 7.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 sample output is 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 67.
Router# show archive config incremental-diffs nvram:startup-config
ip subnet-zero
ip name-server 4.4.4.4
voice dnis-map 1
dnis 111
interface Ethernet1/0
no ip address
shutdown
ip default-gateway 5.5.5.5
ip classless
access-list 110 deny ip any host 1.1.1.1
access-list 110 deny ip any host 1.1.1.2
access-list 110 deny ip any host 1.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 | number [end-number] | user username [session number] number
[end-number] | statistics} [provisioning]
Syntax Description
all
|
Specifies that all configuration log entries will be displayed.
|
number [end-number]
|
Specifies a log entry to be displayed 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 number and end-number arguments will be displayed. Valid values for the number and end-number argument range from 1 to 2147483647.
|
user username
|
Specifies that log entries attributed to a particular user will be displayed.
|
session number
|
(Optional) Specifies that log entries attributed to a particular session will be displayed. Valid values for the session-number argument range from 1 to 1000.
|
statistics
|
Specifies that memory usage information for the configuration log will be displayed.
|
provisioning
|
(Optional) Specifies that the configuration log file information will be displayed as it would appear in a configuration file, rather than in tabular 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.
|
Usage Guidelines
If you do not specify the all keyword, you must specify a record number with the number argument. You can optionally specify an end record number with the end-number argument to display a range of records. If you specify a record number that does not exist with the end-number argument, all records after the starting record number with a record number lower than that specified with the end-number argument will be 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 provision 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 68 describes the fields shown in the display.
Table 68 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, this display includes the commands used to change configuration modes, which 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.
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.
|
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 69 describes the significant fields shown in the display.
Table 69 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 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 privileged EXEC mode.
show bootvar
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
11.3 AA
|
This command was introduced.
|
Usage Guidelines
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 RSP cards (Dual RSPs), this command also shows you the variable settings for both the master and slave RSP card.
Examples
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 the sample output, the BOOT variable contains a null string. That is, a list of bootable images is not 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-config 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 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
Related Commands
Command
|
Description
|
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.
|
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, use the show buffers command in user EXEC or privileged EXEC mode.
show buffers [{address hex-address | failures | pool pool-name | {all | assigned | free | old |
input-interface interface-type interface-number} [pool pool-name]} [dump | header |
packet]]
Syntax Description
address hex-address
|
(Optional) Displays buffers at a specified address. Specify address in hexadecimal notation.
|
failures
|
(Optional) Displays buffer allocation failures.
|
pool pool-name
|
(Optional) Displays buffers in a specified buffer pool.
|
all
|
(Optional) Displays all buffers.
|
assigned
|
(Optional) Displays the buffers in use.
|
free
|
(Optional) Displays the buffers available for use.
|
old
|
(Optional) Displays buffers older than one minute.
|
input-interface interface-type interface-number
|
(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.
|
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 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.
|
Usage Guidelines
The peak field in the output of the show buffers command shows the maximum number of buffers created (highest total) and the time when that peak occurred relative to when you issued the show buffers command. Formats include weeks, days, hours, minutes, and seconds. Not all systems report a peak value, which means this field may not display in output.
Examples
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 70 describes the significant fields shown in the display.
Table 70 show buffers 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.
|
show buffers leak
To display the details of all the buffers that are older than one minute in the system, use the show buffers leak command in user EXEC or privileged EXEC mode.
show buffers leak [resource user]
Syntax Description
resource user
|
(Optional) Displays the resource user information to which the leaked buffers belong to.
|
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
12.3(14)T
|
This command was introduced.
|
Examples
The following is sample output from the show buffers leak command:
Router# show buffers leak
Header DataArea Pool Size Link Enc Flags Input Output User
6488F464 E000084 Small 74 0 0 10 None None EEM ED Sy
6488FB5C E000304 Small 74 0 0 10 None None EEM ED Sy
648905D0 E0006C4 Small 61 0 0 0 None None EEM ED Sy
648913C0 E000BC4 Small 74 0 0 10 None None EEM ED Sy
6489173C E000D04 Small 74 0 0 10 None None EEM ED Sy
648921B0 E0010C4 Small 60 0 0 0 None None Init
6489252C E001204 Small 103 0 0 10 None None EEM ED Sy
64892C24 E001484 Small 74 0 0 10 None None EEM ED Sy
64892FA0 E0015C4 Small 74 0 0 10 None None EEM ED Sy
64893A14 E001984 Small 74 0 0 10 None None EEM ED Sy
64893D90 E001AC4 Small 61 0 0 0 None None EEM ED Sy
64894804 E001E84 Small 61 0 0 0 None None EEM ED Sy
6517CB64 E32F944 Small 74 0 0 10 None None EEM ED Sy
6517D25C E176D44 Small 74 0 0 10 None None EEM ED Sy
6517D5D8 E176E84 Small 74 0 0 10 None None EEM ED Sy
6517D954 E209A84 Small 74 0 0 10 None None EEM ED Sy
6517E744 E209D04 Small 61 0 0 0 None None EEM ED Sy
6517EE3C E29CBC4 Small 61 0 0 0 None None EEM ED Sy
65180324 E177844 Small 74 0 0 10 None None EEM ED Sy
65180D98 E177C04 Small 61 0 0 0 None None EEM ED Sy
65E1F3A0 E4431A4 Small 102 0 0 0 None None EEM ED Sy
64895278 E002644 Middl 191 0 0 10 None None EEM ED Sy
64895CEC E003004 Middl 173 0 0 10 None None EEM ED Sy
64896068 E003344 Middl 176 0 0 10 None None EEM ED Sy
648963E4 E003684 Middl 191 0 0 10 None None EEM ED Sy
64896E58 E004044 Middl 109 0 0 10 None None EEM ED Sy
64897C48 E004D44 Middl 194 0 0 10 None None EEM ED Sy
65181F04 E330844 Middl 173 0 0 10 None None EEM ED Sy
65183070 E3C3644 Middl 105 0 0 10 None None EEM ED Sy
65DF9558 E4746E4 Middl 107 0 0 0 None None EEM ED Sy
65DFA6C4 E475724 Middl 116 0 0 0 None None EEM ED Sy
65DFADBC E475DA4 Middl 115 0 0 0 None None EEM ED Sy
65DFC620 E477464 Middl 110 0 0 0 None None EEM ED Sy
64C64AE0 0 FS He 0 0 3 0 None None Init
64C64E5C 0 FS He 0 0 3 0 None None Init
64C651D8 0 FS He 0 0 3 0 None None Init
64C65554 0 FS He 0 0 0 0 None None Init
64C658D0 0 FS He 0 0 0 0 None None Init
64C65C4C 0 FS He 0 0 0 0 None None Init
64C65FC8 0 FS He 0 0 0 0 None None Init
64C66344 0 FS He 0 0 0 0 None None Init
64D6164C 0 FS He 0 0 0 0 None None Init
64EB9D10 0 FS He 0 0 0 0 None None Init
6523EE14 0 FS He 0 0 0 0 None None Init
65413648 0 FS He 0 0 0 0 None None Init
The following is sample output from the show buffers leak resource user command:
Router# show buffers leak resource user
Resource User: EEM ED Syslog count: 32
Resource User: Init count: 2
Resource User: *Dead* count: 2
Resource User: IPC Seat Manag count: 11
Resource User: XDR mcast count: 2
Table 71 describes the significant fields shown in the display.
Table 71 show buffers leak Field Descriptions
Field
|
Description
|
Header
|
Buffer header.
|
DataArea
|
The area where the data is available.
|
Pool
|
The different buffer pools. It can be: small, middle, big, very big, large, or huge buffers.
|
Size
|
Size of the buffer pool. For example, small buffers are less than or equal to 104 bytes long. Middle buffers are in the range of 105 to 600 bytes long.
|
Flags
|
Flags of a packet. The flag indicates whether a particular packet is an incoming packet or is generated by the router.
|
User
|
RU name.
|
Related Commands
Command
|
Description
|
buffer public
|
Enters the buffer owner configuration mode and sets thresholds for buffer usage.
|
buffer tune automatic
|
Enables automatic buffer tuning.
|
show buffers tune
To display the details of automatic tuning of buffers, use the show buffers tune command in user EXEC or privileged EXEC mode.
show buffers tune
Syntax Description
This command has no arguments or keywords.
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
12.3(14)T
|
This command was introduced.
|
Examples
The following is sample output from the show buffers tune command:
Router# show buffers tune
Tuning happened for the pool Small
Tuning happened at 20:47:25
permanent:50 minfree:20 maxfree:150
permanet:61 minfree:15 maxfree:76
Tuning happened for the pool Middle
Tuning happened at 20:47:25
permanent:25 minfree:10 maxfree:150
permanet:36 minfree:9 maxfree:45
Table 72 describes the significant fields shown in the display.
Table 72 show buffers tune Field Descriptions
Field
|
Description
|
Oldvalues
|
The minimum and maximum free buffers before automatic tuning was enabled.
|
Newvalues
|
The minimum and maximum free buffers after automatic tuning was enabled.
|
Related Commands
Command
|
Description
|
buffer tune automatic
|
Enables automatic tuning of buffers.
|
show buffers usage
To display the details of the buffer usage pattern in a specified buffer pool, use the show buffers usage command in user EXEC or privileged EXEC mode.
show buffers usage [pool pool-name]
Syntax Description
pool pool-name
|
(Optional) Displays the details of the specified pool. If not specified, displays the details of all the pools.
|
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
12.3(14)T
|
This command was introduced.
|
Examples
The following is sample output from the show buffers usage command:
Router# show buffers usage
Statistics for the Small pool
Caller pc : 0x626BA9E0 count: 20
Resource User: EEM ED Sys count: 20
Caller pc : 0x60C71F8C count: 1
Resource User: Init count: 1
Number of Buffers used by packets generated by system: 62
Number of Buffers used by incoming packets: 0
Statistics for the Middle pool
Caller pc : 0x626BA9E0 count: 12
Resource User: EEM ED Sys count: 12
Number of Buffers used by packets generated by system: 41
Number of Buffers used by incoming packets: 0
Statistics for the Big pool
Number of Buffers used by packets generated by system: 50
Number of Buffers used by incoming packets: 0
Statistics for the VeryBig pool
Number of Buffers used by packets generated by system: 10
Number of Buffers used by incoming packets: 0
Statistics for the Large pool
Number of Buffers used by packets generated by system: 0
Number of Buffers used by incoming packets: 0
Statistics for the Huge pool
Number of Buffers used by packets generated by system: 0
Number of Buffers used by incoming packets: 0
Statistics for the IPC pool
Number of Buffers used by packets generated by system: 2
Number of Buffers used by incoming packets: 0
Statistics for the Header pool
Number of Buffers used by packets generated by system: 511
Number of Buffers used by incoming packets: 0
Statistics for the FS Header pool
Caller pc : 0x608F68FC count: 9
Resource User: Init count: 12
Caller pc : 0x61A21D3C count: 1
Caller pc : 0x60643FF8 count: 1
Caller pc : 0x61C526C4 count: 1
Number of Buffers used by packets generated by system: 28
Number of Buffers used by incoming packets: 0
The following is sample output from the show buffers usage pool small command:
Router# show buffers usage pool small
Statistics for the Small pool
Caller pc : 0x626BA9E0 count: 20
Resource User: EEM ED Sys count: 20
Caller pc : 0x60C71F8C count: 1
Resource User: Init count: 1
Number of Buffers used by packets generated by system: 62
Number of Buffers used by incoming packets: 0
Related Commands
Command
|
Description
|
buffer public
|
Enters the buffer owner configuration mode and sets thresholds for buffer usage.
|
show buffers leak
|
Displays details of the buffers that leaked.
|
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.
|
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 73 describes the significant fields shown in the display.
Table 73 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.
|
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 calendar
To display the current time and date setting for the hardware clock, use the show calendar command in EXEC mode:
show calendar
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
Usage Guidelines
Some platforms have a hardware clock (calendar) which is separate from the software clock. The hardware clock is battery operated, and runs continuously, even if the router is powered off or rebooted.
You can compare the time and date shown with this command with the time and date listed via the show clock EXEC command to verify that the hardware clock and software clock are synchronized with each other. The time displayed is relative to the configured time zone.
Examples
In the following sample display, the hardware clock indicates the time stamp of 12:13:44 p.m. on Friday, July 19, 1996:
12:13:44 PST Fri Jul 19 1996
Related Commands
Command
|
Description
|
show clock
|
Displays the time and date from the system software clock.
|
show cdp
To display global Cisco Discovery Protocol (CDP) information, including timer and hold-time information, use the show cdp command in privileged EXEC mode.
show cdp
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
10.3
|
This command was introduced.
|
12.0(3)T
|
The output of this command was modified to include CDP Version 2 information.
|
Examples
The following example shows that the current router is sending CDP advertisements every 1 minute (the default setting for the cdp timer global configuration command). Also shown is that the current router directs its neighbors to hold its CDP advertisements for 3 minutes (the default for the cdp holdtime global configuration command), and that the router is enabled to send CDP Version 2 advertisements:
Sending CDP packets every 60 seconds
Sending a holdtime value of 180 seconds
Sending CDPv2 advertisements is enabled
Table 74 describes the significant fields shown in the display.
Table 74 show cdp Field Descriptions
Field
|
Definition
|
Sending CDP packets every XX seconds
|
The interval (in seconds) between transmissions of CDP advertisements. This field is controlled by the cdp timer command.
|
Sending a holdtime value of XX seconds
|
The amount of time (in seconds) the device directs the neighbor to hold a CDP advertisement before discarding it. This field is controlled by the cdp holdtime command.
|
Sending CDPv2 advertisements is XX
|
The state of whether CDP Version-2 type advertisements are enabled to be sent. Possible states are enabled or disabled. This field is controlled by the cdp advertise v2 global configuration command.
|
Related Commands
Command
|
Description
|
cdp advertise-v2
|
Enables CDP Version 2 advertising functionality on a device.
|
cdp holdtime
|
Specifies the amount of time the receiving device should hold a CDP packet from your router before discarding it.
|
cdp timer
|
Specifies how often the Cisco IOS software sends CDP updates.
|
show cdp entry
|
Displays information about a specific neighbor device listed in the CDP table.
|
show cdp interface
|
Displays information about the interfaces on which CDP is enabled.
|
show cdp neighbors
|
Displays detailed information about neighboring devices discovered using CDP.
|
show cdp traffic
|
Displays information about traffic between devices gathered using CDP.
|
show cdp entry
To display information about a specific neighboring device discovered using Cisco Discovery Protocol (CDP), use the show cdp entry command in privileged EXEC mode.
show cdp entry {* | device-name[*]} [version] [protocol]
Syntax Description
*
|
Displays all of the CDP neighbors.
|
device-name[*]
|
Name of the neighbor about which you want information. You can enter an optional asterisk (*) at the end of an entry-name as a wildcard. For example, entering show cdp entry dev* will match all entries which begin with dev.
|
version
|
(Optional) Limits the display to information about the version of software running on the router.
|
protocol
|
(Optional) Limits the display to information about the protocols enabled on a router.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
10.3
|
This command was introduced.
|
12.2(8)T
|
Support for IPv6 address and address type information was added.
|
12.2(14)S
|
This command was integrated into Cisco IOS Release 12.2(14)S.
|
Examples
The following is sample output from the show cdp entry command. Information about the neighbor device.cisco.com is displayed, including device ID, protocols and addresses, platform, interface, hold time, and version.
Router# show cdp entry device.cisco.com
-------------------------
Device ID: device.cisco.com
IPv6 address: FE80::203:E3FF:FE6A:BF81 (link-local)
IPv6 address: 4000::BC:0:0:C0A8:BC06 (global unicast)
CLNS address: 490001.1111.1111.1111.00
Platform: cisco 3640, Capabilities: Router
Interface: Ethernet0/1, Port ID (outgoing port): Ethernet0/1
Cisco Internetwork Operating System Software
IOS (tm) 3600 Software (C3640-A2IS-M), Experimental Version 12.2
Copyright (c) 1986-2001 by cisco Systems, Inc.
Compiled Wed 08-Aug-01 12:39 by joeuser
The following is sample output from the show cdp entry version command. Only information about the version of software running on device.cisco.com is displayed.
Router# show cdp entry device.cisco.com version
Version information for device.cisco.com:
Cisco Internetwork Operating System Software
IOS (tm) 3600 Software (C3640-A2IS-M), Experimental Version 12.2
Copyright (c) 1986-2001 by cisco Systems, Inc.
Compiled Wed 08-Aug-01 12:39 by joeuser
The following is sample output from the show cdp entry protocol command. Only information about the protocols enabled on device.cisco.com is displayed.
Router# show cdp entry device.cisco.com protocol
Protocol information for device.cisco.com:
IPv6 address: FE80::203:E3FF:FE6A:BF81 (link-local)
IPv6 address: 4000::BC:0:0:C0A8:BC06 (global unicast)
CLNS address: 490001.1111.1111.1111.00
Related Commands
Command
|
Description
|
show cdp
|
Displays global CDP information, including timer and hold-time information.
|
show cdp interface
|
Displays information about the interfaces on which CDP is enabled.
|
show cdp neighbors
|
Displays detailed information about neighboring devices discovered using CDP.
|
show cdp traffic
|
Displays traffic information from the CDP table.
|
show cdp interface
To display information about the interfaces on which Cisco Discovery Protocol (CDP) is enabled, use the show cdp interface command in privileged EXEC mode.
show cdp interface [type number]
Syntax Description
type
|
(Optional) Type of interface about which you want information.
|
number
|
(Optional) Number of the interface about which you want information.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
10.3
|
This command was introduced.
|
Examples
The following is sample output from the show cdp interface command. Status information and information about CDP timer and hold-time settings is displayed for all interfaces on which CDP is enabled.
Router# show cdp interface
Serial0 is up, line protocol is up, encapsulation is SMDS
Sending CDP packets every 60 seconds
Ethernet0 is up, line protocol is up, encapsulation is ARPA
Sending CDP packets every 60 seconds
The following is sample output from the show cdp interface command with an interface specified. Status information and information about CDP timer and hold-time settings is displayed for Ethernet interface 0 only.
Router# show cdp interface ethernet 0
Ethernet0 is up, line protocol is up, encapsulation is ARPA
Sending CDP packets every 60 seconds
Related Commands
Command
|
Description
|
show cdp
|
Displays global CDP information, including timer and hold-time information.
|
show cdp entry
|
Displays information about a specific neighbor device or all neighboring devices discovered using CDP.
|
show cdp neighbors
|
Displays detailed information about neighboring devices discovered using CDP.
|
show cdp traffic
|
Displays traffic information from the CDP table.
|
show cdp neighbors
To display detailed information about neighboring devices discovered using Cisco Discovery Protocol (CDP), use the show cdp neighbors command in privileged EXEC mode.
show cdp neighbors [type number] [detail]
Syntax Description
type
|
(Optional) Type of the interface connected to the neighbors about which you want information.
|
number
|
(Optional) Number of the interface connected to the neighbors about which you want information.
|
detail
|
(Optional) Displays detailed information about a neighbor (or neighbors) including network address, enabled protocols, hold time, and software version.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
10.3
|
This command was introduced.
|
12.0(3)T
|
The output for the detail form of this command was expanded to include CDP Version 2 information.
|
12.2(8)T, 12.2(14)S
|
Support for IPv6 address and address type information was added.
|
Examples
The following example specifies information related to the show cdp neighbors command:
Router# show cdp neighbors
Capability Codes:R - Router, T - Trans Bridge, B - Source Route Bridge S - Switch,
H - Host, I - IGMP, r - Repeater
Device ID Local Intrfce Holdtme Capability Platform Port ID
joe Eth 0 133 R 4500 Eth 0
sam Eth 0 152 R AS5200 Eth 0
terri Eth 0 144 R 3640 Eth0/0
maine Eth 0 141 RP1 Eth 0/0
sancho Eth 0 164 7206 Eth 1/0
Table 75 describes the significant fields shown in the example.
Table 75 show cdp neighbors Field Descriptions
Field
|
Definition
|
Capability Codes
|
The type of device that can be discovered.
|
Device ID
|
The name of the neighbor device and either the MAC address or the serial number of this device.
|
Local Intrfce
|
The local interface through which this neighbor is connected.
|
Holdtme
|
The remaining amount of time (in seconds) the current device will hold the CDP advertisement from a sending router before discarding it.
|
Capability
|
The type of the device listed in the CDP Neighbors table. Possible values are as follows:
R—Router
T—Transparent bridge
B—Source-routing bridge
S—Switch
H—Host
I—IGMP device
r—Repeater
|
Platform
|
The product number of the device.
|
Port ID
|
The interface and port number of the neighboring device.
|
The following is sample output for one neighbor from the show cdp neighbors detail command. Additional detail is shown about neighbors, including network addresses, enabled protocols, and software version.
router# show cdp neighbors detail
Device ID: device.cisco.com
IPv6 address: FE80::203:E3FF:FE6A:BF81 (link-local)
IPv6 address: 4000::BC:0:0:C0A8:BC06 (global unicast)
Platform: cisco 3640, Capabilities: Router
Interface: Ethernet0/1, Port ID (outgoing port): Ethernet0/1
Cisco Internetwork Operating System Software
IOS (tm) 3600 Software (C3640-A2IS-M), Experimental Version 12.2
VTP Management Domain: `Accounting Group'
Table 76 describes the significant fields shown in the display.
Table 76 show cdp neighbors detail Field Descriptions
Field
|
Definition
|
Device ID
|
The name of the neighbor device and either the MAC address or the serial number of this device.
|
Entry address(es)
|
A list of network addresses of neighbor devices.
|
IPv6 address: FE80::203:E3FF:FE6A:BF81 (link-local)
|
The network address of the neighbor device. The address can be in IP, IPv6, IPX, AppleTalk, DECnet, or Connectionless Network Service (CLNS) protocol conventions.
IPv6 addresses are followed by one of the following IPv6 address types:
• global unicast
• link-local
• multicast
• site-local
• V4 compatible
|
Platform
|
The product name and number of the neighbor device.
|
Capabilities
|
The device type of the neighbor. This device can be a router, a bridge, a transparent bridge, a source-routing bridge, a switch, a host, an IGMP device, or a repeater.
|
Interface
|
The local interface through which this neighbor is connected.
|
Port ID
|
The interface and port number of the neighboring device.
|
Holdtime
|
The remaining amount of time (in seconds) the current device will hold the CDP advertisement from a sending router before discarding it.
|
Version
|
The software version of the neighbor device.
|
Duplex Mode
|
The duplex state of connection between the current device and the neighbor device.
|
Native VLAN
|
The ID number of the VLAN on the neighbor device.
|
VTP Management Domain
|
A string that is the name of the collective group of VLANs associated with the neighbor device.
|
Related Commands
Command
|
Description
|
show cdp
|
Displays global CDP information, including timer and hold-time information.
|
show cdp entry
|
Displays information about a specific neighbor device listed in the CDP table.
|
show cdp interface
|
Displays information about the interfaces on which CDP is enabled.
|
show cdp traffic
|
Displays information about traffic between devices gathered using CDP.
|
show cdp traffic
To display information about traffic between devices gathered using Cisco Discovery Protocol (CDP), use the show cdp traffic command in privileged EXEC mode.
show cdp traffic
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
10.3
|
This command was introduced.
|
Examples
The following is sample output from the show cdp traffic command:
Total packets output: 543, Input: 333
Hdr syntax: 0, Chksum error: 0, Encaps failed: 0
No memory: 0, Invalid: 0, Fragmented: 0
CDP version 1 advertisements output: 191, Input: 187
CDP version 2 advertisements output: 352, Input: 146
Table 77 describes the significant fields shown in the display.
Table 77 show cdp traffic Field Descriptions
Field
|
Definition
|
Total packets output
|
The number of CDP advertisements sent by the local device. Note that this value is the sum of the CDP Version 1 advertisements output and CDP Version 2 advertisements output fields.
|
Input
|
The number of CDP advertisements received by the local device. Note that this value is the sum of the CDP Version 1 advertisements input and CDP Version 2 advertisements input fields.
|
Hdr syntax
|
The number of CDP advertisements with bad headers, received by the local device.
|
Chksum error
|
The number of times the checksum (verifying) operation failed on incoming CDP advertisements.
|
Encaps failed
|
The number of times CDP failed to send advertisements on an interface because of a failure caused by the bridge port of the local device.
|
No memory
|
The number of times the local device did not have enough memory to store the CDP advertisements in the advertisement cache table when the device was attempting to assemble advertisement packets for transmission and parse them when receiving them.
|
Invalid
|
The number of invalid CDP advertisements received and sent by the local device.
|
Fragmented
|
The number of times fragments or portions of a single CDP advertisement were received by the local device instead of the complete advertisement.
|
CDP version 1 advertisements output
|
The number of CDP Version 1 advertisements sent by the local device.
|
Input
|
The number of CDP Version 1 advertisements received by the local device.
|
CDP version 2 advertisements output
|
The number of CDP Version 2 advertisements sent by the local device.
|
Input
|
The number of CDP Version 2 advertisements received by the local device.
|
Related Commands
Command
|
Description
|
show cdp
|
Displays global CDP information, including timer and hold-time information.
|
show cdp entry
|
Displays information about a specific neighbor device listed in the CDP table.
|
show cdp interface
|
Displays information about the interfaces on which CDP is enabled.
|
show cdp neighbors
|
Displays detailed information about neighboring devices discovered using CDP.
|
show clock
To display the time and date from the system software clock, use the show clock command in EXEC mode.
show clock [detail]
Syntax Description
detail
|
(Optional) Indicates the clock source (NTP, VINES, hardware clock, and so on) and the current summer-time setting (if any).
|
Command Modes
EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
Usage Guidelines
The software clock keeps an "authoritative" flag that indicates whether the time is authoritative (believed to be accurate). If the software clock has been set by a timing source (for example, via NTP), the flag is set. If the time is not authoritative, it will be used only for display purposes. Until the clock is authoritative and the "authoritative" flag is set, the flag prevents peers from synchronizing to the software clock.
The symbol that precedes the show clock display indicates the following:
Symbol
|
Description
|
Example
|
*
|
Time is not authoritative: the software clock is not in sync or has never been set.
|
*15:29:03.158 UTC Tue Feb 25 2003:
|
(blank)
|
Time is authoritative: the software clock is in sync or has just been set manually
|
15:29:03.158 UTC Tue Feb 25 2003:
|
.
|
Time is authoritative, but NTP is not synchronized: the software clock was in sync, but has since lost contact with all configured NTP servers
|
.15:29:03.158 UTC Tue Feb 25 2003:
|
These symbols are also used in NTP-based timestamping, such as for syslog (SEM) messages.
Note
In general, NTP synchronization takes approximately 15 to 20 minutes.
Examples
The following sample output shows that the current clock is authoritative and that the time source is NTP:
Router> show clock detail
15:29:03.158 PST Tue Feb 25 2003
The following example shows the current clock is authoritative, but NTP is not yet synchronized:
.16:42:35.597 UTC Tue Feb 25 2003
Related Commands
Command
|
Description
|
clock set
|
Manually sets the software clock.
|
show calendar
|
Displays the current time and date setting of the system hardware clock.
|
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.
|
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 cns config connections
To display the status of the Cisco Networking Services (CNS) event agent connection, use the show cns config connections command in privileged EXEC mode.
show cns config connections
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.2(8)T
|
This command was introduced.
|
Usage Guidelines
Use the show cns config connections command to determine whether the CNS event agent is connecting to the gateway, connected, or active, and to display the gateway used by the event agent and its IP address and port number.
Examples
The following is sample output from the show cns config connections command:
Router# show cns config connections
The partial configuration agent is enabled.
Configuration server: 10.1.1.1
Connection Status: Connection not active.
Related Commands
Command
|
Description
|
show cns config outstanding
|
Displays information about incremental CNS configurations that have started but not yet completed.
|
show cns config stats
|
Displays statistics about the CNS configuration agent.
|
show cns config outstanding
To display information about incremental (partial) Cisco Networking Services (CNS) configurations that have started but not yet completed, use the show cns config outstanding command in privileged EXEC mode.
show cns config outstanding
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.2(2)T
|
This command was introduced.
|
12.2(8)T
|
This command was implemented on Cisco 2600 series and Cisco 3600 series routers.
|
Usage Guidelines
Use the show cns config outstanding command to display information about outstanding incremental (partial) configurations that have started but not yet completed, including the following:
•
Queue ID (location of configuration in the config queue)
•
Identifier (group ID)
•
Config ID (identity of configuration within the group)
Examples
The following is sample output from the show cns config outstanding command:
Router# show cns config outstanding
The outstanding configuration information:
queue id identifier config-id
1 identifierREAD config_idREAD
Related Commands
Command
|
Description
|
cns config cancel
|
Cancels an incremental two-phase synchronization configuration.
|
config-cli
|
Displays the status of the CNS event agent connection.
|
show cns config stats
|
Displays statistics about the CNS configuration agent.
|
show cns config stats
To display statistics about the CNS configuration agent, use the show cns config stats command in privileged EXEC mode.
show cns config stats
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.2(2)T
|
This command was introduced.
|
12.2(8)T
|
This command was implemented on Cisco 2600 series and Cisco 3600 series routers.
|
12.3(1)
|
Additional output fields were added.
|
Usage Guidelines
This command displays the following statistics on the CNS configuration agent:
•
The number of configurations requests received
•
The number of configurations completed
•
The number of configurations failed
•
The number of configurations pending
•
The number of configurations cancelled
•
The time stamp of the last configuration received
•
The time stamp of the initial configuration received
Examples
The following is sample output from the show cns config stats command:
Router# show cns config stats
6 configuration requests received.
4 configurations completed.
1 configurations pending.
0 configurations cancelled.
The time of last received configuration is *May 5 2003 10:42:15 UTC.
Initial Config received *May 5 2003 10:45:15 UTC.
Related Commands
Command
|
Description
|
clear cns config stats
|
Clears all the statistics about the CNS configuration agent.
|
show cns config outstanding
|
Displays information about incremental CNS configurations that have started but not yet completed.
|
show cns config status
To display the status of the Cisco Networking Services (CNS) Configuration Agent, use the show cns config status command in EXEC mode.
show cns config status
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Release
|
Modification
|
12.2(2)T
|
This command was introduced.
|
12.0(18)ST
|
This command was integrated into Cisco IOS Release 12.0(18)ST.
|
12.0(22)S
|
This command was integrated into Cisco IOS Release 12.0 (22)S.
|
Usage Guidelines
This command displays the status of the Configuration Agent. Use this option to display the following information about the Configuration Agent:
•
Status of the Configuration Agent, for example, whether it has been configured properly.
•
IP address and port number of the trusted server that the Configuration Agent is using.
•
Config ID (identity of configuration within the configuration group).
Related Commands
Command
|
Description
|
cns config cancel
|
Cancels a CNS configuration.
|
cns config initial
|
Starts the initial CNS Configuration Agent.
|
cns config partial
|
Starts the partial CNS Configuration Agent.
|
cns config retrieve
|
Gets the configuration of a routing device using CNS.
|
show cns event connections
To display the status of the Cisco Networking Services (CNS) event agent connection, use the show cns event connections command in privileged EXEC mode.
show cns event connections
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.2(8)T
|
This command was introduced.
|
Usage Guidelines
Use the show cns event connections command to display the status of the event agent connection—such as whether it is connecting to the gateway, connected, or active—and to display the gateway used by the event agent and its IP address and port number.
Examples
The following example displays the IP address and port number of the primary and backup gateways:
Router# show cns event connections
The currently configured primary event gateway:
Event-Id is Internal test1
The currently configured backup event gateway:
The currently connected event gateway:
Related Commands
Command
|
Description
|
show cns event stats
|
Displays statistics about the CNS event agent connection.
|
show cns event subject
|
Displays a list of subjects about the CNS event agent connection.
|
show cns event gateway
To display information about the Cisco Networking Services (CNS) Event Agent, use the show cns event gateway command in EXEC mode.
show cns event gateway
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
Release
|
Modification
|
12.2(2)T
|
This command was introduced.
|
12.0(18)ST
|
This command was integrated into Cisco IOS Release 12.0 (18)ST
|
Usage Guidelines
Use this command to display the following information about CNS gateways:
•
Primary gateway:
–
IP address
–
Port number
•
Backup gateways:
–
IP address
–
Port number
•
Currently connected gateway:
–
IP address
–
Port number
Related Commands
Command
|
Description
|
cns event
|
Configures the CNS Event Gateway.
|
show cns event stats
To display statistics about the CNS event agent connection, use the show cns event stats command in privileged EXEC mode.
show cns event stats
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.2(2)T
|
This command was introduced.
|
12.0(18)ST
|
This command was integrated into Cisco IOS Release 12.0(18)ST.
|
12.0(22)S
|
This command was integrated into Cisco IOS Release 12.0(22)S.
|
12.2(8)T
|
This command was implemented on the Cisco 2600 series and the Cisco 3600 series routers.
|
12.3(1)
|
Output was changed to display statistics generated since last cleared.
|
Usage Guidelines
Use this command to display the following statistics for the CNS event agent:
•
Number of events received
•
Number of events sent
•
Number of events not processed successfully
•
Number of events in the queue
•
Time stamp showing when statistics were last cleared (time stamp is router time)
•
Number of events received since the statistics were cleared
•
Time stamp of latest event received (time stamp is router time)
•
Time stamp of latest event sent
•
Number of applications using the Event Agent
•
Number of subjects subscribed
Examples
The following example displays statistics for the CNS event agent:
Router# show cns event stats
0 events sent to other IOS applications.
Event agent stats last cleared at Apr 4 2003 00:55:25 UTC
No events received since stats cleared
The time stamp of the last received event is *Mar 30 2003 11:04:08 UTC
The time stamp of the last sent event is *Apr 11 2003 22:21:23 UTC
3 applications are using the event agent.
Related Commands
Command
|
Description
|
clear cns event stats
|
Clears all the statistics about the CNS event agent.
|
cns event
|
Enables and configures CNS event agent services.
|
show cns event connections
|
Displays the status of the CNS event agent connection.
|
show cns event subject
|
Displays a list of subjects about the CNS event agent connection.
|
show cns event status
To display information about the Cisco Networking Services (CNS) Event Agent, use the show cns event status command in EXEC mode.
show cns event status
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Release
|
Modification
|
12.2(2)T
|
This command was introduced.
|
12.0(18)ST
|
This command was integrated into Cisco IOS Release 12.0 (18)ST.
|
Usage Guidelines
Use this command to display the following information about the CNS Event Agent:
•
Status of Event Agent:
–
Connected
–
Active
•
Gateway used by the Event Agent:
–
IP address
–
Port number
•
Device ID
Related Commands
Command
|
Description
|
cns event
|
Configures the CNS Event Gateway.
|
show cns event subject
To display a list of subjects about the Cisco Networking Services (CNS) event agent connection, use the show cns event subject command in privileged EXEC mode.
show cns event subject [name]
Syntax Description
name
|
(Optional) Displays a list of applications that are subscribing to this specific subject name.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.2(2)T
|
This command was introduced.
|
12.0(18)ST
|
This command was integrated into Cisco IOS Release 12.0(18)ST.
|
12.0(22)S
|
This command was integrated into Cisco IOS Release 12.0(22)S.
|
12.2(8)T
|
This command was implemented on the Cisco 2600 series and the Cisco 3600 series.
|
Usage Guidelines
Use the show cns event subject command to display a list of subjects of the event agent that are subscribed to by applications.
Examples
The following example displays the IP address and port number of the primary and backup gateways:
Router# show cns event subject
The list of subjects subscribed by applications.
cisco.cns.mibaccess:request
Related Commands
Command
|
Description
|
show cns event connections
|
Displays the status of the CNS event agent connection.
|
show cns event stats
|
Displays statistics about the CNS event agent connection.
|
show cns image connections
To display the status of the Cisco Networking Services (CNS) image management server HTTP connections, use the show cns image connections command in privileged EXEC mode.
show cns image connections
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.3(1)
|
This command was introduced.
|
Usage Guidelines
Use the show cns image connections command when troubleshooting HTTP connection problems with the CNS image server. The output displays the following information:
•
Number of connection attempts
•
Number of connections that were never connected and those that were abruptly disconnected
•
Date and time of last successful connection
Examples
The following is sample output from the show cns image connections command:
Router# show cns image connections
CNS Image Agent: HTTP connections
never connected:0 Abrupt disconnect:0
Last successful connection at 11:45:02.000 UTC Mon May 6 2003
Related Commands
Command
|
Description
|
show cns image inventory
|
Displays inventory information about the CNS image agent.
|
show cns image status
|
Displays status information about the CNS image agent.
|
show cns image inventory
To provide a dump of Cisco Networking Services (CNS) image inventory information in XML format, use the show cns image inventory command in privileged EXEC mode.
show cns image inventory
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.3(1)
|
This command was introduced.
|
Usage Guidelines
To view the XML output in a better format, paste the content into a text file and use an XML viewing tool.
Examples
The following is sample output from the show cns image inventory command:
Router# show cns image inventory
<imageInventoryReport><deviceName><imageID>Router</imageID><hostName>Router</ho
IOS (tm) C2600 Software (C2600-I-M), Experimental Version 12.3(20030414:081500)]
Copyright (c) 1986-2003 by cisco Systems, Inc.
Compiled Mon 14-Apr-03 02:03 by engineer</versionString><imageFile>tftp://10.25>
Related Commands
Command
|
Description
|
show cns image connections
|
Displays connection information for the CNS image agent.
|
show cns image status
|
Displays status information about the CNS image agent.
|
show cns image status
To display status information about the Cisco Networking Services (CNS) image agent, use the show cns image status command in privileged EXEC mode.
show cns image status
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.3(1)
|
This command was introduced.
|
Usage Guidelines
Use this command to display the following status information about the CNS image agent:
•
Start date and time of last upgrade
•
End date and time of last upgrade
•
End date and time of last successful upgrade
•
End date and time of last failed upgrade
•
Number of failed upgrades
•
Number of successful upgrades with number of received messages and errors
•
Transmit status with number of attempts, successes, and failures
Examples
The following is sample output from the show cns image status command:
Router# show cns image status
Last upgrade started at 11:45:02.000 UTC Mon May 6 2003
Last upgrade ended at 11:56:04.000 UTC Mon May 6 2003 status SUCCESS
Last successful upgrade ended at 00:00:00.000 UTC Mon May 6 2003
Last failed upgrade ended at 00:00:00.000 UTC Wed Apr 16 2003
Number of failed upgrades: 2
Number of successful upgrades: 6
Related Commands
Command
|
Description
|
show cns image connections
|
Displays connection information for the CNS image agent.
|
show cns image inventory
|
Displays image inventory information in XML format.
|
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.
|
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.
|
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.
|
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.
|
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.
|