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
setup
show aliases
show async bootp
show bootvar
show buffers
show c2600
show c7200
show calendar
show cdp entry
show cdp interface
show cdp neighbors
show cdp traffic
show cdp
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> 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 43 describes the symbols that proceed the timestamp.
Table 43 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
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 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 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 44 describes the significant fields shown in the display.
Table 44 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 EXEC mode.
show bootvar
Syntax Description
This command has no arguments or keywords.
Command Modes
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 45 describes the significant fields shown in the display.
Table 45 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 buffe |