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: