Cisco Command Reference PDF
Cisco Command Reference PDF
Configuration Fundamentals
Command Reference
Release 12.2
Corporate Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: 408 526-4000
800 553-NETS (6387)
Fax: 408 526-4100
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT
NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE
PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR
APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION
PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO
LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of
UCBs public domain version of the UNIX operating system. All rights reserved. Copyright 1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED
AS IS WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED,
INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL
DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR
INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
AccessPath, AtmDirector, Browse with Me, CCDA, CCDE, CCDP, CCIE, CCNA, CCNP, CCSI, CD-PAC, CiscoLink, the Cisco NetWorks logo, the Cisco
Powered Network logo, Cisco Systems Networking Academy, the Cisco Systems Networking Academy logo, Fast Step, Follow Me Browsing, FormShare,
FrameShare, GigaStack, IGX, Internet Quotient, IP/VC, iQ Breakthrough, iQ Expertise, iQ FastTrack, the iQ Logo, iQ Net Readiness Scorecard, MGX,
the Networkers logo, Packet, PIX, RateMUX, ScriptBuilder, ScriptShare, SlideCast, SMARTnet, TransPath, Unity, Voice LAN, Wavelength Router, and
WebViewer are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, Discover All Thats Possible, and Empowering
the Internet Generation, are service marks of Cisco Systems, Inc.; and Aironet, ASIST, BPX, Catalyst, Cisco, the Cisco Certified Internetwork Expert logo,
Cisco IOS, the Cisco IOS logo, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Enterprise/Solver, EtherChannel, EtherSwitch, FastHub,
FastSwitch, IOS, IP/TV, LightStream, MICA, Network Registrar, Post-Routing, Pre-Routing, Registrar, StrataView Plus, Stratm, SwitchProbe, TeleRouter,
and VCO are registered trademarks of Cisco Systems, Inc. or its affiliates in the U.S. and certain other countries.
All other brands, names, or trademarks mentioned in this document or Web site are the property of their respective owners. The use of the word partner
does not imply a partnership relationship between Cisco and any other company. (0102R)
Cisco IOS Configuration Fundamentals Command Reference
2001 2006 Cisco Systems, Inc.
All rights reserved.
CONTENTS
About Cisco IOS Software Documentation
Using Cisco IOS Software
xiii
FR-3
FR-45
FR-53
FR-123
FR-167
FR-179
FR-231
FR-267
FR-293
FR-311
FR-343
FR-375
FR-481
FR-667
FR-743
FR-767
FR-805
iii
Contents
WCCP Commands
FR-895
APPENDIXES
ASCII Character Set and Hex Values
FR-919
FR-925
INDEX
iv
78-11740-02
Documentation Objectives
Cisco IOS software documentation describes the tasks and commands necessary to configure and
maintain Cisco networking devices.
Audience
The Cisco IOS software documentation set is intended primarily for users who configure and maintain
Cisco networking devices (such as routers and switches) but who may not be familiar with the tasks,
the relationship between tasks, or the Cisco IOS software commands necessary to perform particular
tasks. The Cisco IOS software documentation set is also intended for those users experienced with
Cisco IOS software who need to know about new features, new configuration options, and new software
characteristics in the current Cisco IOS software release.
Documentation Organization
The Cisco IOS software documentation set consists of documentation modules and master indexes. In
addition to the main documentation set, there are supporting documents and resources.
Documentation Modules
The Cisco IOS documentation modules consist of configuration guides and corresponding command
reference publications. Chapters in a configuration guide describe protocols, configuration tasks, and
Cisco IOS software functionality and contain comprehensive configuration examples. Chapters in a
command reference publication provide complete Cisco IOS command syntax information. Use each
configuration guide in conjunction with its corresponding command reference publication.
Note
Figure 1
The abbreviations (for example, FC and FR) next to the book icons are page designators,
which are defined in a key in the index of each document to help you with navigation. The
bullets under each module list the major technology areas discussed in the corresponding
books.
FC
Cisco IOS
Configuration
Fundamentals
Configuration
Guide
Cisco IOS
Configuration
Fundamentals
Command
Reference
FR
IP2R
Module FC/FR:
Cisco IOS User
Interfaces
File Management
System Management
WR
Cisco IOS
Wide-Area
Networking
Command
Reference
Module WC/WR:
ATM
Broadband Access
Frame Relay
SMDS
X.25 and LAPB
Cisco IOS
IP Command
Reference,
Volume 1 of 3:
Addressing
and Services
Cisco IOS
IP Command
Reference,
Volume 2 of 3:
Routing
Protocols
P2C
IP3R
Cisco IOS
IP Command
Reference,
Volume 3 of 3:
Multicast
Cisco IOS
Interface
Configuration
Guide
IR
Cisco IOS
Interface
Command
Reference
Module IC/IR:
LAN Interfaces
Serial Interfaces
Logical Interfaces
P3C
Cisco IOS
AppleTalk and
Novell IPX
Configuration
Guide
P2R
Module IPC/IP1R/IP2R/IP3R:
IP Addressing and Services
IP Routing Protocols
IP Multicast
IC
Cisco IOS
Wide-Area
Networking
Configuration
Guide
IP1R
Cisco IOS
AppleTalk and
Novell IPX
Command
Reference
P3R
Module P2C/P2R:
AppleTalk
Novell IPX
MWC
Cisco IOS
Mobile
Wireless
Configuration
Guide
MWR
Cisco IOS
Mobile
Wireless
Command
Reference
Module MWC/MWR:
General Packet
Radio Service
Cisco IOS
Apollo Domain,
Banyan VINES,
DECnet, ISO
CLNS, and XNS
Configuration
Guide
SC
Cisco IOS
Apollo Domain,
Banyan VINES,
DECnet, ISO
CLNS, and XNS
Command
Reference
Module P3C/P3R:
Apollo Domain
Banyan VINES
DECnet
ISO CLNS
XNS
Cisco IOS
Security
Configuration
Guide
SR
Cisco IOS
Security
Command
Reference
Module SC/SR:
AAA Security Services
Security Server Protocols
Traffic Filtering and Firewalls
IP Security and Encryption
Passwords and Privileges
Neighbor Router Authentication
IP Security Options
Supported AV Pairs
47953
WC
Cisco IOS
IP
Configuration
Guide
vi
78-11740-02
Cisco IOS
Dial
Technologies
Configuration
Guide
TC
BC
Cisco IOS
Terminal
Services
Configuration
Guide
Cisco IOS
Bridging and
IBM Networking
Configuration
Guide
B2R
B1R
DR
Cisco IOS
Dial
Technologies
Command
Reference
TR
Module DC/DR:
Preparing for Dial Access
Modem and Dial Shelf Configuration
and Management
ISDN Configuration
Signalling Configuration
Dial-on-Demand Routing
Configuration
Dial-Backup Configuration
Dial-Related Addressing Services
Virtual Templates, Profiles, and
Networks
PPP Configuration
Callback and Bandwidth Allocation
Configuration
Dial Access Specialized Features
Dial Access Scenarios
VC
Cisco IOS
Voice, Video,
and Fax
Configuration
Guide
VR
Cisco IOS
Voice, Video,
and Fax
Command
Reference
Module VC/VR:
Voice over IP
Call Control Signalling
Voice over
Frame Relay
Voice over ATM
Telephony Applications
Trunk Management
Fax, Video, and
Modem Support
Cisco IOS
Bridging
and IBM
Networking
Command
Reference,
Volume 1 of 2
Cisco IOS
Terminal
Services
Command
Reference
Module BC/B1R:
Transparent
Bridging
SRB
Token Ring
Inter-Switch Link
Token Ring Route
Switch Module
RSRB
DLSw+
Serial Tunnel and
Block Serial Tunnel
LLC2 and SDLC
IBM Network
Media Translation
SNA Frame Relay
Access
NCIA Client/Server
Airline Product Set
Module TC/TR:
ARA
LAT
NASI
Telnet
TN3270
XRemote
X.28 PAD
Protocol Translation
QC
XC
Cisco IOS
Quality of
Service
Solutions
Configuration
Guide
QR
Cisco IOS
Bridging
and IBM
Networking
Command
Reference,
Volume 2 of 2
Cisco IOS
Quality of
Service
Solutions
Command
Reference
Cisco IOS
Switching
Services
Configuration
Guide
XR
Module QC/QR:
Packet Classification
Congestion Management
Congestion Avoidance
Policing and Shaping
Signalling
Link Efficiency
Mechanisms
Module BC/B2R:
DSPU and SNA
Service Point
SNA Switching
Services
Cisco Transaction
Connection
Cisco Mainframe
Channel Connection
CLAW and TCP/IP
Offload
CSNA, CMPC,
and CMPC+
TN3270 Server
Cisco IOS
Switching
Services
Command
Reference
Module XC/XR:
Cisco IOS
Switching Paths
NetFlow Switching
Multiprotocol Label Switching
Multilayer Switching
Multicast Distributed Switching
Virtual LANs
LAN Emulation
47954
DC
vii
Master Indexes
Two master indexes provide indexing information for the Cisco IOS software documentation set:
an index for the configuration guides and an index for the command references. Individual books also
contain a book-specific index.
The master indexes provide a quick way for you to find a command when you know the command name
but not which module contains the command. When you use the online master indexes, you can click
the page number for an index entry and go to that page in the online document.
Cisco IOS Command Summary (two volumes)This publication explains the function and syntax
of the Cisco IOS software commands. For more information about defaults and usage guidelines,
refer to the Cisco IOS command reference publications.
Cisco IOS System Error MessagesThis publication lists and describes Cisco IOS system error
messages. Not all system error messages indicate problems with your system. Some are purely
informational, and others may help diagnose problems with communications lines, internal
hardware, or the system software.
Cisco IOS Debug Command ReferenceThis publication contains an alphabetical listing of the
debug commands and their descriptions. Documentation for each command includes a brief
description of its use, command syntax, usage guidelines, and sample output.
Dictionary of Internetworking Terms and AcronymsThis Cisco publication compiles and defines
the terms and acronyms used in the internetworking industry.
New feature documentationThe Cisco IOS software documentation set documents the mainline
release of Cisco IOS software (for example, Cisco IOS Release 12.2). New software features are
introduced in early deployment releases (for example, the Cisco IOS T release train for 12.2,
12.2(x)T). Documentation for these new features can be found in standalone documents called
feature modules. Feature module documentation describes new Cisco IOS software and hardware
networking functionality and is available on Cisco.com and the Documentation CD-ROM.
RFCsRFCs are standards documents maintained by the Internet Engineering Task Force (IETF).
Cisco IOS software documentation references supported RFCs when applicable. The full text of
referenced RFCs may be obtained on the World Wide Web at http://www.rfc-editor.org/.
MIBsMIBs are used for network monitoring. For lists of supported MIBs by platform and
release, and to download MIB files, see the Cisco MIB website on Cisco.com at
http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml.
viii
78-11740-02
Document Conventions
Within Cisco IOS software documentation, the term router is generally used to refer to a variety of Cisco
products (for example, routers, access servers, and switches). Routers, access servers, and other
networking devices that support Cisco IOS software are shown interchangeably within examples. These
products are used only for illustrative purposes; that is, an example that shows one product does not
necessarily indicate that other products are not supported.
The Cisco IOS documentation set uses the following conventions:
Convention
Description
^ or Ctrl
The ^ and Ctrl symbols represent the Control key. For example, the key combination ^D or Ctrl-D
means hold down the Control key while you press the D key. Keys are indicated in capital letters but
are not case sensitive.
string
A string is a nonquoted set of characters shown in italics. For example, when setting an SNMP
community string to public, do not use quotation marks around the string or the string will include the
quotation marks.
Command syntax descriptions use the following conventions:
Convention
Description
boldface
Boldface text indicates commands and keywords that you enter literally as shown.
italics
[x]
A vertical line indicates a choice within an optional or required set of keywords or arguments.
[x | y]
Square brackets enclosing keywords or arguments separated by a vertical line indicate an optional
choice.
{x | y}
Braces enclosing keywords or arguments separated by a vertical line indicate a required choice.
Nested sets of square brackets or braces indicate optional or required choices within optional or
required elements. For example:
Convention
Description
[x {y | z}]
Braces and a vertical line within square brackets indicate a required choice within an optional element.
Examples use the following conventions:
Convention
Description
screen
boldface screen
Examples of text that you must enter are set in Courier bold font.
<
Angle brackets enclose text that is not printed to the screen, such as passwords.
>
ix
Convention
Description
An exclamation point at the beginning of a line indicates a comment line. (Exclamation points are also
displayed by the Cisco IOS software for certain processes.)
Caution
Note
Timesaver
Means reader be careful. In this situation, you might do something that could result in
equipment damage or loss of data.
Means reader take note. Notes contain helpful suggestions or references to materials not
contained in this manual.
Means the described action saves time. You can save time by performing the action
described in the paragraph.
Obtaining Documentation
The following sections provide sources for obtaining documentation from Cisco Systems.
Documentation CD-ROM
Cisco documentation and additional literature are available in a CD-ROM package, which ships
with your product. The Documentation CD-ROM is updated monthly and may be more current than
printed documentation. The CD-ROM package is available as a single unit or through an
annual subscription.
78-11740-02
Ordering Documentation
Cisco documentation can be ordered in the following ways:
Registered Cisco Direct Customers can order Cisco product documentation from the Networking
Products MarketPlace:
http://www.cisco.com/cgi-bin/order/order_root.pl
Registered Cisco.com users can order the Documentation CD-ROM through the online
Subscription Store:
http://www.cisco.com/go/subscription
Nonregistered Cisco.com users can order documentation through a local account representative by
calling Cisco corporate headquarters (California, USA) at 408 526-7208 or, in North America, by
calling 800 553-NETS(6387).
Documentation Feedback
If you are reading Cisco product documentation on the World Wide Web, you can submit technical
comments electronically. Click Feedback in the toolbar and select Documentation. After you complete
the form, click Submit to send it to Cisco.
You can e-mail your comments to [email protected].
To submit your comments by mail, use the response card behind the front cover of your document, or
write to the following address:
Cisco Systems, Inc.
Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883
We appreciate your comments.
Cisco.com
Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open
access to Cisco information and resources at anytime, from anywhere in the world. This highly
integrated Internet application is a powerful, easy-to-use tool for doing business with Cisco.
Cisco.com provides a broad range of features and services to help customers and partners streamline
business processes and improve productivity. Through Cisco.com, you can find information about Cisco
and our networking solutions, services, and programs. In addition, you can resolve technical issues with
online technical support, download and test software packages, and order Cisco learning materials and
merchandise. Valuable online skill assessment, training, and certification programs are also available.
xi
Customers and partners can self-register on Cisco.com to obtain additional personalized information
and services. Registered users can order products, check on the status of an order, access technical
support, and view benefits specific to their relationships with Cisco.
To access Cisco.com, go to the following website:
http://www.cisco.com
P4You need information or assistance on Cisco product capabilities, product installation, or basic
product configuration.
In each of the above cases, use the Cisco TAC website to quickly find answers to your questions.
To register for Cisco.com, go to the following website:
http://www.cisco.com/register/
If you cannot resolve your technical issue by using the TAC online resources, Cisco.com registered
users can open a case online by using the TAC Case Open tool at the following website:
http://www.cisco.com/tac/caseopen
P1Your production network is down, causing a critical impact to business operations if service
is not restored quickly. No workaround is available.
P2Your production network is severely degraded, affecting significant aspects of your business
operations. No workaround is available.
xii
78-11740-02
Getting Help
For an overview of Cisco IOS software configuration, refer to the Release 12.2 Cisco IOS
Configuration Fundamentals Configuration Guide.
For information on the conventions used in the Cisco IOS software documentation set, see the previous
chapter, About Cisco IOS Software Documentation.
xiii
Table 1 describes how to access and exit various common command modes of the Cisco IOS software.
It also shows examples of the prompts displayed for each mode.
Table 1
Command
Mode
Access Method
Prompt
Exit Method
User EXEC
Log in.
Router>
Privileged
EXEC
Router#
Global
configuration
Router(config)#
Interface
configuration
Router(config-if)#
From global
configuration mode,
specify an interface using
an interface command.
>
From privileged EXEC
mode, use the reload
EXEC command. Press
the Break key during the
first 60 seconds while the
system is booting.
ROM monitor
For more information on command modes, refer to the Using the Command-Line Interface chapter in
the Release 12.2 Cisco IOS Configuration Fundamentals Configuration Guide.
Getting Help
Entering a question mark (?) at the CLI prompt displays a list of commands available for each command
mode. You can also get a list of keywords and arguments associated with any command by using the
context-sensitive help feature.
To get help specific to a command mode, a command, a keyword, or an argument, use one of the
following commands:
Command
Purpose
help
abbreviated-command-entry?
Provides a list of commands that begin with a particular character string. (No space
between command and question mark.)
abbreviated-command-entry<Tab>
command ?
Lists the keywords or arguments that you must enter next on the command line.
(Space between command and question mark.)
xiv
78-11740-02
Command
Comment
Router> enable
Password: <password>
Router#
xv
Table 2
Command
Comment
Router(config-if)# ?
Interface configuration commands:
.
.
.
ip
Interface Internet Protocol config commands
keepalive
Enable keepalive
lan-name
LAN Name command
llc2
LLC2 Interface Subcommands
load-interval
Specify interval for load calculation for an
interface
locaddr-priority
Assign a priority group
logging
Configure logging for interface
loopback
Configure internal loopback on an interface
mac-address
Manually set interface MAC address
mls
mls router sub/interface commands
mpoa
MPOA interface configuration commands
mtu
Set the interface Maximum Transmission Unit (MTU)
netbios
Use a defined NETBIOS access list or enable
name-caching
no
Negate a command or set its defaults
nrzi-encoding
Enable use of NRZI encoding
ntp
Configure NTP
.
.
.
Router(config-if)#
Router(config-if)# ip ?
Interface IP configuration subcommands:
access-group
Specify access control for packets
accounting
Enable IP accounting on this interface
address
Set the IP address of an interface
authentication
authentication subcommands
bandwidth-percent
Set EIGRP bandwidth limit
broadcast-address
Set the broadcast address of an interface
cgmp
Enable/disable CGMP
directed-broadcast Enable forwarding of directed broadcasts
dvmrp
DVMRP interface commands
hello-interval
Configures IP-EIGRP hello interval
helper-address
Specify a destination address for UDP broadcasts
hold-time
Configures IP-EIGRP hold time
.
.
.
Router(config-if)# ip
xvi
78-11740-02
Table 2
Command
Comment
Router(config-if)# ip address ?
A.B.C.D
IP address
negotiated
IP Address negotiated over PPP
Router(config-if)# ip address
xvii
have variables set to certain default values. In these cases, the default form of the command enables the
command and sets the variables to their default values. The Cisco IOS software command reference
publications describe the effect of the default form of a command if the command functions differently
than the no form.
It might take a minute or two to save the configuration. After the configuration has been saved, the
following output appears:
[OK]
Router#
On most platforms, this task saves the configuration to NVRAM. On the Class A Flash file system
platforms, this task saves the configuration to the location specified by the CONFIG_FILE environment
variable. The CONFIG_FILE variable defaults to NVRAM.
For more information on the search and filter functionality, refer to the Using the Command-Line
Interface chapter in the Cisco IOS Configuration Fundamentals Configuration Guide.
xviii
78-11740-02
Memory recommendations
Feature descriptions
Release notes are intended to be release-specific for the most current release, and the information
provided in these documents may not be cumulative in providing information about features that first
appeared in previous releases.
xix
xx
78-11740-02
FR-3
disable
To exit privileged EXEC mode and return to user EXEC mode, or to exit to a lower privilege level, enter
the disable EXEC command.
disable [privilege-level]
Syntax Description
privilege-level
Command Modes
EXEC
Command History
Release
Modification
10.0
Usage Guidelines
Note
Examples
Up to 16 security levels can be configured using Cisco IOS software. If such levels are configured on a
system, using this command with the privilege-level option allows you to exit to a lower security level.
If a level is not specified, the user will exit to the user EXEC mode, which is the default.
Five EXEC commands are associated with privilege level 0: disable, enable, exit, help, and logout.
If you configure a privilege level greater than 0, these five commands will not be included in the
command set for that privilege level.
In the following example, the user enters privileged EXEC mode using the enable command, then exits
back to user EXEC mode using the disable command. Note that the prompt for user EXEC mode is >,
and the prompt for privileged EXEC mode is #.
Router> enable
Password: <letmein>
Router# disable
Router>
Related Commands
Command
Description
enable
FR-4
78-11740-02
editing
To reenable Cisco IOS enhanced editing features for a particular line after they have been disabled, use
the editing line configuration command. To disable these features, use the no form of this command.
editing
no editing
Syntax Description
Defaults
Enabled
Command Modes
Line configuration
Command History
Release
Modification
10.0
Usage Guidelines
Enhanced editing features are enabled by default. However, there may be situations in which you need
to disable these features. The no form of this command disables these enhanced editing features, and the
plain form of the command can be used to reenable these features.
Table 3 provides a description of the keys used to enter and edit commands when the editing features are
enabled. Ctrl indicates the Control key, which must be pressed simultaneously with its associated letter
key. Esc indicates the Escape key, which must be pressed first, followed by its associated letter key. A
comma is used in the following table to indicate a key sequence (the comma key should not be pressed).
Keys are not case sensitive. Many letters used for CLI navigation and editing were chosen to provide an
easy way of remembering their functions. In the following table (Table 3), characters are bolded in the
Function Summary column to indicate the relation between the letter used and the function.
FR-5
Table 3
Keys
Function Summary
Function Details
Tab
Complete command
Return
(at the command
line)
Execute
Return
(at the --More-prompt)
Continue
Space Bar
(at the --More-prompt)
Continue
Delete or
Backspace
Backspace
Left Arrow1 or
Ctrl-B
Back character
Right Arrow1 or
Ctrl-F
Forward character
Esc, B
Back word
Esc, F
Forward word
Ctrl-A
Beginning of line
Ctrl-E
End of line
Ctrl-D
Delete character
Esc, D
Ctrl-W
Ctrl-K
Ctrl-U or Ctrl-X
Ctrl-T
Transpose characters
FR-6
78-11740-02
Table 3
Keys
Function Summary
Function Details
Ctrl-R or Ctrl-L
Redisplay line
Ctrl-V or Esc, Q
Ignore editing
Up Arrow1 or
Ctrl-P
Previous command
Down Arrow1 or
Ctrl-N (next)
Next command
Ctrl-Y
Esc, Y
Esc, C
Capitalize word
Esc, U
Esc, L
Examples
Related Commands
Command
Description
terminal editing
Controls CLI enhanced editing feature for the current terminal session.
FR-7
enable
To enter privileged EXEC mode, or any other security level set by a system administrator, use the enable
EXEC command.
enable [privilege-level]
Syntax Description
privilege-level
Defaults
Command Modes
EXEC
Command History
Release
Modification
10.0
Usage Guidelines
Entering privileged EXEC mode enables the use of privileged commands. Because many of the
privileged commands set operating parameters, privileged access should be password-protected to
prevent unauthorized use. If the system administrator has set a password with the enable password
global configuration command, you are prompted to enter it before being allowed access to privileged
EXEC mode. The password is case sensitive.
If an enable password has not been set, enable mode only can be accessed through the console
connection.
Security levels can be set by an administrator using the enable password and privilege level commands.
Up to 16 privilege levels can be specified, using the numbers 0 through 15. Using these privilege levels,
the administrator can allow or deny access to specific commands. Privilege level 0 is associated with
user EXEC mode, and privilege level 15 is associated with privileged EXEC mode.
For more information on defined privilege levels, see the Passwords and Privileges chapters of the
Cisco IOS Security Configuration Guide and the Cisco IOS Security Command Reference publications.
If a level is not specified when entering the enable command, the user will enter the default mode of
privileged EXEC (level 15).
FR-8
78-11740-02
Examples
In the following example, the user enters privileged EXEC mode using the enable command. The system
prompts the user for a password before allowing access to the privileged EXEC mode. The password is
not printed to the screen. The user then exits back to user EXEC mode using the disable command. Note
that the prompt for user EXEC mode is >, and the prompt for privileged EXEC mode is #.
Router> enable
Password: <letmein>
Router# disable
Router>
Related Commands
Command
Description
disable
Exits from privileged EXEC mode to user EXEC mode, or, if privilege
levels are set, to the specified privilege level.
enable password
FR-9
end
To end the current configuration session and return to privileged EXEC mode, use the end global
configuration command.
end
Syntax Description
Defaults
Command Modes
Global configuration
Command History
Release
Modification
10.0
Usage Guidelines
Note
This command will bring you back to privileged EXEC mode regardless of what configuration mode or
configuration submode you are in.
Examples
In the following example, the end command is used to exit from ALPS ASCU configuration mode and
return to privileged EXEC mode. A show command is used in privileged EXEC mode to verify the
configuration.
Router# configure terminal
Router(config)# interface serial 1:1
Router(config-if)# alps ascu 4B
Router(config-alps-ascu)# end
Router# show interface serial 1:1
Related Commands
Command
Description
exit (global)
FR-10
78-11740-02
exit (EXEC)
To close an active terminal session by logging off the router, use the exit command in EXEC mode.
exit
Syntax Description
Defaults
Command Modes
EXEC
Command History
Release
Modification
10.0
Usage Guidelines
Use the exit (EXEC) command in EXEC mode to exit the active session (log off the device).
Examples
In the following example, the exit (global) command is used to move from global configuration mode to
privileged EXEC mode, the disable command is used to move from privileged EXEC mode to user
EXEC mode, and the exit (EXEC) command is used to log off (exit the active session):
Router(config)# exit
Router# disable
Router> exit
Related Commands
Command
Description
disconnect
Disconnects a line.
end
exit (global)
Exits from the current configuration mode to the next highest configuration
mode.
FR-11
exit (global)
To exit any configuration mode to the next highest mode in the CLI mode hierarchy, use the exit
command in any configuration mode.
exit
Syntax Description
Defaults
Command Modes
Command History
Release
Modification
10.0
Usage Guidelines
The exit command is used in the Cisco IOS CLI to exit from the current command mode to the next
highest command mode in the CLI mode hierarchy.
For example, use the exit command in global configuration mode to return to privileged EXEC mode.
Use the exit command in interface, line, or router configuration mode to return to global configuration
mode. Use the exit command in subinterface configuration mode to return to interface configuration
mode. At the highest level, EXEC mode, the exit command will exit the EXEC mode and disconnect
from the router interface (see the description of the exit (EXEC) command for details).
Examples
The following example displays an exit from the subinterface configuration mode to return to the
interface configuration mode:
Router(config-subif)# exit
Router(config-if)#
The following example displays an exit from the interface configuration mode to return to the global
configuration mode:
Router(config-if)# exit
Router(config)#
Related Commands
Command
Description
disconnect
Disconnects a line.
end
exit (EXEC)
FR-12
78-11740-02
full-help
To get help for the full set of user-level commands, use the full-help line configuration command.
full-help
Syntax Description
Defaults
Disabled
Command Modes
Line configuration
Command History
Release
Modification
10.0
Usage Guidelines
The full-help command enables (or disables) an unprivileged user to see all of the help messages
available. It is used with the show ? command.
Examples
In the following example, the show ? command is used first with full-help disabled. Then full-help is
enabled for the line, and the show ? command is used again to demonstrate the additional help output
that is displayed.
Router> show ?
bootflash
calendar
clock
context
dialer
history
hosts
isdn
kerberos
modemcap
ppp
rmon
sessions
snmp
terminal
users
version
Router> enable
Password:<letmein>
FR-13
translate
ttycap
users
version
vines
vlans
whoami
x25
xns
xremote
.
.
.
Related Commands
Command
Description
help
FR-14
78-11740-02
help
To display a brief description of the help system, enter the help command.
help
Syntax Description
Defaults
Command Modes
Command History
Release
Modification
10.0
Usage Guidelines
Examples
The help command provides a brief description of the context-sensitive help system, which functions as
follows:
To list all commands available for a particular command mode, enter a question mark (?) at the
system prompt.
To obtain a list of commands that begin with a particular character string, enter the abbreviated
command entry immediately followed by a question mark (?). This form of help is called word help,
because it lists only the keywords or arguments that begin with the abbreviation you entered.
To list the keywords and arguments associated with a command, enter a question mark (?) in place
of a keyword or argument on the command line. This form of help is called command syntax help,
because it lists the keywords or arguments that apply based on the command, keywords, and
arguments you have already entered.
In the following example, the help command is used to display a brief description of the help system:
Router# help
Help may be requested at any point in a command by entering
a question mark '?'. If nothing matches, the help list will
be empty and you must backup until entering a '?' shows the
available options.
Two styles of help are provided:
1. Full help is available when you are ready to enter a
command argument (e.g. 'show ?') and describes each possible
argument.
2. Partial help is provided when an abbreviated argument is entered
and you want to know what arguments match the input
(e.g. 'show pr?'.)
FR-15
The following example shows how to use word help to display all the privileged EXEC commands that
begin with the letters co. The letters entered before the question mark are reprinted on the next
command line to allow the user to continue entering the command.
Router# co?
configure connect
Router# co
copy
The following example shows how to use command syntax help to display the next argument of a
partially complete access-list command. One option is to add a wildcard mask. The <cr> symbol
indicates that the other option is to press Return to execute the command without adding any more
keywords or arguments. The characters entered before the question mark are reprinted on the next
command line to allow the user to continue entering the command or to execute that command as it is.
Router(config)# access-list 99 deny 131.108.134.234 ?
A.B.C.D Mask of bits to ignore
<cr>
Router(config)# access-list 99 deny 131.108.134.234
Related Commands
Command
Description
full-help
FR-16
78-11740-02
history
To enable the command history function, use the history line configuration command. To disable the
command history feature, use the no form of this command.
history
no history
Syntax Description
Defaults
Command Modes
Line configuration
Command History
Release
Modification
10.0
Usage Guidelines
The command history feature provides a record of EXEC commands that you have entered. This feature
is particularly useful for recalling long or complex commands or entries, including access lists.
To change the number of command lines that the system will record in its history buffer, use the
history size line configuration command.
The history command enables the history function with the last buffer size specified or, if there was not
a prior setting, with the default of ten lines. The no history command disables the history feature.
The show history EXEC command will list the commands you have entered, but you can also use your
keyboard to display individual commands. Table 4 lists the keys you can use to recall commands from
the command history buffer.
Table 4
History Keys
Key(s)
Ctrl-P or Up Arrow
Functions
1
Ctrl-N or Down Arrow1 Returns to more recent commands in the history buffer after
recalling commands with Ctrl-P or the Up Arrow. Repeat the key
sequence to recall successively more recent commands.
1. The arrow keys function only with ANSI-compatible terminals.
Examples
In the following example, line 4 is configured with a history buffer size of 35 lines:
Router(config)# line 4
FR-17
Related Commands
Command
Description
history size
show history
Lists the commands you have entered in the current EXEC session.
terminal history
Enables the command history feature for the current terminal session or
changes the size of the command history buffer for the current terminal
session.
FR-18
78-11740-02
history size
To change the command history buffer size for a particular line, use the history size line configuration
command. To reset the command history buffer size to ten lines, use the no form of this command.
history size number-of-lines
no history size
Syntax Description
number-of-lines
Defaults
Command Modes
Line configuration
Command History
Release
Modification
10.0
Usage Guidelines
Note
Examples
Specifies the number of command lines that the system will record in its
history buffer. The range is from 0 to 256. The default is ten.
The history size command should be used in conjunction with the history and show history commands.
The history command enables or disables the command history function. The show history command
lists the commands you have entered in the current EXEC session. The number of commands that the
history buffer will show is set by the history size command.
The history size command only sets the size of the buffer; it does not reenable the history feature. If
the no history command is used, the history command must be used to reenable this feature.
The following example displays line 4 configured with a history buffer size of 35 lines:
Router(config)# line 4
Router(config-line)# history size 35
Related Commands
Command
Description
history
show history
Lists the commands you have entered in the current EXEC session.
Enables the command history function for the current terminal session or
changes the size of the command history buffer for the current terminal
session.
FR-19
logout
To close an active terminal session by logging off the router, use the logout command in user EXEC
mode.
logout
Syntax Description
Defaults
Command Modes
User EXEC
Command History
Release
Modification
10.0
Examples
In the following example, the exit (global) command is used to move from global configuration mode to
privileged EXEC mode, the disable command is used to move from privileged EXEC mode to user
EXEC mode, and the logout command is used to log off (exit from the active session):
Router(config)# exit
Router# disable
Router> logout
Related Commands
Command
Description
exit (global)
Exits any configuration mode to the next highest mode in the CLI mode
hierarchy.
FR-20
78-11740-02
menu (EXEC)
To display a preconfigured user menu, use the menu command in user or privileged EXEC mode.
menu menu-name
Syntax Description
menu-name
Command Modes
EXEC
Command History
Release
Modification
10.0
Usage Guidelines
A user menu is a type of user interface where text descriptions of actions to be performed are displayed
to the user. The user can use the menu to select services and functions without having to know the details
of command-line interface (CLI) commands.
Menus can be created for users in global configuration mode, using the commands listed in the Related
Commands section. The description of these commands can be found in the Connection, Menu, and
System Banner Commands chapter of this document.
A menu can be invoked at either the user or privileged EXEC level, but if an item in the menu contains
a privileged EXEC command, the user must be logged in at the privileged level for the command to
succeed.
Examples
Read email
FR-21
Related Commands
Command
Description
menu clear-screen
menu command
menu default
menu line-mode
menu options
menu prompt
menu single-space
menu status-line
Displays a line of status information about the current user at the top of a
menu
menu text
menu title
no menu
FR-22
78-11740-02
more begin
To search the output of any more command, use the more begin command in EXEC mode. This
command begins unfiltered output of the more command with the first line that contains the regular
expression you specify.
more file-url | begin regular-expression
Syntax Description
file-url
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
Usage Guidelines
Modification
11.3 AA
12.0(1)T
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 more command, use the following command at the --More-prompt:
/regular-expression
To filter the remaining output of the more 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.
FR-23
Note
Once you specify a filter for a more command, you cannot specify another filter at a --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.
Examples
The following is partial sample output of the more nvram:startup-config | begin command that begins
unfiltered output with the first line that contain the regular expression ip. At the --More-- prompt, the
user specifies a filter to exclude output lines that contain the regular expression ip.
router# more nvram:startup-config | begin ip
ip subnet-zero
ip domain-name cisco.com
ip name-server 198.92.30.32
ip name-server 171.69.2.132
!
isdn switch-type primary-5ess
.
.
.
interface Ethernet1
ip address 5.5.5.99 255.255.255.0
--More--ip
filtering...
media-type 10BaseT
!
interface Serial0:23
encapsulation frame-relay
no keepalive
dialer string 4001
dialer-group 1
isdn switch-type primary-5ess
no fair-queue
Related Commands
Command
Description
more exclude
more include
Filters more command output so that it displays only lines that contain a
particular regular expression.
show begin
Searches the output of any show command and displays the output from the
first instance of a specified string.
show exclude
show include
Filters show command output so that it displays only lines that contain a
particular regular expression.
FR-24
78-11740-02
more exclude
To filter more command output so that it excludes lines that contain a particular regular expression, use
the more exclude command in EXEC mode.
more file-url | exclude regular-expression
Syntax Description
file-url
regular-expression
Command Modes
EXEC
Command History
Release
Modification
11.3 AA
12.0(1)T
Usage Guidelines
The regular-expression argument is case sensitive and allows for complex matching requirements.
You can specify a new search at any --More-- prompt. To search the remaining output of the more
command, use the following command 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.
Examples
The following is partial sample output of the more nvram:startup-config | exclude command. The use
of | exclude service in the command specifies a filter that excludes lines that contain the regular
expression service. At the --More-- prompt, the user searches for the regular expression Dialer1,
which continues filtered output with the first line that contains Dialer1.
router# more nvram:startup-config | exclude service
!
version 12.0
!
hostname router
!
boot system flash
no logging buffered
!
FR-25
ip subnet-zero
ip domain-name cisco.com
.
.
.
--More-/Dialer1
filtering...
interface Dialer1
no ip address
no ip directed-broadcast
dialer in-band
no cdp enable
Related Commands
Command
Description
more begin
Begins unfiltered output of the more command with the first line that
contains the regular expression you specify.
more include
Filters more command output so that it displays only lines that contain a
particular regular expression.
show begin
Searches the output of any show command and displays the output from the
first instance of a specified string.
show exclude
show include
Filters show command output so that it displays only lines that contain a
particular regular expression.
FR-26
78-11740-02
more include
To filter more command output so that it displays only lines that contain a particular regular expression,
use the more include command in EXEC mode.
more file-url | include regular-expression
Syntax Description
file-url
regular-expression
Command Modes
EXEC
Command History
Release
Modification
11.3 AA
12.0(1)T
Usage Guidelines
The regular-expression argument is case sensitive and allows for complex matching requirements.
You can specify a new search at any --More-- prompt. To search the remaining output of the more
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.
Examples
The following is partial sample output of the more nvram:startup-config | include command. It only
displays lines that contain the regular expression ip.
router# more nvram:startup-config | include ip
ip subnet-zero
ip domain-name cisco.com
ip name-server 198.92.30.32
ip name-server 171.69.2.132
description ip address 172.21.53.199 255.255.255.0
ip address 172.21.53.199 255.255.255.0
FR-27
Related Commands
Command
Description
more begin
Begins unfiltered output of the more command with the first line that
contains the regular expression you specify.
more exclude
show begin
Searches the output of any show command and displays the output from the
first instance of a specified string.
show exclude
show include
Filters show command output so that it displays only lines that contain a
particular regular expression.
FR-28
78-11740-02
show begin
To begin the output of any show command from a specified string, use the show begin command in
EXEC mode.
show any-command | begin regular-expression
Syntax Description
any-command
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 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
Usage Guidelines
Modification
8.3
12.0(1)T
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.
FR-29
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
Examples
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.
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
--More-+Serial
filtering...
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 begin
Begins unfiltered output of the more command with the first line that
contains the regular expression you specify.
more exclude
more include
Filters more command output so that it displays only lines that contain a
particular regular expression.
show exclude
show include
Filters show command output so that it displays only lines that contain a
particular regular expression.
FR-30
78-11740-02
show exclude
To filter show command output so that it excludes lines that contain a particular regular expression, use
the show exclude command in EXEC mode.
show any-command | exclude regular-expression
Syntax Description
any-command
regular-expression
Command Modes
EXEC
Command History
Release
Modification
8.3
12.0(1)T
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
Examples
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.
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
Buffer elements:
398 in free list (500 max allowed)
Public buffer pools:
FR-31
Related Commands
Command
Description
more begin
Begins unfiltered output of the more command with the first line that
contains the regular expression you specify.
more exclude
more include
Filters more command output so that it displays only lines that contain a
particular regular expression.
show begin
Searches the output of any show command and displays the output from the
first instance of a specified string.
show include
Filters show command output so that it displays only lines that contain a
particular regular expression.
FR-32
78-11740-02
show history
To list the commands you have entered in the current EXEC session, use the show history EXEC
command.
show history
Syntax Description
Command Modes
EXEC
Command History
Release
Modification
10.0
Usage Guidelines
The command history feature provides a record of EXEC commands you have entered. The number of
commands that the history buffer will record is determined by the history size line configuration
command or the terminal history size EXEC command.
Table 5 lists the keys and functions you can use to recall commands from the command history buffer.
Table 5
History Keys
Key
Ctrl-P or Up Arrow
Function
1
Ctrl-N or Down Arrow1 Returns to more recent commands in the history buffer after recalling
commands with Ctrl-P or the Up Arrow. Repeat the key sequence to recall
successively more recent commands.
1. The arrow keys function only with ANSI-compatible terminals.
Examples
The following is sample output from the show history command, which lists the commands the user has
entered in EXEC mode for this session:
Router# show history
help
where
show hosts
show history
Router#
FR-33
Related Commands
Command
Description
history size
Enables the command history feature for the current terminal session, or
changes the size of the command history buffer for the current terminal
session.
FR-34
78-11740-02
show include
To filter show command output so that it only displays lines that contain a particular regular expression,
use the show include command in EXEC mode.
show any-command | include regular-expression
Syntax Description
any-command
regular-expression
Command Modes
EXEC
Command History
Release
Modification
8.3
12.0(1)T
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
Examples
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.
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 )
FR-35
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
filtering...
Serial0:13 is down, line protocol is down
Hardware is DSX1
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 begin
Begins unfiltered output of the more command with the first line that
contains the regular expression you specify.
more exclude
more include
Filters more command output so that it displays only lines that contain a
particular regular expression.
show begin
Searches the output of any show command and displays the output from the
first instance of a specified string.
show exclude
FR-36
78-11740-02
terminal editing
To reenable the enhanced editing mode for only the current terminal session, use the terminal editing
EXEC command. To disable the enhanced editing mode on the current line, use the no form of this
command.
terminal editing
terminal no editing
Syntax Description
Defaults
Enabled
Command Modes
EXEC
Command History
Release
Modification
10.0
Usage Guidelines
This command is identical to the editing EXEC mode command, except that it controls (enables or
disables) enhanced editing for only the terminal session you are using. For a description of the available
editing keys, see the description of the editing command in this chapter.
Examples
In the following example, enhanced editing mode is reenabled for only the current terminal session:
Router> terminal editing
Related Commands
Command
Description
editing
FR-37
terminal full-help
To get help for the full set of user-level commands, use the terminal full-help EXEC mode command.
terminal full-help
Syntax Description
Defaults
Disabled
Command Modes
EXEC
Command History
Release
Modification
10.0
Usage Guidelines
The terminal full-help command enables a user to see all of the help messages available from the
terminal. It is used with the show ? command.
Examples
In the following example, the difference between the output of the show ? command before and after
using the terminal full-help command is shown:
Router> show ?
bootflash
calendar
clock
context
dialer
history
hosts
isdn
kerberos
modemcap
ppp
rmon
sessions
snmp
terminal
users
version
FR-38
78-11740-02
appletalk
arp
async
bootflash
bridge
bsc
bstun
buffers
calendar
cdp
clns
clock
cls
cmns
compress
.
.
.
x25
xns
xremote
Related Commands
AppleTalk information
ARP table
Information on terminal lines used as router interfaces
Boot Flash information
Bridge Forwarding/Filtering Database [verbose]
BSC interface information
BSTUN interface information
Buffer pool statistics
Display the hardware calendar
CDP information
CLNS network information
Display the system clock
DLC user information
Connection-Mode networking services (CMNS) information
Show compression statistics.
X.25 information
XNS information
XRemote statistics
Command
Description
full-help
help
FR-39
terminal history
To enable the command history feature for the current terminal session, use the terminal history
command in user EXEC mode or privileged EXEC mode. To disable the command history feature, use
the no form of this command.
terminal history
terminal no history
Syntax Description
Defaults
Command Modes
EXEC
Command History
Release
Modification
10.0
Usage Guidelines
The history feature provides a record of commands you have entered. This feature is particularly useful
for recalling long or complex commands or entries for the purposes of modifying them slightly and
reexecuting them.
The terminal history command enables the command history feature with the default buffer size or the
last buffer size specified using the terminal history size command.
Table 6 lists the keys and functions you can use to recall commands from the history buffer.
Table 6
History Keys
Key(s)
Ctrl-P or Up Arrow
Function
1
Ctrl-N or Down Arrow1 Returns to more recent commands in the history buffer after recalling
commands with Ctrl-P or the Up Arrow. Repeat the key sequence to recall
successively more recent commands.
1. The arrow keys function only with ANSI-compatible terminals.
Examples
In the following example, the command history feature is disabled for the current terminal session:
Router> terminal no history
FR-40
78-11740-02
Related Commands
Command
Description
history
show history
Lists the commands you have entered in the current EXEC session.
Sets the size of the history buffer for the command history feature for the
current terminal session.
FR-41
Syntax Description
number-of-lines
Defaults
Command Modes
EXEC
Command History
Release
Modification
10.0
Usage Guidelines
Number of command lines that the system will record in its history
buffer. The range is from 0 to 256. The default is 10.
The history feature provides a record of commands you have entered. This feature is particularly useful
for recalling long or complex commands or entries for the purposes of modifying them slightly and
reissuing them.
The terminal history size command enables the command history feature and sets the command history
buffer size. The terminal no history size command resets the buffer size to the default of 10 command
lines.
Table 6 lists the keys and functions you can use to recall commands from the history buffer. When you
use these keys, the commands recalled will be from EXEC mode if you are in EXEC mode, or from all
configuration modes if you are in any configuration mode.
Table 7
History Keys
Key
Ctrl-P or Up Arrow
Function
1
Ctrl-N or Down Arrow1 Returns to more recent commands in the history buffer after recalling
commands with Ctrl-P or the Up Arrow. Repeat the key sequence to
recall successively more recent commands.
1. The arrow keys function only with ANSI-compatible terminals.
FR-42
78-11740-02
In EXEC mode, you can also use the show history command to show the contents of the command
history buffer.
To check the current settings for the command history feature on your line, use the show line command.
Examples
In the following example, the number of command lines recorded is set to 15 for the current terminal
session. The user then checks to see what line he/she is connected to using the show users command.
The user uses this line information to issue the show line command. (In this example, the user uses the
show begin option in the show line command to start the output at the Editing is enabled/disabled
line.)
Router# terminal history size 15
Router# show users
Line
User
Host(s)
Idle
Location
* 50 vty 0
admin
idle
00:00:00
! the * symbol indicates the active terminal session for the user (line 50)
Router# show line 50 | begin Editing
Editing is enabled.
! the following line shows the history settings for the line
History is enabled, history size is 15.
DNS resolution in show commands is enabled
Full user help is disabled
Allowed transports are telnet. Preferred is none.
No output characters are padded
No special data dispatching characters
Related Commands
Command
Description
history
show begin
Searches the output of any show command and displays the output from the
first instance of a specified string.
show history
Lists the commands you have entered in the current EXEC session.
terminal history
Enables the command history feature for the current terminal session.
FR-43
FR-44
78-11740-02
FR-45
setup
To enter Setup mode, use the setup privileged EXEC command.
setup
Syntax Description
Command Modes
Privileged EXEC
Command History
Release
Modification
11.1
Usage Guidelines
Setup mode gives you the option of configuring your system without using the Cisco IOS 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 Setup 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 Setup, you should have the following information so that you can configure the system
properly:
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.
FR-46
78-11740-02
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 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:
Router# setup
--- 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
Ethernet0
Serial0
Serial1
IP-Address
172.16.72.2
unassigned
172.16.72.2
OK?
YES
YES
YES
Method
manual
not set
not set
Status
up
administratively down
up
Protocol
up
down
up
FR-47
FR-48
78-11740-02
FR-49
line 1 16
arap enable
autoselect
!
! Turn off IPX to prevent network conflicts.
interface Ethernet0
no ipx network
interface Serial0
no ipx network
interface Serial1
no ipx network
!
interface Ethernet0
ip address 172.16.72.2 255.255.255.0
appletalk cable-range 1-1 1.204
appletalk zone Sales
ipx network 1
no mop enabled
!
interface Serial0
no shutdown
no ip address
ip unnumbered Ethernet0
appletalk cable-range 3-3
appletalk zone ZZ Serial
ipx network 3
no mop enabled
!
interface Serial1
no ip address
ip unnumbered Ethernet0
appletalk cable-range 2-2 2.2
appletalk zone ZZ Serial
ipx network 2
no mop enabled
!
Interface Async1
ipx network 4
ip unnumbered Ethernet0
peer default ip address 172.16.72.4
async mode interactive
!
Interface Async2
ipx network 5
ip unnumbered Ethernet0
peer default ip address 172.16.72.5
async mode interactive
!
Interface Async3
ipx network 6
ip unnumbered Ethernet0
peer default ip address 172.16.72.6
async mode interactive
!
Interface Async4
ipx network 7
ip unnumbered Ethernet0
peer default ip address 172.16.72.7
async mode interactive
async dynamic address
!
Interface Async5
ipx network 8
ip unnumbered Ethernet0
FR-50
78-11740-02
172.16.72.8
172.16.72.9
172.16.72.10
172.16.72.11
172.16.72.12
172.16.72.13
172.16.72.14
172.16.72.15
172.16.72.16
172.16.72.17
172.16.72.18
FR-51
ipx network 13
ip unnumbered Ethernet0
peer default ip address 172.16.72.19
async mode interactive
!
router igrp 15
network 172.16.0.0
!
end
Use this configuration? [yes/no]: yes
Building configuration...
Use the enabled mode 'configure' command to modify this configuration.
Router#
Related Commands
Command
Description
erase nvram:
show running-config
show startup-config
Displays the startup configuration file. Command alias for the more
system:startup-config command.
show version
FR-52
78-11740-02
FR-53
activation-character
To define the character you enter at a vacant terminal to begin a terminal session, use the
activation-character line configuration command. To make any character activate a terminal, use the
no form of this command.
activation-character ascii-number
no activation-character
Syntax Description
ascii-number
Defaults
Command Modes
Line configuration
Command History
Release
Modification
10.0
Usage Guidelines
Note
Examples
See the ASCII Character Set and Hex Values appendix for a list of ASCII characters.
If you are using the autoselect function, set the activation character to the default, Return, and
exec-character-bits to 7. If you change these defaults, the application will not recognize the activation
request.
The following example sets the activation character for the console to Delete, which is decimal character
127:
Router(config)# line console
Router(config-line)# activation-character 127
FR-54
78-11740-02
autobaud
To set the line for automatic baud rate detection (autobaud), use the autobaud line configuration
command. To disable automatic baud detection, use the no form of this command.
autobaud
no autobaud
Syntax Description
Defaults
Command Modes
Line configuration
Command History
Release
Modification
10.0
Usage Guidelines
Note
Examples
The autobaud detection supports a range from 300 to 19200 baud. A line set for autobaud cannot be used
for outgoing connections, nor can you set autobaud capability on a line using 19200 baud when the parity
bit is set (because of hardware limitations).
Automatic baud rate detection must be disabled by using the no autobaud command prior to entering
the rxspeed, speed, or txspeed commands.
In the following example, the auxiliary port is configured for autobaud detection:
Router(config)# line aux
Router(config-line)# autobaud
FR-55
buffer-length
To specify the maximum length of the data stream to be forwarded, use the buffer-length command in
line configuration mode. To restore the default setting, use the no form of this command.
buffer-length length
no buffer-length
Syntax Description
length
Defaults
1536 bytes
Command Modes
Line configuration
Command History
Release
Modification
12.1
Specifies the length of the buffer in bytes. Valid values for the length argument
range from 16 to 1536. The default buffer length is 1536 bytes.
Usage Guidelines
The buffer-length command configures the size of the forwarded data stream. The higher the value used
for the length argument is, the longer the delay between data transmissions will be. Configuring a smaller
buffer length can prevent connections from timing out inappropriately.
Examples
FR-56
78-11740-02
databits
To set the number of data bits per character that are interpreted and generated by the router hardware,
use the databits line configuration command. To restore the default value, use the no form of the
command.
databits {5 | 6 | 7 | 8}
no databits
Syntax Description
Defaults
Command Modes
Line configuration
Command History
Release
Modification
10.0
Usage Guidelines
Examples
The databits line configuration command can be used to mask the high bit on input from devices that
generate 7 data bits with parity. If parity is being generated, specify 7 data bits per character. If no parity
generation is in effect, specify 8 data bits per character. The other keywords are supplied for
compatibility with older devices and generally are not used.
The following example sets the number of data bits per character to seven on line 4:
Router(config)# line 4
Router(config-line)# databits 7
Related Commands
Command
Description
data-character-bits
Sets the number of data bits per character that are interpreted and
generated by the Cisco IOS software.
terminal databits
Changes the number of data bits per character for the current
terminal line for this session.
terminal data-character-bits
Sets the number of data bits per character that are interpreted and
generated by the Cisco IOS software for the current line and session.
FR-57
data-character-bits
To set the number of data bits per character that are interpreted and generated by the Cisco IOS software,
use the data-character-bits line configuration command. To restore the default value, use the no form
of this command.
data-character-bits {7 | 8}
no data-character-bits
Syntax Description
Defaults
Command Modes
Line configuration
Command History
Release
Modification
10.0
Usage Guidelines
The data-character-bits line configuration command is used primarily to strip parity from X.25
connections on routers with the protocol translation software option. The data-character-bits line
configuration command does not work on hard-wired lines.
Examples
The following example sets the number of data bits per character to seven on virtual terminal line 1:
Router(config)# line vty 1
Router(config-line)# data-character-bits 7
Related Commands
Command
Description
terminal data-character-bits
Sets the number of data bits per character that are interpreted and
generated by the Cisco IOS software for the current line and session.
FR-58
78-11740-02
default-value exec-character-bits
To define the EXEC character width for either 7 bits or 8 bits, use the default-value exec-character-bits
global configuration command. To restore the default value, use the no form of this command.
default-value exec-character-bits {7 | 8}
no default-value exec-character-bits
Syntax Description
Defaults
Command Modes
Global configuration
Command History
Release
Modification
10.0
Usage Guidelines
Configuring the EXEC character width to 8 bits allows you to add graphical and international characters
in banners, prompts, and so on. However, setting the EXEC character width to 8 bits can also cause
failures. If a user on a terminal that is sending parity enters the help command, an unrecognized
command message appears because the system is reading all 8 bits, although the eighth bit is not needed
for the help command.
Examples
The following example selects the full 8-bit ASCII character set for EXEC banners and prompts:
Router(config)# default-value exec-character-bits 8
Related Commands
Command
Description
default-value special-character-bits
exec-character-bits
length
terminal exec-character-bits
terminal special-character-bits
FR-59
default-value special-character-bits
To configure the flow control default value from a 7-bit width to an 8-bit width, use the default-value
special-character-bits global configuration command. To restore the default value, use the no form of
this command.
default-value special-character-bits {7 | 8}
no default-value special-character-bits
Syntax Description
Defaults
Command Modes
Global configuration
Command History
Release
Modification
10.0
Usage Guidelines
Configuring the special character width to 8 bits allows you to add graphical and international characters
in banners, prompts, and so on.
Examples
The following example selects the full 8-bit special character set:
Router(config)# default-value special-character-bits 8
Related Commands
Command
Description
default-value exec-character-bits
exec-character-bits
length
terminal exec-character-bits
terminal special-character-bits
FR-60
78-11740-02
disconnect-character
To define a character to disconnect a session, use the disconnect-character line configuration
command. To remove the disconnect character, use the no form of this command.
disconnect-character ascii-number
no disconnect-character
Syntax Description
ascii-number
Defaults
Command Modes
Line configuration
Command History
Release
Modification
10.0
Usage Guidelines
See theASCII Character Set and Hex Values appendix for a list of ASCII characters.
The Break character is represented by zero; NULL cannot be represented.
To use the session-disconnect character in normal communications, precede it with the escape character.
Examples
The following example defines the disconnect character for virtual terminal line 4 as Escape, which is
decimal character 27:
Router(config)# line vty 4
Router(config-line)# disconnect-character 27
FR-61
dispatch-character
To define a character that causes a packet to be sent, use the dispatch-character line configuration
command. To remove the definition of the specified dispatch character, use the no form of this command.
dispatch-character ascii-number1 [ascii-number2 . . . ascii-number]
no dispatch-character ascii-number1 [ascii-number2 . . . ascii-number]
Syntax Description
ascii-number1
ascii-number2 . . . ascii-number
Defaults
Command Modes
Line configuration
Command History
Release
Modification
10.0
Usage Guidelines
See theASCII Character Set and Hex Values appendix for a list of ASCII characters.
The dispatch-character command defines one or more dispatch characters that cause a packet to be sent
even if the dispatch timer has not expired. Use of a dispatch character causes the Cisco IOS software to
attempt to buffer characters into larger-sized packets for transmission to the remote host.
Enable the dispatch-character command from the session that initiates the connection, not from the
incoming side of a streaming Telnet session.
This command can take multiple arguments, so you can define any number of characters as dispatch
characters.
Examples
The following example defines the Return character (decimal 13) as the dispatch character for vty line 4:
Router(config)# line vty 4
Router(config-line)# dispatch-character 13
Related Commands
Command
Description
dispatch-machine
dispatch-timeout
FR-62
78-11740-02
Command
Description
state-machine
terminal dispatch-character
FR-63
dispatch-machine
To specify an identifier for a TCP packet dispatch state machine on a particular line, use the
dispatch-machine line configuration command. To disable a state machine on a particular line, use the
no form of this command.
dispatch-machine name
no dispatch-machine
Syntax Description
name
Defaults
Command Modes
Line configuration
Command History
Release
Modification
10.0
Usage Guidelines
When the dispatch-timeout command is specified, a packet being built will be sent when the timer
expires, and the state will be reset to zero.
Any dispatch characters specified using the dispatch-character command are ignored when a state
machine is also specified.
If a packet becomes full, it will be sent regardless of the current state, but the state will not be reset. The
packet size depends on the traffic level on the asynchronous line and the dispatch-timeout value. There
is always room for 60 data bytes. If the dispatch-timeout value is greater than or equal to
100 milliseconds, a packet size of 536 (data bytes) is allocated.
Examples
The following example specifies the name linefeed for the state machine:
Router(config)# state-machine linefeed 0 0 9 0
Router(config)# state-machine linefeed 0 11 255 0
Router(config)# state-machine linefeed 0 10 10 transmit
Router(config)# line 1
Router(config-line)# dispatch-machine linefeed
Related Commands
Command
Description
dispatch-character
dispatch-timeout
state-machine
Specifies the transition criteria for the state of a particular state machine.
FR-64
78-11740-02
dispatch-timeout
To set the character dispatch timer, use the dispatch-timeout line configuration command. To remove
the timeout definition, use the no form of this command.
dispatch-timeout milliseconds
no dispatch-timeout
Syntax Description
milliseconds
Defaults
Command Modes
Line configuration
Command History
Release
Modification
10.0
Usage Guidelines
Use this command to increase the processing efficiency for the remote host.
The dispatch-timeout line configuration command causes the software to buffer characters into packets
for transmission to the remote host. The Cisco IOS software sends a packet a specified amount of time
after the first character is put into the buffer. You can use the dispatch-timeout and dispatch-character
line configuration commands together. In this case, the software dispatches a packet each time the
dispatch character is entered, or after the specified dispatch timeout interval, depending on which
condition is met first.
Note
Examples
The system response time might appear intermittent if the timeout interval is greater than
100 milliseconds and remote echoing is used. For lines with a reverse-Telnet connection, use a
dispatch-timeout value less than 10 milliseconds.
The following example sets the dispatch timer to 80 milliseconds for vty lines 0 through 4:
Router(config)# line vty 0 4
Router(config-line)# dispatch-timeout 80
FR-65
Related Commands
Command
Description
dispatch-character
dispatch-machine
state-machine
terminal dispatch-timeout
FR-66
78-11740-02
escape-character
To define a system escape character, use the escape-character line configuration command. To set the
escape character to Break, use the no or default form of this command.
escape-character {break | char | default | none | soft}
no escape-character [soft]
default escape-character [soft]
Syntax Description
Defaults
break
Sets the escape character to Break. Note that the Break key should not
be used as an escape character on a console terminal.
char
default
none
soft
The default escape key sequence is Ctrl-Shift-6 (Ctrl-^) or Ctrl-Shift-6, X (^^X). The X is generally only
required for modem connections.
The default escape-character command sets the escape character to Break (the default setting for Break
is Ctrl-C).
Command Modes
Line configuration
Command History
Release
Usage Guidelines
Modification
10.0
11.3
See the ASCII Character Set and Hex Values appendix for a list of ASCII characters and their
numerical representation.
The escape character (or key sequence) suspends any actively running processes and returns you to
privileged EXEC mode or, if a menu is being used , to the system menu interface. The escape character
is used for interrupting or aborting a process started by previously executed command. Examples of
processes from which you can escape include Domain-Name lookup, ping, trace, and Telnet sessions
initiated from the device to which you are connected.
To view the current setting of the escape sequence for a line, use the show line command followed by
the specific line identifier (for example, show line 0, or show line console). The default escape sequence
for a line is often displayed as ^^X . The first caret symbol represents the Control (Ctrl) key, the second
caret symbol is literal (Shift-6), and the X is literal (for most systems, the X is not required).
FR-67
To set the escape key for the active terminal line session, use the terminal escape-character command.
The Break key cannot be used as an escape character on a console terminal because the Cisco IOS
software interprets Break as an instruction to halt the system. Depending upon the configuration register
setting, break commands issued from the console line either will be ignored or cause the server to shut
down.
To send an escape sequence over a Telnet connection, press Ctrl-Shift-6 twice.
The escape-character soft form of this command defines a character or character sequence that will
cause the system to wait until pending input is processed before suspending the current session. This
option allows you to program a key sequence to perform multiple actions, such as using the F1 key to
execute a command, then execute the escape function after the first command is executed.
The following restrictions apply when using the soft keyword:
Examples
The soft escape character cannot be the same as the generic Cisco escape character, Break, or the
characters b, d, n, or s.
The soft escape character should be an ASCII value from 1 to 127. Do not use the number 30.
The following example sets the escape character for the console line to the keyboard entry Ctrl-P, which
is represented by the ASCII decimal value of 16:
Router(config)# line console
Router(config-line)# escape-character 16
The following example sets the escape character for line 1 to !, which is represented in the configuration
file as the ASCII number 33:
Router(config)# line 1
Router(config-line)# escape-character !
Router(config-line)# end
Router# show running-config
Building configuration...
.
.
.
line 1
autoselect during-login
autoselect ppp
modem InOut
transport preferred none
transport output telnet
escape-character 33
.
.
.
Related Commands
Command
Description
show line
terminal escape-character
Sets the escape character for the current terminal line for the current
session.
FR-68
78-11740-02
exec-character-bits
To configure the character widths of EXEC and configuration command characters, use the
exec-character-bits line configuration command. To restore the default value, use the no form of this
command.
exec-character-bits {7 | 8}
no exec-character-bits
Syntax Description
Selects the full 8-bit character set for use of international and
graphical characters in banner messages, prompts, and so on.
Defaults
Command Modes
Line configuration
Command History
Release
Modification
10.0
Usage Guidelines
Note
Examples
Setting the EXEC character width to 8 allows you to use special graphical and international characters
in banners, prompts, and so on. However, setting the EXEC character width to 8 bits can cause failures.
If a user on a terminal that is sending parity enters the help command, an unrecognized command
message appears because the system is reading all 8 bits, and the eighth bit is not needed for the help
command.
If you are using the autoselect function, set the activation character to the default (Return) and the
value for exec-character-bits to 7. If you change these defaults, the application will not recognize
the activation request.
The following example enables full 8-bit international character sets, except for the console, which is an
ASCII terminal. It illustrates use of the default-value exec-character-bits global configuration
command and the exec-character-bits line configuration command.
Router(config)# default-value exec-character-bits 8
Router(config)# line 0
Router(config-line)# exec-character-bits 7
FR-69
Related Commands
Command
Description
default-value exec-character-bits
default-value
special-character-bits
length
terminal exec-character-bits
terminal special-character-bits
FR-70
78-11740-02
hold-character
To define the local hold character used to pause output to the terminal screen, use the hold-character
line configuration command. To restore the default, use the no form of this command.
hold-character ascii-number
no hold-character
Syntax Description
ascii-number
Defaults
Command Modes
Line configuration
Command History
Release
Modification
10.0
Usage Guidelines
The Break character is represented by zero; NULL cannot be represented. To continue the output, enter
any character after the hold character. To use the hold character in normal communications, precede it
with the escape character. See the ASCII Character Set appendix for a list of ASCII characters.
Examples
The following example sets the hold character to Ctrl-S, which is ASCII decimal character 19:
Router(config)# line 8
Router(config-line)# hold-character 19
Related Commands
Command
Description
terminal hold-character
FR-71
insecure
To configure a line as insecure, use the insecure line configuration command. To disable this feature,
use the no form of this command.
insecure
no insecure
Syntax Description
Defaults
Disabled
Command Modes
Line configuration
Command History
Release
Modification
10.0
Usage Guidelines
Use this command to identify a modem line as insecure for DEC local area transport (LAT)
classification.
Examples
FR-72
78-11740-02
length
To set the terminal screen length, use the length line configuration command. To restore the default
value, use the no form of this command.
length screen-length
no length
Syntax Description
screen-length
Defaults
Command Modes
Line configuration
Command History
Release
Modification
10.0
Usage Guidelines
The Cisco IOS software uses the value of this command to determine when to pause during
multiple-screen output. Not all commands recognize the configured screen length. For example, the
show terminal command assumes a screen length of 24 lines or more.
Examples
In the following example, the terminal type is specified and the screen pause function is disabled for the
terminal connection on line 6:
Router(config)# line 6
Router(config-line)# terminal-type VT220
Router(config-line)# length 0
Related Commands
Command
Description
terminal length
Sets the number of lines on the current terminal screen for the current
session.
FR-73
location
To provide a description of the location of a serial device, use the location line configuration command.
To remove the description, use the no form of this command.
location text
no location
Syntax Description
text
Defaults
Command Modes
Line configuration
Command History
Release
Modification
10.0
Location description.
Usage Guidelines
The location command enters information about the device location and status. Use the show users all
EXEC command to display the location information.
Examples
In the following example, the location description for the console line is given as Building 3,
Basement:
Router(config)# line console
Router(config-line)# location Building 3, Basement
FR-74
78-11740-02
lockable
To enable use of the lock EXEC command, use the lockable line configuration command. To reinstate
the default (the terminal session cannot be locked), use the no form of this command.
lockable
no lockable
Syntax Description
Defaults
Sessions on the line are not lockable (the lock EXEC command has no effect).
Command Modes
Line configuration
Command History
Release
Modification
10.0
Usage Guidelines
This command enables use of temporary terminal locking, which is executed using the lock EXEC
command. Terminal locking allows a user keep the current session open while preventing access by other
users.
Examples
In the following example, the terminal connection is configured as lockable, then the current connection
is locked:
Router# configure terminal
Router(config)# line console 0
Router(config-line)# lockable
Router(config)# ^Z
Router# lock
Password: <password>
Again: <password>
Locked
Password: <password>
Router#
Related Commands
Command
Description
lock
FR-75
logout-warning
To warn users of an impending forced timeout, use the logout-warning line configuration command. To
restore the default, use the no form of this command.
logout-warning [seconds]
logout-warning
Syntax Description
seconds
Defaults
Command Modes
Line configuration
Command History
Release
Modification
10.3
Usage Guidelines
This command notifies the user of an impending forced timeout (set using the absolute-timeout
command).
Examples
In the following example, a logout warning is configured on line 5 with a countdown value of 30 seconds:
Router(config)# line 5
Router(config-line)# logout-warning 30
Related Commands
Command
Description
absolute-timeout
Sets the interval for closing user connections on a specific line or port.
session-timeout
Sets the interval for closing the connection when there is no input or output
traffic.
FR-76
78-11740-02
notify
To enable terminal notification about pending output from other Telnet connections, use the notify line
configuration command. To disable notifications, use the no form of this command.
notify
no notify
Syntax Description
Defaults
Disabled
Command Modes
Line configuration
Command History
Release
Modification
10.0
Usage Guidelines
This command sets a line to inform a user that has multiple, concurrent Telnet connections when output
is pending on a connection other than the current one.
Examples
In the following example, notification of pending output from connections is enabled on virtual terminal
lines 0 to 4:
Router(config)# line vty 0 4
Router(config-line)# notify
Related Commands
Command
Description
terminal notify
FR-77
padding
To set the padding on a specific output character, use the padding line configuration command. To
remove padding for the specified output character, use the no form of this command.
padding ascii-number count
no padding ascii-number
Syntax Description
ascii-number
count
Defaults
No padding
Command Modes
Line configuration
Command History
Release
Modification
10.0
Usage Guidelines
Use this command when the attached device is an old terminal that requires padding after certain
characters (such as ones that scrolled or moved the carriage). See the ASCII Character Set and Hex
Values appendix for a list of ASCII characters.
Examples
In the following example, the Return (decimal character 13) is padded with 25 NULL bytes on the
console line:
Router(config)# line console
Router(config-line)# padding 13 25
Related Commands
Command
Description
terminal padding
Changes the character padding on a specific output character for the current
session.
FR-78
78-11740-02
parity
To define generation of a parity bit, use the parity line configuration command. To specify no parity, use
the no form of this command.
parity {none | even | odd | space | mark}
no parity
Syntax Description
none
even
Even parity.
odd
Odd parity.
space
Space parity.
mark
Mark parity.
Defaults
No parity.
Command Modes
Line configuration
Command History
Release
Modification
10.0
Usage Guidelines
Communication protocols provided by devices such as terminals and modems will sometimes require a
specific parity bit setting. Refer to the documentation for your device to determine required parity
settings.
Examples
Related Commands
Command
Description
terminal parity
Defines the generation of the parity bit for the current for the current session
and line.
FR-79
printer
To configure a printer and assign a server tty line (or lines) to it, use the printer global configuration
command. To disable printing on a tty line, use the no form of this command.
printer printer-name {line number | rotary number} [newline-convert | formfeed]
no printer
Syntax Description
printer-name
Printer name.
line number
rotary number
newline-convert
formfeed
Defaults
Command Modes
Global configuration
Command History
Release
Modification
10.3
Usage Guidelines
This command enables you to configure a printer for operations and assign either a single tty line or a
group of tty lines to it. To make multiple printers available through the same printer name, specify the
number of a rotary group.
In addition to configuring the printer with the printer command, you must modify the file /etc/printcap
on your UNIX system to include the definition of the remote printer in the Cisco IOS software. Refer to
the Release 12.2 Cisco IOS Configuration Fundamentals Configuration Guide for additional
information.
Use the optional newline-convert keyword in UNIX environments that cannot handle single-character
line terminators. This converts newline characters to a carriage-return, linefeed sequence. Use the
formfeed keyword when using the line printer daemon (lpd) protocol to print and your system is unable
to separate individual output jobs with a form feed (page eject). You can enter the newline-convert and
formfeed keywords together and in any order.
Examples
In the following example a printer named printer1 is configured and output is assigned to tty line 4:
Router(config)# printer printer1 line 4
FR-80
78-11740-02
Related Commands
Command
Description
clear line
FR-81
private
To save user EXEC command changes between terminal sessions, use the private line configuration
command. To restore the default condition, use the no form of this command.
private
no private
Syntax Description
Defaults
User-set configuration options are cleared with the exit EXEC command or when the interval set with
the exec-timeout line configuration command has passed.
Command Modes
Line configuration
Command History
Release
Modification
10.0
Usage Guidelines
This command ensures that the terminal parameters set by the user remain in effect between terminal
sessions. This behavior is desirable for terminals in private offices.
Examples
In the following example, line 15 (in this example, vty 1) is configured to keep all user-supplied settings
at system restarts:
Router(config)# line 15
Router(config-line)# private
Related Commands
Command
Description
exec-timeout
Sets the interval that the EXEC command interpreter waits until user input
is detected.
exit
FR-82
78-11740-02
show whoami
To display information about the terminal line of the current user, including host name, line number, line
speed, and location, use the show whoami EXEC command.
show whoami [text]
Syntax Description
text
Command Modes
EXEC
Command History
Release
Modification
10.0
Usage Guidelines
If text is included as an argument in the command, that text is displayed as part of the additional data
about the line.
To prevent the information from being lost if the menu display clears the screen, this command always
displays a More prompt before returning. Press the space bar to return to the prompt.
Examples
The following example is sample output from the show whoami command:
Router> show whoami
--More-Router>
FR-83
special-character-bits
To configure the number of data bits per character for special characters such as software flow control
characters and escape characters, use the special-character-bits line configuration command. To restore
the default value, use the no form of this command.
special-character-bits {7 | 8}
no special-character-bits
Syntax Description
Defaults
Command Modes
Line configuration
Command History
Release
Modification
10.0
Usage Guidelines
Setting the special character bits to 8 allows you to use twice as many special characters as with the 7-bit
ASCII character set. The special characters affected by this setting are the escape, hold, stop, start,
disconnect, and activation characters.
Examples
The following example allows the full 8-bit international character set for special characters on line 5:
Router(config)# line 5
Router(config-line)# special-character-bits 8
Related Commands
Command
Description
default-value exec-character-bits
default-value
special-character-bits
exec-character-bits
terminal exec-character-bits
terminal special-character-bits
FR-84
78-11740-02
state-machine
To specify the transition criteria for the state of a particular state machine, use the state-machine global
configuration command. To remove a particular state machine from the configuration, use the no form
of this command.
state-machine name state first-character last-character [nextstate | transmit]
no state-machine name
Syntax Description
name
Name for the state machine (used in the dispatch-machine line configuration
command). The user can specify any number of state machines, but each line can
have only one state machine associated with it.
state
State being modified. There are a maximum of eight states per state machine.
Lines are initialized to state 0 and return to state 0 after a packet is transmitted.
first-character
last-character
nextstate
transmit
(Optional) Causes the packet to be transmitted and the state machine to be reset
to state 0. Recurring characters that have not been explicitly defined to have a
particular action return the state machine to state 0.
Defaults
Command Modes
Global configuration
Command History
Release
Modification
10.0
Usage Guidelines
This command is paired with the dispatch-machine line configuration command, which defines the line
on which the state machine is effective.
Examples
In the following example a dispatch machine named function is configured to ensure that the function
key characters on an ANSI terminal are kept in one packet. Because the default in the example is to
remain in state 0 without sending anything, normal key signals are sent immediately.
Router(config)# line 1 20
Router(config-line)# dispatch-machine function
Router(config-line)# exit
FR-85
Related Commands
Command
Description
dispatch-character
dispatch-machine
dispatch-timeout
FR-86
78-11740-02
stopbits
To set the number of the stop bits transmitted per byte, use the stopbits line configuration command. To
restore the default value, use the no form of this command.
stopbits {1 | 1.5 | 2}
no stopbits
Syntax Description
1.5
Defaults
Command Modes
Line configuration
Command History
Release
Modification
10.0
Usage Guidelines
Communication protocols provided by devices such as terminals and modems often require a specific
stop-bit setting.
Examples
In the following example, the stop bits transmitted per byte are changed from the default of two stop bits
to one stop bit as a performance enhancement for line 4:
Router(config)# line 4
Router(config-line)# stopbits 1
Related Commands
Command
Description
terminal stopbits
Changes the number of stop bits sent per byte by the current terminal line
during an active session.
FR-87
terminal databits
To change the number of data bits per character for the current terminal line for this session, use the
terminal databits EXEC command.
terminal databits {5 | 6 | 7 | 8}
Syntax Description
Defaults
Command Modes
EXEC
Command History
Release
Modification
10.0
Usage Guidelines
Communication protocols provided by devices such as terminals and modems often require a specific
data bit setting. The terminal databits command can be used to mask the high bit on input from devices
that generate 7 data bits with parity. If parity is being generated, specify 7 data bits per character. If no
parity generation is in effect, specify 8 data bits per character. The other keywords (5 and 6) are supplied
for compatibility with older devices and are generally not used.
Examples
In the following example, the databits per character is changed to seven for the current session:
Router# terminal databits 7
Related Commands
Command
Description
databits
Sets the number of data bits per character that are interpreted and generated
by the router hardware.
terminal parity
Defines the generation of the parity bit for the current terminal line and
session.
FR-88
78-11740-02
terminal data-character-bits
To set the number of data bits per character that are interpreted and generated by the Cisco IOS software
for the current line and session, use the terminal data-character-bits EXEC command.
terminal data-character-bits {7 | 8}
Syntax Description
Defaults
Command Modes
EXEC
Command History
Release
Modification
10.0
Usage Guidelines
This command is used primarily to strip parity from X.25 connections on routers with the protocol
translation software option. The terminal data-character-bits command does not work on hard-wired
lines.
Examples
The following example sets the data bits per character to seven on the current line:
Router# terminal data-character-bits 7
Related Commands
Command
Description
data-character-bits
Sets the number of data bits per character that are interpreted and generated
by the Cisco IOS software.
FR-89
terminal dispatch-character
To define a character that causes a packet to be sent for the current session, use the
terminal dispatch-character EXEC command.
terminal dispatch-character ascii-number [ascii-number2 . . . ascii-number]
Syntax Description
ascii-number
ascii-number2 . . .
ascii-number
Command Modes
EXEC
Command History
Release
Modification
10.0
Usage Guidelines
At times, you might want to queue up a string of characters until they fill a complete packet and then
transmit the packet to a remote host. This can make more efficient use of a line, because the access server
or router normally dispatches each character as it is entered.
Examples
The following example defines the characters Ctrl-D (ASCII decimal character 4) and Ctrl-Y (ASCII
decimal character 25) as the dispatch characters:
Router# terminal dispatch-character 4 25
Related Commands
Command
Description
dispatch-character
FR-90
78-11740-02
terminal dispatch-timeout
To set the character dispatch timer for the current terminal line for the current session, use the
terminal dispatch-timeout EXEC command.
terminal dispatch-timeout milliseconds
Syntax Description
milliseconds
Command Modes
EXEC
Command History
Release
Modification
10.0
Usage Guidelines
Integer that specifies the number of milliseconds that the router waits after it puts
the first character into a packet buffer before sending the packet. During this
interval, more characters can be added to the packet, which increases the
processing efficiency of the remote host.
Use this command to increase the processing efficiency of the remote host.
The dispatch-timeout line configuration command causes the software to buffer characters into packets
for transmission to the remote host. The Cisco IOS software sends a packet a specified amount of time
after the first character is put into the buffer. You can use the terminal dispatch-timeout and terminal
dispatch-character line configuration commands together. In this case, the software dispatches a packet
each time the dispatch character is entered, or after the specified dispatch timeout interval, depending
on which condition is met first.
Note
Examples
The router response time might appear intermittent if the timeout interval is greater than
100 milliseconds and remote echoing is used.
Related Commands
Command
Description
dispatch-timeout
Sets the character dispatch timer for a specified line or group of lines.
FR-91
terminal download
To temporarily set the ability of a line to act as a transparent pipe for file transfers for the current session,
use the terminal download EXEC command.
terminal download
Syntax Description
Defaults
Disabled
Command Modes
EXEC
Command History
Release
Modification
10.0
Usage Guidelines
Examples
You can use this feature to run a program such as KERMIT, XMODEM, or CrossTalk that downloads a
file across an access server or router line. This command configures the terminal line to send data and is
equivalent to entering all the following commands:
terminal databits 8
FR-92
78-11740-02
terminal escape-character
To set the escape character for the current terminal line for the current session, use the
terminal escape-character EXEC command.
terminal escape-character ascii-number
Syntax Description
ascii-number
Defaults
Ctrl-^ (Ctrl-Shift-6)
Command Modes
EXEC
Command History
Release
Modification
10.0
Usage Guidelines
See the ASCII Character Set and Hex Values appendix for a list of ASCII characters and their
numerical representation.
This command is useful, for example, if you have the default escape character defined for a different
purpose in your keyboard file. Entering the escape character followed by the X key returns you to EXEC
mode when you are connected to another computer.
Note
Examples
The Break key generally cannot be used as an escape character on the console terminal because the
operating software interprets the Break command on a console line as an instruction to halt the
system.
In the following example the escape character to Ctrl-P (ASCII decimal character 16) for the current
session:
Router# terminal escape-character 16
Related Commands
Command
Description
escape-character
FR-93
terminal exec-character-bits
To locally change the ASCII character set used in EXEC and configuration command characters for the
current session, use the terminal exec-character-bits EXEC command.
terminal exec-character-bits {7 | 8}
Syntax Description
Defaults
7-bit ASCII character set (unless set otherwise in global configuration mode)
Command Modes
EXEC
Command History
Release
Modification
10.0
Usage Guidelines
This EXEC command overrides the default-value exec-character-bits global configuration command.
Configuring the EXEC character width to 8 bits enables you to view special graphical and international
characters in banners, prompts, and so on.
When the user exits the session, the character width is reset to the default value established by the
exec-character-bits global configuration command. However, setting the EXEC character width to
8 bits can also cause failures. For example, if a user on a terminal that is sending parity enters the help
command, an unrecognized command message appears because the system is reading all 8 bits, and
the eighth bit is not needed for the help command.
Examples
The following example temporarily configures the system to use a full 8-bit user interface for system
banners and prompts, allowing the use of additional graphical and international characters:
Router# terminal exec-character-bits 8
Related Commands
Command
Description
exec-character-bits
FR-94
78-11740-02
terminal flowcontrol
To set flow control for the current terminal line for the current session, use the terminal flowcontrol
EXEC command.
terminal flowcontrol {none | software [in | out] | hardware}
Syntax Description
none
software
in | out
(Optional) Specifies the direction of flow control: in causes the router to listen to flow
control from the attached device, and out causes the router to send flow control
information to the attached device. If you do not specify a direction, both directions
are assumed.
hardware
Sets hardware flow control. For information about setting up the EIA/TIA-232 line,
see the manual that was shipped with your product.
Command Modes
EXEC
Command History
Release
Modification
10.0
Usage Guidelines
Flow control enables you to regulate the rate at which data can be transmitted from one point so that it
is equal to the rate at which it can be received at another point. Flow control protects against loss of data
because the terminal is not capable of receiving data at the rate it is being sent. You can set up data flow
control for the current terminal line in one of two ways: software flow control, which you do with control
key sequences, and hardware flow control, which you do at the device level.
For software flow control, the default stop and start characters are Ctrl-S and Ctrl-Q (XOFF and XON).
You can change them with the terminal stop-character and terminal start-character EXEC
commands.
Examples
In the following example incoming software flow control is set for the current session:
Router# terminal flowcontrol software in
Related Commands
Command
Description
flowcontrol
Sets the method of data flow control between the terminal or other serial
device and the router.
FR-95
terminal hold-character
To define the hold character for the current session, use the terminal hold-character EXEC command.
To return the hold character definition to the default, use the terminal no hold-character command.
terminal hold-character ascii-number
terminal no hold-character
Syntax Description
ascii-number
Defaults
The default hold character is defined by the hold-character global configuration command.
Command Modes
EXEC
Command History
Release
Modification
10.0
Usage Guidelines
You can define a local hold character that temporarily suspends the flow of output on the terminal. When
information is scrolling too quickly, you can enter the hold character to pause the screen output, then
enter any other character to resume the flow of output.
You cannot suspend output on the console terminal. To send the hold character to the host, precede it
with the escape character.
Examples
In the following example the hold character for the current (local) session is set to Ctrl-P. The show
terminal output is included to show the verification of the setting (the value for the hold character is
shown in the Special Characters listing).
Router# terminal hold-character 16
"^P" is the local hold character
Router# show terminal
Line 50, Location: "", Type: "VT220"
Length: 24 lines, Width: 80 columns
Baud rate (TX/RX) is 9600/9600
Status: PSI Enabled, Ready, Active, No Exit Banner, Automore On
Capabilities: none
Modem state: Ready
Group codes:
0
Special Chars: Escape Hold Stop Start Disconnect Activation
^^x
^P
none
Timeouts:
Idle EXEC
Idle Session
Modem Answer Session
00:10:00
never
none
Idle Session Disconnect Warning
never
Login-sequence User Response
Dispatch
not set
FR-96
78-11740-02
00:00:30
Autoselect Initial Wait
not set
Modem type is unknown.
Session limit is not set.
Time since activation: 00:04:13
Editing is enabled.
History is enabled, history size is 10.
.
.
.
Related Commands
Command
Description
hold-character
Defines the local hold character used to pause output to the terminal screen.
show terminal
FR-97
terminal keymap-type
To specify the current keyboard type for the current session, use the terminal keymap-type EXEC
command.
terminal keymap-type keymap-name
Syntax Description
keymap-name
Defaults
VT100
Command Modes
EXEC
Command History
Release
Modification
11.2
Usage Guidelines
You must use this command when you are using a keyboard other than the default of VT100.
Examples
The following example specifies a VT220 keyboard as the current keyboard type:
Router# terminal keymap-type vt220
Related Commands
Command
Description
show keymap
FR-98
78-11740-02
terminal length
To set the number of lines on the current terminal screen for the current session, use the terminal length
EXEC command.
terminal length screen-length
Syntax Description
screen-length
Defaults
24 lines
Command Modes
EXEC
Command History
Release
Modification
10.0
Usage Guidelines
Number of lines on the screen. A value of zero disables pausing between screens
of output.
The system uses the length value to determine when to pause during multiple-screen output. A value of
zero prevents the router from pausing between screens of output.
Some types of terminal sessions do not require you to specify the screen length because the screen length
specified can be learned by some remote hosts. For example, the rlogin protocol uses the screen length
to set up terminal parameters on a remote UNIX host.
Examples
In the following example the system is configured to prevent output from pausing if it exceeds the length
of the screen:
Router# terminal length 0
Related Commands
Command
Description
length
FR-99
terminal monitor
To display debug command output and system error messages for the current terminal and session, use
the terminal monitor EXEC command.
terminal monitor
Syntax Description
Defaults
Disabled
Command Modes
EXEC
Command History
Release
Modification
10.0
Usage Guidelines
Remember that all terminal parameter-setting commands are set locally and do not remain in effect after
a session is ended.
Examples
In the following example the system is configured to display debug command output and error messages
during the current terminal session:
Router# terminal monitor
FR-100
78-11740-02
terminal notify
To enable terminal notification about pending output from other Telnet connections for the current
session, use the terminal notify EXEC command. To disable notifications for the current session, use
the no form of this command.
terminal notify
terminal no notify
Syntax Description
Command Modes
EXEC
Command History
Release
Modification
10.0
Usage Guidelines
Enabling notifications may be useful if, for example, you want to know when another connection
receives mail, or when a process has been completed.
This command enables or disables notifications for only the current session. To globally set these
notifications, use the notify line configuration command.
Examples
In the following example notifications will be displayed to inform the user when output is pending on
another connection:
Router# terminal notify
Related Commands
Command
Description
notify
FR-101
terminal padding
To change the character padding on a specific output character for the current session, use the
terminal padding EXEC command.
terminal padding ascii-number count
Syntax Description
ascii-number
count
Number of NULL bytes sent after the specified character, up to 255 padding
characters in length.
Defaults
No padding
Command Modes
EXEC
Command History
Release
Modification
10.0
Usage Guidelines
Character padding adds a number of null bytes to the end of the string and can be used to make a string
an expected length for conformity.
Use this command when the attached device is an old terminal that requires padding after certain
characters (such as ones that scrolled or moved the carriage). See the ASCII Character Set and Hex
Values appendix for a list of ASCII characters.
Examples
The following example pads Ctrl-D (ASCII decimal character 4) with 164 NULL bytes:
Router# terminal padding 4 164
Related Commands
Command
Description
padding
FR-102
78-11740-02
terminal parity
To define the generation of the parity bit for the current terminal line and session, use the
terminal parity EXEC command.
terminal parity {none | even | odd | space | mark}
Syntax Description
none
even
Even parity.
odd
Odd parity.
space
Space parity.
mark
Mark parity.
Defaults
No parity.
Command Modes
EXEC
Command History
Release
Modification
10.0
Usage Guidelines
Communication protocols provided by devices such as terminals and modems will sometimes require a
specific parity bit setting. Refer to the documentation for your device to determine required parity
settings.
Examples
In the following example odd parity checking is enabled for the current session:
Router# terminal parity odd
Related Commands
Command
Description
parity
FR-103
terminal-queue entry-retry-interval
To change the retry interval for a terminal port queue, use the terminal-queue global configuration
command. To restore the default terminal port queue interval, use the no form of this command.
terminal-queue entry-retry-interval interval
no terminal-queue entry-retry-interval
Syntax Description
interval
Defaults
60 seconds
Command Modes
Global configuration
Command History
Release
Modification
11.1
Usage Guidelines
If a remote device (such as a printer) is busy, the connection attempt is placed in a terminal port queue.
If you want to decrease the waiting period between subsequent connection attempts, decrease the default
of 60 to an interval of 10 seconds. Decrease the time between subsequent connection attempts when, for
example, a printer queue stalls for long periods.
Examples
The following example changes the terminal port queue retry interval from the default of 60 seconds to
10 seconds:
Router# terminal-queue entry-retry-interval 10
FR-104
78-11740-02
terminal rxspeed
To set the terminal receive speed (how fast information is sent to the terminal) for the current line and
session, use the terminal rxspeed EXEC command.
terminal rxspeed bps
Syntax Description
bps
Defaults
9600 bps
Command Modes
EXEC
Command History
Release
Modification
10.0
Usage Guidelines
Set the speed to match the baud rate of whatever device you have connected to the port. Some baud rates
available on devices connected to the port might not be supported on the system. The system will indicate
if the speed you select is not supported.
Examples
The following example sets the current auxiliary line receive speed to 115200 bps:
Router# terminal rxspeed 115200
Related Commands
Command
Description
rxspeed
terminal rxspeed
terminal txspeed
terminal speed
Sets the transmit and receive speeds for the current session.
FR-105
terminal special-character-bits
To change the ASCII character widths to accept special characters for the current terminal line and
session, use the terminal special-character-bits EXEC command.
terminal special-character-bits {7 | 8}
Syntax Description
Defaults
Command Modes
EXEC
Command History
Release
Modification
10.0
Usage Guidelines
Configuring the width to 8 bits enables you to use twice as many special characters as with the 7-bit
setting. This selection enables you to add special graphical and international characters in banners,
prompts, and so on.
This command is useful, for example, if you want the router to provide temporary support for
international character sets. It overrides the default-value special-character-bits global configuration
command and is used to compare character sets typed by the user with the special character available
during a data connection, which includes software flow control and escape characters.
When you exit the session, character width is reset to the width established by the default-value
exec-character-bits global configuration command.
Note that setting the EXEC character width to eight bits can cause failures. For example, if a user on a
terminal that is sending parity enters the help command, an unrecognized command message appears
because the Cisco IOS software is reading all eight bits, and the eighth bit is not needed for the help
command.
Examples
The following example temporarily configures a router to use a full 8-bit user interface for system
banners and prompts.
Router# terminal special-character-bits 8
FR-106
78-11740-02
Related Commands
Command
Description
default-value
exec-character-bits
special-character-bits
Configures the number of data bits per character for special characters
such as software flow control characters and escape characters.
FR-107
terminal speed
To set the transmit and receive speeds of the current terminal line for the current session, use the
terminal speed EXEC command.
terminal speed bps
Syntax Description
bps
Defaults
9600 bps
Command Modes
EXEC
Command History
Release
Modification
10.0
Usage Guidelines
Set the speed to match the transmission rate of whatever device you have connected to the port. Some
baud rates available on devices connected to the port might not be supported on the router. The router
indicates whether the speed you selected is not supported.
Examples
The following example restores the transmit and receive speed on the current line to 9600 bps:
Router# terminal speed 9600
Related Commands
Command
Description
speed
FR-108
78-11740-02
terminal start-character
To change the flow control start character for the current session, use the terminal start-character
EXEC command.
terminal start-character ascii-number
Syntax Description
ascii-number
Defaults
Command Modes
EXEC
Command History
Release
Modification
10.0
Usage Guidelines
The flow control start character signals the start of data transmission when software flow control is in
effect.
Examples
The following example changes the start character to Ctrl-O (ASCII decimal character 15):
Router# terminal start-character 15
Related Commands
Command
Description
start-character
FR-109
terminal stopbits
To change the number of stop bits sent per byte by the current terminal line during an active session, use
the terminal stopbits EXEC command.
terminal stopbits {1 | 1.5 | 2}
Syntax Description
1.5
Defaults
2 stop bits
Command Modes
EXEC
Command History
Release
Modification
10.0
Usage Guidelines
Communication protocols provided by devices such as terminals and modems often require a specific
stop-bit setting.
Examples
In the following example the setting for stop bits is changed to one for the current session:
Router# terminal stopbits 1
Related Commands
Command
Description
stopbits
FR-110
78-11740-02
terminal stop-character
To change the flow control stop character for the current session, use the terminal stop-character
EXEC command.
terminal stop-character ascii-number
Syntax Description
ascii-number
Defaults
Command Modes
EXEC
Command History
Release
Modification
10.0
Usage Guidelines
The flow control stop character signals the end of data transmission when software flow control is in
effect.
See the ASCII Character Set and Hex Values appendix for a list of ASCII characters.
Examples
In the following example the stop character is configured as Ctrl-E (ASCII character decimal 5) for the
current session:
Router# terminal stop-character 5
Related Commands
Command
Description
stop-character
FR-111
Syntax Description
Defaults
Disabled
Command Modes
EXEC
Command History
Release
Modification
10.0
Usage Guidelines
Note
The hardware Break signal occurs when a Telnet interrupt-process (ip) command is received on that
connection. The terminal telnet break-on-ip command can be used to control the translation of Telnet
interrupt-process commands into X.25 Break indications.
In this command, the acronym ip indicates interrupt-process, not internet protocol (IP).
This command is also a useful workaround in the following situations:
Several user Telnet programs send an ip command, but cannot send a Telnet Break signal.
Some EIA/TIA-232 hardware devices use a hardware Break signal for various purposes. A hardware
Break signal is generated when a Telnet Break command is received.
You can verify if this command is enabled with the show terminal EXEC command. If enabled the
following line will appear in the output: Capabilities: Send BREAK on IP.
In the following example, a Break signal is generated for the current connection when an
interrupt-process command is issued:
Examples
Related Commands
Command
Description
FR-112
78-11740-02
Syntax Description
Defaults
Disabled
Command Modes
EXEC
Command History
Release
Modification
10.0
Usage Guidelines
You can set the line to allow access server to refuse full-duplex, remote echo connection requests from
the other end. This command suppresses negotiation of the Telnet Remote Echo and Suppress Go Ahead
options.
Examples
In the following example the current session is configured to refuse full-duplex, remote echo requests:
Router# terminal telnet refuse-negotiations
FR-113
Syntax Description
default-speed
Line speed, in bits per second (bps), that the access server will use if the device
on the other end of the connection has not specified a speed.
maximum-speed
Maximum line speed in bits per second (bps), that the device on the other end
of the connection can use.
Defaults
9600 bps (unless otherwise set using the speed, txspeed or rxspeed line configuration commands)
Command Modes
EXEC
Command History
Release
Modification
10.0
Usage Guidelines
Note
Examples
You can match line speeds on remote systems in reverse Telnet, on host machines connected to an access
server to access the network, or on a group of console lines connected to the access server when disparate
line speeds are in use at the local and remote ends of the connections listed above. Line speed negotiation
adheres to the Remote Flow Control option, defined in RFC 1080.
This command applies only to access servers. It is not supported on standalone routers.
The following example enables the access server to negotiate a bit rate on the line using the Telnet
option. If no speed is negotiated, the line will run at 2400 bps. If the remote host requests a speed greater
than 9600 bps, then 9600 bps will be used.
Router# terminal telnet speed 2400 9600
FR-114
78-11740-02
Syntax Description
Defaults
Disabled
Command Modes
EXEC
Command History
Release
Modification
10.0
Usage Guidelines
Note
Examples
You can configure the session to cause a reverse Telnet line to send a Telnet Synchronize signal when it
receives a Telnet Break signal. The TCP Synchronize signal clears the data path, but still interprets
incoming commands.
This command applies only to access servers. It is not supported on standalone routers.
The following example sets an asynchronous line to cause the access server to send a Telnet Synchronize
signal:
Router# terminal telnet sync-on-break
FR-115
Syntax Description
Defaults
CR followed by an LF
Command Modes
EXEC
Command History
Release
Modification
10.0
Usage Guidelines
Note
Examples
The end of each line typed at the terminal is ended with a Return (CR). This command permits
interoperability with different interpretations of end-of-line demarcation in the Telnet protocol
specification.
This command applies only to access servers. It is not supported on stand-alone routers.
In the following example the session is configured to send a CR signal as a CR followed by a NULL:
Router# terminal telnet transparent
FR-116
78-11740-02
terminal terminal-type
To specify the type of terminal connected to the current line for the current session, use the
terminal terminal-type EXEC command.
terminal terminal-type terminal-type
Syntax Description
terminal-type
Defaults
VT100
Command Modes
EXEC
Command History
Release
Modification
10.0
Usage Guidelines
Defines the terminal name and type, and permits terminal negotiation by hosts
that provide that type of service.
Examples
In the following example the terminal type is defined as VT220 for the current session:
Router# terminal terminal-type VT220
Related Commands
Command
Description
terminal keymap-type
terminal-type
FR-117
terminal txspeed
To set the terminal transmit speed (how fast the terminal can send information) for the current line and
session, use the terminal txspeed EXEC command.
terminal txspeed bps
Syntax Description
bps
Defaults
9600 bps
Command Modes
EXEC
Command History
Release
Modification
10.0
Examples
In the following example the line transmit speed is set to 2400 bps for the current session:
Router# terminal txspeed 2400
Related Commands
Command
Description
rxspeed
terminal rxspeed
Sets the terminal receive speed for the current line and session.
terminal terminal-type
Specifies the type of terminal connected to the current line for the current
session.
txspeed
FR-118
78-11740-02
terminal-type
To specify the type of terminal connected to a line, use the terminal-type line configuration command.
To remove any information about the type of terminal and reset the line to the default terminal emulation,
use the no form of this command.
terminal-type {terminal-name | terminal-type}
no terminal-type
Syntax Description
terminal-name
Terminal name.
terminal-type
Terminal type.
Defaults
VT100
Command Modes
Line configuration
Command History
Release
Modification
10.0
Usage Guidelines
This command records the type of terminal connected to the line. The terminal-name argument provides
a record of the terminal type and allows terminal negotiation of display management by hosts that
provide that type of service.
For TN3270 applications, this command must follow the corresponding ttycap entry in the configuration
file.
Examples
FR-119
terminal width
To set the number of character columns on the terminal screen for the current line for a session, use the
terminal width EXEC command.
terminal width characters
Syntax Description
characters
Defaults
80 characters
Command Modes
EXEC
Command History
Release
Modification
10.0
Usage Guidelines
By default, the route provides a screen display width of 80 characters. You can reset this value for the
current session if it does not meet the needs of your terminal.
The rlogin protocol uses the value of the characters argument to set up terminal parameters on a remote
host.
Examples
Related Commands
Command
Description
width
Sets the terminal screen width (the number of character columns displayed
on the attached terminal).
FR-120
78-11740-02
where
To list the open sessions, use the where EXEC command.
where
Syntax Description
Command Modes
EXEC
Command History
Release
Modification
10.0
This command first appeared in a release prior to Cisco IOS Release 10.0.
Usage Guidelines
The where command displays all open sessions associated with the current terminal line.
The break (Ctrl-Shift-6, x), where, and resume commands are available with all supported connection
protocols.
Examples
Address
192.31.7.21
131.108.12.19
Byte
0
0
Idle
0
0
Conn Name
MATHOM
CHAFF
Related Commands
Field
Description
Conn
Host
Address
Byte
Idle
Interval (in minutes) since data was last sent on the line.
Conn Name
Command
Description
show line
Displays information about all lines on the system or the specified line.
show sessions
FR-121
width
To set the terminal screen width, use the width line configuration command. To return to the default
screen width, use the no form of this command.
width characters
no width
Syntax Description
characters
Defaults
80 character columns
Command Modes
Line configuration
Command History
Release
Modification
10.0
Usage Guidelines
By default, the route provides a screen display width of 80 characters. You can reset this value for the
current session if it does not meet the needs of your terminal.
The rlogin protocol uses the value of the characters argument to set up terminal parameters on a remote
host.
Examples
In the following example the location for line 7 is defined as console terminal and the display is set to
132 columns wide:
Router(config)# line 7
Router(config-line)# location console terminal
Router(config-line)# width 132
Related Commands
Command
Description
terminal width
Sets the number of character columns on the terminal screen for the current
session.
FR-122
78-11740-02
FR-123
banner exec
To specify and enable a message to be displayed when an EXEC process is created (an EXEC banner),
use the banner exec global configuration command. To delete the existing EXEC banner, use the no
form of this command.
banner exec d message d
no banner exec
Syntax Description
message
Message text. You can include tokens in the form $(token) in the
message text. Tokens will be replaced with the corresponding
configuration variable. Tokens are described in Table 9.
Defaults
Command Modes
Global configuration
Command History
Release
Modification
10.0
11.3(7.5) AA
12.0(3) T
Usage Guidelines
This command specifies a message to be displayed when an EXEC process is created (a line is activated,
or an incoming connection is made to a vty). Follow this command with one or more blank spaces and
a delimiting character of your choice. Then enter one or more lines of text, terminating the message with
the second occurrence of the delimiting character.
When a user connects to a router, the message-of-the-day (MOTD) banner appears first, followed by the
login banner and prompts. After the user logs in to the router, the EXEC banner or incoming banner will
be displayed, depending on the type of connection. For a reverse Telnet login, the incoming banner will
be displayed. For all other connections, the router will display the EXEC banner.
To disable the EXEC banner on a particular line or lines, use the no exec-banner line configuration
command.
To customize the banner, use tokens in the form $(token) in the message text. Tokens will display current
Cisco IOS configuration variables, such as the routers host name and IP address. The tokens are
described in Table 9.
FR-124
78-11740-02
Table 9
Token
Examples
$(domain)
$(line)
$(line-desc)
The following example sets an EXEC banner that uses tokens. The percent sign (%) is used as a
delimiting character. Notice that the $(token) syntax is replaced by the corresponding configuration
variable.
Router(config)# banner exec %
Enter TEXT message. End with the character '%'.
Session activated on line $(line), $(line-desc). Enter commands at the prompt.
%
Related Commands
Command
Description
banner incoming
banner login
banner motd
banner slip-ppp
exec-banner
FR-125
banner incoming
To define and enable a banner to be displayed when there is an incoming connection to a terminal line
from a host on the network, use the banner incoming global configuration command. To delete the
incoming connection banner, use the no form of this command.
banner incoming d message d
no banner incoming
Syntax Description
message
Message text. You can include tokens in the form $(token) in the
message text. Tokens will be replaced with the corresponding
configuration variable. Tokens are described in Table 10.
Defaults
Command Modes
Global configuration
Command History
Release
Modification
10.0
11.3(7.5) AA
12.0(3) T
Usage Guidelines
Follow the banner incoming command with one or more blank spaces and a delimiting character of your
choice. Then enter one or more lines of text, terminating the message with the second occurrence of the
delimiting character.
An incoming connection is one initiated from the network side of the router. Incoming connections are
also called reverse Telnet sessions. These sessions can display MOTD banners and incoming banners,
but they do not display EXEC banners. Use the no motd-banner line configuration command to disable
the MOTD banner for reverse Telnet sessions on asynchronous lines.
When a user connects to the router, the message-of-the-day (MOTD) banner (if configured) appears first,
before the login prompt. After the user successfully logs in to the router, the EXEC banner or incoming
banner will be displayed, depending on the type of connection. For a reverse Telnet login, the incoming
banner will be displayed. For all other connections, the router will display the EXEC banner.
Incoming banners cannot be suppressed. If you do not want the incoming banner to appear, you must
delete it with the no banner incoming command.
To customize the banner, use tokens in the form $(token) in the message text. Tokens will display current
Cisco IOS configuration variables, such as the routers host name and IP address. The tokens are
described in Table 10.
FR-126
78-11740-02
Table 10
Examples
Token
$(hostname)
$(domain)
$(line)
$(line-desc)
The following example sets an incoming connection banner. The pound sign (#) is used as a delimiting
character.
Router# banner incoming #
This is the Reuses router.
#
The following example sets an incoming connection banner that uses several tokens. The percent sign
(%) is used as a delimiting character.
darkstar(config)# banner incoming %
Enter TEXT message. End with the character '%'.
You have entered $(hostname).$(domain) on line $(line) ($(line-desc)) %
When the incoming connection banner is executed, the user will see the following banner. Notice that
the $(token) syntax is replaced by the corresponding configuration variable.
You have entered darkstar.ourdomain.com on line 5 (Dialin Modem)
Related Commands
Command
Description
banner exec
banner login
banner motd
banner slip-ppp
FR-127
banner login
To define and enable a customized banner to be displayed before the username and password login
prompts, use the banner login global configuration command. To disable the login banner, use no form
of this command.
banner login d message d
no banner login
Syntax Description
message
Message text. You can include tokens in the form $(token) in the
message text. Tokens will be replaced with the corresponding
configuration variable. Tokens are described in Table 11.
Defaults
Command Modes
Global configuration
Command History
Release
Modification
10.0
11.3(7.5) AA
12.0(3) T
Usage Guidelines
Follow the banner login command with one or more blank spaces and a delimiting character of your
choice. Then enter one or more lines of text, terminating the message with the second occurrence of the
delimiting character.
When a user connects to the router, the message-of-the-day (MOTD) banner (if configured) appears first,
followed by the login banner and prompts. After the user successfully logs in to the router, the EXEC
banner or incoming banner will be displayed, depending on the type of connection. For a reverse Telnet
login, the incoming banner will be displayed. For all other connections, the router will display the EXEC
banner.
To customize the banner, use tokens in the form $(token) in the message text. Tokens will display current
Cisco IOS configuration variables, such as the routers host name and IP address. The tokens are
described in Table 11.
Table 11
Token
FR-128
78-11740-02
Table 11
Examples
Token
$(line)
$(line-desc)
The following example sets a login banner. Double quotes (") are used as the delimiting character.
Router# banner login " Access for authorized users only. Please enter your username and
password. "
The following example sets a login banner that uses several tokens. The percent sign (%) is used as the
delimiting character.
darkstar(config)# banner login %
Enter TEXT message. End with the character '%'.
You have entered $(hostname).$(domain) on line $(line) ($(line-desc)) %
When the login banner is executed, the user will see the following banner. Notice that the $(token) syntax
is replaced by the corresponding configuration variable.
You have entered darkstar.ourdomain.com on line 5 (Dialin Modem)
Related Commands
Command
Description
banner exec
banner incoming
banner motd
banner slip-ppp
FR-129
banner motd
To define and enable a message-of-the-day (MOTD) banner, use the banner motd global configuration
command. To delete the MOTD banner, use the no form of this command.
banner motd d message d
no banner motd
Syntax Description
message
Message text. You can include tokens in the form $(token) in the
message text. Tokens will be replaced with the corresponding
configuration variable.
Defaults
Command Modes
Global configuration
Command History
Release
Modification
10.0
11.3(7.5) AA
12.0(3) T
Usage Guidelines
Follow this command with one or more blank spaces and a delimiting character of your choice. Then
enter one or more lines of text, terminating the message with the second occurrence of the delimiting
character.
This MOTD banner is displayed to all terminals connected and is useful for sending messages that affect
all users (such as impending system shutdowns). Use the no exec-banner or no motd-banner command
to disable the MOTD banner on a line. The no exec-banner command also disables the EXEC banner
on the line.
When a user connects to the router, the MOTD banner appears before the login prompt. After the user
logs in to the router, the EXEC banner or incoming banner will be displayed, depending on the type of
connection. For a reverse Telnet login, the incoming banner will be displayed. For all other connections,
the router will display the EXEC banner.
To customize the banner, use tokens in the form $(token) in the message text. Tokens will display current
Cisco IOS configuration variables, such as the routers host name and IP address. The tokens are
described in Table 12.
FR-130
78-11740-02
Table 12
Examples
Token
$(hostname)
$(domain)
$(line)
$(line-desc)
The following example configures an MOTD banner. The pound sign (#) is used as a delimiting
character.
Router# banner motd # Building power will be off from 7:00 AM until 9:00 AM this coming
Tuesday. #
The following example configures an MOTD banner with a token. The percent sign (%) is used as a
delimiting character.
darkstar(config)# banner motd %
Enter TEXT message. End with the character '%'.
Notice: all routers in $(domain) will be upgraded beginning April 20
%
When the MOTD banner is executed, the user will see the following. Notice that the $(token) syntax is
replaced by the corresponding configuration variable.
Notice: all routers in ourdomain.com will be upgraded beginning April 20
Related Commands
Command
Description
banner exec
banner incoming
banner login
banner slip-ppp
exec-banner
motd-banner
FR-131
banner slip-ppp
To customize the banner that is displayed when a SLIP or PPP connection is made, use the banner
slip-ppp global configuration command. To restore the default SLIP or PPP banner, use the no form of
this command.
banner slip-ppp d message d
no banner slip-ppp
Syntax Description
Defaults
message
Message text. You can include tokens in the form $(token) in the
message text. Tokens will be replaced with the corresponding
configuration variable.
The banner message when using the service old-slip-prompt command is:
Entering encapsulation mode.
Your IP address is 10.100.0.0 MTU is 1500 bytes
Command Modes
Global configuration
Command History
Release
Modification
12.0(3)T
Usage Guidelines
Follow this command with one or more blank spaces and a delimiting character of your choice. Then
enter one or more lines of text, terminating the message with the second occurrence of the delimiting
character.
Use this command to define a custom SLIP or PPP connection message. This is useful when legacy client
applications require a specialized connection string. To customize the banner, use tokens in the form
$(token) in the message text. Tokens will display current Cisco IOS configuration variables, such as the
routers host name, IP address, encapsulation type, and MTU size. The banner tokens are described in
Table 13.
FR-132
78-11740-02
Table 13
Examples
Token
$(hostname)
$(domain)
$(peer-ip)
$(gate-ip)
$(encap)
$(encap-alt)
$(mtu)
The following example sets the SLIP/PPP banner using several tokens and the percent sign (%) as the
delimiting character:
Router(config)# banner slip-ppp %
Enter TEXT message. End with the character '%'.
Starting $(encap) connection from $(gate-ip) to $(peer-ip) using a maximum packet size of
$(mtu) bytes... %
The new SLIP/PPP banner will now be displayed when the slip EXEC command is used. Notice that the
$(token) syntax is replaced by the corresponding configuration variable.
Router# slip
Starting SLIP connection from 172.16.69.96 to 192.168.1.200 using a maximum packet size of
1500 bytes...
Related Commands
Command
Description
banner exec
banner incoming
banner motd
slip
ppp
FR-133
clear tcp
To clear a TCP connection, use the clear tcp privileged EXEC command.
clear tcp {line line-number | local hostname port remote hostname port | tcb address}
Syntax Description
line line-number
Host name of the local router and port and host name of the remote
router and port of the TCP connection to clear.
tcb address
Command Modes
Privileged EXEC
Command History
Release
Modification
11.1
Usage Guidelines
The clear tcp command is particularly useful for clearing hung TCP connections.
The clear tcp line line-number command terminates the TCP connection on the specified tty line.
Additionally, all TCP sessions initiated from that tty line are terminated.
The clear tcp local hostname port remote hostname port command terminates the specific TCP
connection identified by the host name and port pair of the local and remote router.
The clear tcp tcb address command terminates the specific TCP connection identified by the TCB
address.
Examples
The following example clears a TCP connection using its tty line number. The show tcp command
displays the line number (tty2) that is used in the clear tcp command.
Router# show tcp
tty2, virtual tty from host router20.cisco.com
Connection state is ESTAB, I/O status: 1, unread input bytes: 0
Local host: 171.69.233.7, Local port: 23
Foreign host: 171.69.61.75, Foreign port: 1058
Enqueued packets for retransmit: 0, input: 0, saved: 0
Event Timers (current time is 0x36144):
Timer
Starts
Wakeups
Retrans
4
0
TimeWait
0
0
AckHold
7
4
SendWnd
0
0
KeepAlive
0
0
GiveUp
0
0
PmtuAger
0
0
Next
0x0
0x0
0x0
0x0
0x0
0x0
0x0
FR-134
78-11740-02
iss: 4151109680
irs: 1249472001
snduna: 4151109752
rcvnxt: 1249472032
sndnxt: 4151109752
rcvwnd:
4258
sndwnd:
delrcvwnd:
24576
30
SRTT: 710 ms, RTTO: 4442 ms, RTV: 1511 ms, KRTT: 0 ms
minRTT: 0 ms, maxRTT: 300 ms, ACK hold: 300 ms
Router# clear tcp line 2
[confirm]
[OK]
The following example clears a TCP connection by specifying its local router host name and port and its
remote router host name and port. The show tcp brief command displays the local (Local Address) and
remote (Foreign Address) host names and ports to use in the clear tcp command.
Router# show tcp brief
TCB
Local Address
Foreign Address
(state)
60A34E9C router1.cisco.com.23
router20.cisco.1055 ESTAB
The following example clears a TCP connection using its TCB address. The show tcp brief command
displays the TCB address to use in the clear tcp command.
Router# show tcp brief
TCB
60B75E48
Local Address
router1.cisco.com.23
Foreign Address
router20.cisco.1054
(state)
ESTAB
Related Commands
Command
Description
show tcp
FR-135
exec
To allow an EXEC process on a line, use the exec line configuration command. To turn off the EXEC
process for the specified line, use the no form of this command.
exec
no exec
Syntax Description
Defaults
Command Modes
Line configuration
Command History
Release
Modification
10.0
Usage Guidelines
When you want to allow an outgoing connection only for a line, use the no exec command. When a user
tries to Telnet to a line with the no exec command configured, the user will get no response when
pressing the Return key at the login screen.
Examples
The following example turns off the EXEC process on line 7. You might want to do this on the auxiliary
port if the attached device (for example, the control port of a rack of modems) sends unsolicited data. If
this happens, an EXEC process starts, which makes the line unavailable.
line 7
no exec
FR-136
78-11740-02
exec-banner
To reenable the display of EXEC and message-of-the-day (MOTD) banners on the specified line or lines,
use the exec-banner line configuration command. To suppress the banners on the specified line or lines,
use the no form of this command.
exec-banner
no exec-banner
Syntax Description
Defaults
Command Modes
Line configuration
Command History
Release
Modification
10.0
Usage Guidelines
This command determines whether the router will display the EXEC banner and the message-of-the-day
(MOTD) banner when an EXEC session is created. These banners are defined with the banner exec and
banner motd global configuration commands. By default, these banner are enabled on all lines. Disable
the EXEC and MOTD banners using the no exec-banner command.
This command has no effect on the incoming banner, which is controlled by the banner incoming
command.
The MOTD banners can also be disabled by the no motd-banner line configuration command, which
disables MOTD banners on a line. If the no exec-banner command is configured on a line, the MOTD
banner will be disabled regardless of whether the motd-banner command is enabled or disabled.
Table 14 summarizes the effects of the exec-banner command and the motd-banner command.
Table 14
exec-banner (default)
no exec-banner
MOTD banner
None
motd-banner (default)
EXEC banner
no motd-banner
EXEC banner
None
For reverse Telnet connections, the EXEC banner is never displayed. Instead, the incoming banner is
displayed. The MOTD banner is displayed by default, but it is disabled if either the no exec-banner
command or no motd-banner command is configured. Table 15 summarizes the effects of the
exec-banner command and the motd-banner command for reverse Telnet connections.
FR-137
Table 15
Examples
exec-banner (default)
no exec-banner
MOTD banner
Incoming banner
motd-banner (default)
Incoming banner
no motd-banner
Incoming banner
Incoming banner
The following example suppresses the EXEC and MOTD banners on virtual terminal lines 0 to 4:
line vty 0 4
no exec-banner
Related Commands
Command
Description
banner exec
banner incoming
banner motd
motd-banner
FR-138
78-11740-02
exec-timeout
To set the interval that the EXEC command interpreter waits until user input is detected, use the
exec-timeout line configuration command. To remove the timeout definition, use the no form of this
command.
exec-timeout minutes [seconds]
no exec-timeout
Syntax Description
minutes
seconds
Defaults
10 minutes
Command Modes
Line configuration
Command History
Release
Modification
10.0
Usage Guidelines
If no input is detected during the interval, the EXEC facility resumes the current connection. If no
connections exist, the EXEC facility returns the terminal to the idle state and disconnects the incoming
session.
To specify no timeout, enter the exec-timeout 0 0 command.
Examples
FR-139
lock
To configure a temporary password on a line, use the lock EXEC command.
lock
Syntax Description
Defaults
Not locked
Command Modes
EXEC
Command History
Release
Modification
10.0
This command was introduced in a release prior to Cisco IOS Release 10.0.
Usage Guidelines
You can prevent access to your session while keeping your connection open by setting up a temporary
password. To lock access to the terminal, perform the following steps:
Step 1
Enter the lock command. The system prompts you for a password.
Step 2
Enter a password, which can be any arbitrary string. The system will prompt you to confirm the
password. The screen then clears and displays the message Locked.
Step 3
The Cisco IOS software honors session timeouts on a locked lines. You must clear the line to remove
this feature. The system administrator must set the line up to allow use of the temporary locking feature
by using the lockable line configuration command.
Examples
The following example shows configuring the router as lockable, saving the configuration, and then
locking the current session for the user:
Router(config-line)# lockable
Router(config-line)# ^Z
Router# copy system:running-config nvram:startup-config
Building configuration...
OK
Router# lock
Password: <password>
Again: <password>
Locked
Password: <password>
Router#
FR-140
78-11740-02
Related Commands
Command
Description
lockable
login (EXEC)
FR-141
menu clear-screen
To clear the terminal screen before displaying a menu, use the menu clear-screen global configuration
command.
menu menu-name clear-screen
Syntax Description
menu-name
Defaults
Disabled
Command Modes
Global configuration
Command History
Release
Modification
10.0
Usage Guidelines
This command uses a terminal-independent mechanism based on termcap entries defined in the router
and the configured terminal type for the user. This command allows the same menu to be used on
multiple types of terminals instead of having terminal-specific strings embedded within menu titles. If
the termcap entry does not contain a clear string, the menu system enters 24 new lines, causing all
existing text to scroll off the top of the terminal screen.
Examples
In the following example, the terminal screen is cleared before displaying the menu named Access1:
menu Access1 clear-screen
Related Commands
Command
Description
menu (EXEC)
menu command
menu default
menu line-mode
menu options
menu prompt
menu single-space
menu status-line
Displays a line of status information about the current user at the top of a
menu
menu text
menu title
no menu
FR-142
78-11740-02
menu command
To specify underlying commands for user menus, use the menu command global configuration
command.
menu menu-name command menu-item {command | menu-exit}
Syntax Description
menu-name
menu-item
Number, character, or string used as the key for the item. The key is displayed
to the left of the menu item text. You can specify a maximum of 18 menu
entries. When the tenth item is added to the menu, the line-mode and
single-space options are activated automatically.
command
menu-exit
Provides a way for menu users to return to a higher-level menu or exit the
menu system.
Defaults
Disabled
Command Modes
Global configuration
Command History
Release
Modification
10.0
Usage Guidelines
Use this command to assign actions to items in a menu. Use the menu text global configuration
command to assign text to items. These commands must use the same menu name and menu selection
key.
The menu command command has a special keyword for the command argument, menu-exit, that is
available only within menus. It is used to exit a submenu and return to the previous menu level, or to exit
the menu altogether and return to the EXEC command prompt.
You can create submenus that are opened by selecting entries in another menu. Use the menu EXEC
command as the command for the submenu item.
Note
If you nest too many levels of menus, the system prints an error message on the terminal and returns to
the previous menu level.
When a menu allows connections (their normal use), the command for an entry activating the connection
should contain a resume command, or the line should be configured to prevent users from escaping their
sessions with the escape-char none command. Otherwise, when they escape from a connection and
return to the menu, there will be no way to resume the session and it will sit idle until the user logs out.
FR-143
Specifying the resume command as the action that is performed for a selected menu entry permits a user
to resume a named connection or connect using the specified name, if there is no active connection by
that name. As an option, you can also supply the connect string needed to connect initially. When you
do not supply this connect string, the command uses the specified connection name.
You can also use the resume/next command, which resumes the next connection in the users list of
connections. This function allows you to create a single menu entry that steps through all of the users
connections.
Note
A menu should not contain any exit paths that leave users in an unfamiliar interface environment.
When a particular line should always display a menu, that line can be configured with an autocommand
line configuration command. Menus can be run on a per-user basis by defining a similar autocommand
command for that local username. For more information about the autocommand command, refer to the
Cisco IOS Dial Technologies Configuration Guide.
Examples
In the following example, the commands to be issued when the menu user selects option 1, 2, or 3 are
specified for the menu named Access1:
menu Access1 command 1 tn3270 vms.cisco.com
menu Access1 command 2 rlogin unix.cisco.com
menu Access1 command 3 menu-exit
The following example allows a menu user to exit a menu by entering Exit at the menu prompt:
menu Access1 text Exit Exit
menu Access1 command Exit menu-exit
Related Commands
Command
Description
autocommand
menu (EXEC)
menu clear-screen
menu default
menu line-mode
menu options
menu prompt
menu single-space
menu status-line
Displays a line of status information about the current user at the top of a
menu
menu text
menu title
FR-144
78-11740-02
menu default
To specify the menu item to use as the default, use the menu default global configuration command.
menu menu-name default menu-item
Syntax Description
menu-name
menu-item
Defaults
Disabled
Command Modes
Global configuration
Command History
Release
Modification
10.0
Usage Guidelines
Use this command to specify which menu entry is used when the user presses Enter without specifying
an item. The menu entries are defined by the menu command and menu text global configuration
commands.
Examples
In the following example, the menu user exits the menu when pressing Enter without selecting an item:
menu Access1 9 text Exit the menu
menu Access1 9 command menu-exit
menu Access1 default 9
Related Commands
Command
Description
menu (EXEC)
menu command
menu prompt
menu text
menu title
FR-145
menu line-mode
To require the user to press Enter after specifying an item, use the menu line-mode global configuration
command.
menu menu-name line-mode
Syntax Description
menu-name
Defaults
Enabled for menus with more than nine items. Disabled for menus with nine or fewer items.
Command Modes
Global configuration
Command History
Release
Modification
10.0
Usage Guidelines
In a menu of nine or fewer items, you ordinarily select a menu item by entering the item number. In line
mode, you select a menu entry by entering the item number and pressing Enter. Line mode allows you
to backspace over the selected number and enter another number before pressing Enter to issue the
command.
This option is activated automatically when more than nine menu items are defined but also can be
configured explicitly for menus of nine or fewer items.
In order to use strings as keys for items, the menu line-mode command must be configured.
Examples
In the following example, the line-mode option is enabled for the menu named Access1:
menu Access1 line-mode
Related Commands
Command
Description
menu (EXEC)
menu clear-screen
menu command
menu default
menu options
menu prompt
menu single-space
menu status-line
Displays a line of status information about the current user at the top of a
menu
menu text
FR-146
78-11740-02
menu options
To set options for items in user menus, use the menu options global configuration command.
menu menu-name options menu-item {login | pause}
Syntax Description
menu-name
menu-item
login
pause
Defaults
Disabled
Command Modes
Global configuration
Command History
Release
Modification
10.0
Usage Guidelines
Use the menu command and menu text global configuration commands to define a menu entry.
Examples
In the following example, a login is required before issuing the command specified by menu entry 3 of
the menu named Access1:
menu Access1 options 3 login
Related Commands
Command
Description
menu (EXEC)
menu clear-screen
menu command
menu default
menu line-mode
menu prompt
menu single-space
menu status-line
Displays a line of status information about the current user at the top of a
menu.
menu text
menu title
FR-147
menu prompt
To specify the prompt for a user menu, use the menu prompt global configuration command.
menu menu-name prompt d prompt d
Syntax Description
menu-name
A delimiting character that marks the beginning and end of a title. Text
delimiters are characters that do not ordinarily appear within the text of a title,
such as slash ( / ), double quote ("), and tilde (~). ^C is reserved for special
use and should not be used in the text of the title.
prompt
Defaults
Disabled
Command Modes
Global configuration
Command History
Release
Modification
10.0
Usage Guidelines
Press Enter after entering the first delimiter. The router will prompt you for the text of the prompt. Enter
the text followed by the delimiter, and press Enter.
Use the menu command and menu text commands to define the menu selections.
Examples
In the following example, the prompt for the menu named Access1 is configured as Select an item.:
Router(config)# menu Access1 prompt /
Enter TEXT message. End with the character '/'.
Select an item. /
Router(config)#
Related Commands
Command
Description
menu (EXEC)
menu command
menu default
menu text
menu title
FR-148
78-11740-02
menu single-space
To display menu items single-spaced rather than double-spaced, use the menu single-space global
configuration command.
menu menu-name single-space
Syntax Description
menu-name
Defaults
Enabled for menus with more than nine items; disabled for menus with nine or fewer items.
Command Modes
Global configuration
Command History
Release
Modification
10.0
Usage Guidelines
When more than nine menu items are defined, the menu is displayed single-spaced. To configure the
menus with nine or fewer items to display single-spaced, use this command.
Examples
In the following example, single-spaced menu items are displayed for the menu named Access1:
menu Access1 single-space
Related Commands
Command
Description
menu (EXEC)
menu clear-screen
menu command
menu default
menu line-mode
menu options
menu prompt
menu status-line
Displays a line of status information about the current user at the top of a
menu.
menu text
menu title
FR-149
menu status-line
To display a line of status information about the current user at the top of a menu, use the menu
status-line global configuration command.
menu menu-name status-line
Syntax Description
menu-name
Defaults
Disabled
Command Modes
Global configuration
Command History
Release
Modification
10.0
Usage Guidelines
This command displays the status information at the top of the screen before the menu title is displayed.
This status line includes the routers host name, the users line number, and the current terminal type and
keymap type (if any).
Examples
In the following example, status information is enabled for the menu named Access1:
menu Access1 status-line
Related Commands
Command
Description
menu (EXEC)
menu clear-screen
menu command
menu default
menu line-mode
menu options
menu prompt
menu single-space
menu text
menu title
FR-150
78-11740-02
menu text
To specify the text of a menu item in a user menu, use the menu text global configuration command.
menu menu-name text menu-item menu-text
Syntax Description
menu-name
menu-item
Number, character, or string used as the key for the item. The key is displayed
to the left of the menu item text. You can specify a maximum of 18 menu
items. When the tenth item is added to the menu, the menu line-mode and
menu single-space commands are activated automatically.
menu-text
Defaults
Command Modes
Global configuration
Command History
Release
Modification
10.0
Usage Guidelines
Use this command to assign text to items in a menu. Use the menu command command to assign actions
to items. These commands must use the same menu name and menu selection key.
You can specify a maximum of 18 items in a menu.
Examples
In the following example, the descriptive text for the three entries is specified for options 1, 2, and 3 in
the menu named Access1:
menu Access1 text 1 IBM Information Systems
menu Access1 text 2 UNIX Internet Access
menu Access1 text 3 Exit menu system
Related Commands
Command
Description
menu (EXEC)
menu clear-screen
menu command
menu default
menu line-mode
menu options
menu prompt
FR-151
Command
Description
menu single-space
menu status-line
Displays a line of status information about the current user at the top of a
menu
menu title
FR-152
78-11740-02
menu title
To create a title (banner) for a user menu, use the menu title global configuration command.
menu menu-name title d menu-title d
Syntax Description
menu-name
A delimiting character that marks the beginning and end of a title. Text
delimiters are characters that do not ordinarily appear within the text of a title,
such as slash ( / ), double quote ("), and tilde (~). ^C is reserved for special
use and should not be used in the text of the title.
menu-title
Defaults
Command Modes
Global configuration
Command History
Release
Modification
10.0
Usage Guidelines
The menu title command must use the same menu name used with the menu text and menu command
commands used to create a menu.
You can position the title of the menu horizontally by preceding the title text with blank characters. You
can also add lines of space above and below the title by pressing Enter.
Follow the title keyword with one or more blank characters and a delimiting character of your choice.
Then enter one or more lines of text, ending the title with the same delimiting character. You cannot use
the delimiting character within the text of the message.
When you are configuring from a terminal and are attempting to include special control characters, such
as a screen-clearing string, you must use Ctrl-V before the special control characters so that they are
accepted as part of the title string. The string ^[[H^[[J is an escape string used by many
VT100-compatible terminals to clear the screen. To use a special string, you must enter Ctrl-V before
each escape character.
You also can use the menu clear-screen global configuration command to clear the screen before
displaying menus and submenus, instead of embedding a terminal-specific string in the menu title. The
menu clear-screen command allows the same menu to be used on different types of terminals.
Examples
In the following example, the title that will be displayed is specified when the menu named Access1 is
invoked. Press Enter after the second slash (/) to display the prompt.
Router(config)# menu Access1 title /^[[H^[[J
Enter TEXT message. End with the character '/'.
Welcome to Access1 Internet Services
FR-153
Related Commands
Command
Description
menu (EXEC)
menu clear-screen
menu command
menu default
menu line-mode
menu options
menu prompt
menu single-space
menu status-line
Displays a line of status information about the current user at the top of a
menu
menu text
FR-154
78-11740-02
no menu
To delete a user menu from the configuration file, use the no menu global configuration command.
no menu menu-name
Syntax Description
menu-name
Defaults
None
Command Modes
Global configuration
Command History
Release
Modification
10.0
Usage Guidelines
Use this command to remove any menu commands for a particular menu from the configuration file.
As with all global configuration commands, this command will only effect the startup configuration file
when you save the running configuration using the copy running-config startup-config EXEC
command.
Examples
Related Commands
Command
Description
menu (EXEC)
menu command
menu prompt
menu text
menu title
FR-155
motd-banner
To enable the display of message-of-the-day (MOTD) banners on the specified line or lines, use the
motd-banner line configuration command. To suppress the MOTD banners on the specified line or lines,
use the no form of this command.
motd-banner
no motd-banner
Syntax Description
Defaults
Command Modes
Line configuration
Command History
Release
Modification
11.1
Usage Guidelines
This command determines whether the router will display the MOTD banner when an EXEC session is
created on the specified line or lines. The MOTD banner is defined with the banner motd global
configuration command. By default, the MOTD banner is enabled on all lines. Disable the MOTD banner
on specific lines using the no motd-banner line configuration command.
The MOTD banners can also be disabled by the no exec-banner line configuration command, which
disables both MOTD banners and EXEC banners on a line. If the no exec-banner command is
configured on a line, the MOTD banner will be disabled regardless of whether the motd-banner
command is enabled or disabled. Table 16 summarizes the effects of the exec-banner command and the
motd-banner command.
Table 16
exec-banner (default)
no exec-banner
MOTD banner
None
motd-banner (default)
EXEC banner
no motd-banner
EXEC banner
None
For reverse Telnet connections, the EXEC banner is never displayed. Instead, the incoming banner is
displayed. The MOTD banner is displayed by default, but it is disabled if either the no exec-banner
command or no motd-banner command is configured. Table 17 summarizes the effects of the
exec-banner command and the motd-banner command for reverse Telnet connections.
FR-156
78-11740-02
Table 17
Examples
exec-banner (default)
no exec-banner
MOTD banner
Incoming banner
motd-banner (default)
Incoming banner
no motd-banner
Incoming banner
Incoming banner
The following example suppresses the MOTD banner on vty lines 0 through 4:
line vty 0 4
no motd-banner
Related Commands
Command
Description
banner exec
banner incoming
banner motd
motd-banner
FR-157
name-connection
To assign a logical name to a connection, use the name-connection user EXEC command.
name-connection
Syntax Description
Defaults
Command Modes
User EXEC
Command History
Release
Modification
10.0
Usage Guidelines
Examples
The following example assigns the logical name blue to the connection:
Router> where
Conn Host
* 1 doc-2509
Address
172.30.162.131
Byte
0
Router> name-connection
Connection number: 1
Enter logical name: blue
Connection 1 to doc-2509 will be named "BLUE" [confirm]
Related Commands
Command
Description
where
FR-158
78-11740-02
refuse-message
To define and enable a line-in-use message, use the refuse-message line configuration command. To
disable the message, use the no form of this command.
refuse-message d message d
no refuse-message
Syntax Description
message
Message text.
Defaults
Command Modes
Line configuration
Command History
Release
Modification
10.0
Usage Guidelines
Follow this command with one or more blank spaces and a delimiting character of your choice. Then
enter one or more lines of text, terminating the message with the second occurrence of the delimiting
character. You cannot use the delimiting character within the text of the message.
When you define a message using this command, the Cisco IOS software performs the following steps:
Examples
1.
2.
3.
In the following example, line 5 is configured with a line-in-use message, and the user is instructed to
try again later:
line 5
refuse-message
FR-159
send
To send messages to one or all terminal lines, use the send EXEC command.
send {line-number | * | aux number | console number | tty number | vty number}
Syntax Description
line-number
aux number
console number
tty number
vty number
Defaults
Command Modes
EXEC
Command History
Release
Modification
11.2
Usage Guidelines
Caution
Examples
After entering this command, the system prompts for the message to be sent, which can be up to 500
characters long. Enter Ctrl-Z to end the message. Enter Ctrl-C to abort this command.
Be aware that in some circumstances text sent using the send command may be interpreted as an
executable command by the receiving device. For example, if the receiving device is Unix workstation,
and the receiving device is in a state (shell) where commands can be executed, the incoming text (if a
valid Unix command) will be interpreted as a command. For this reason you should limit your use of any
unmonitored connection to a router that uses an interactive shell.
***
***
*** Message from tty0 to all terminals:
***
The system 2509 will be shut down in 10 minutes for repairs.
FR-160
78-11740-02
2509#
FR-161
service linenumber
To configure the Cisco IOS software to display line number information after the EXEC or incoming
banner, use the service linenumber global configuration command. To disable this function, use the no
form of this command.
service linenumber
no service linenumber
Syntax Description
Defaults
Disabled
Command Modes
Global configuration
Command History
Release
Modification
10.0
Usage Guidelines
With the service linenumber command, you can have the Cisco IOS software display the host name,
line number, and location each time an EXEC process is started, or an incoming connection is made. The
line number banner appears immediately after the EXEC banner or incoming banner. This feature is
useful for tracking problems with modems, because the host and line for the modem connection are
listed. Modem type information can also be included.
Examples
In the following example, a user Telnets to Router2 before and after the service linenumber command
is enabled. The second time, information about the line is displayed after the banner.
Router1> telnet Router2
Trying Router2 (172.30.162.131)... Open
Welcome to Router2.
User Access Verification
Password:
Router2> enable
Password:
Router2# configure terminal
Enter configuration commands, one per line.
Router2(config)# service linenumber
Router2(config)# end
Router2# logout
FR-162
78-11740-02
Related Commands
Command
Description
show users
FR-163
vacant-message
To display an idle terminal message, use the vacant-message line configuration command. To remove
the default vacant message or any other vacant message that may have been set, use the no form of this
command.
vacant-message [d message d]
no vacant-message
Syntax Description
Defaults
message
Command Modes
Line configuration
Command History
Release
Modification
10.0
Usage Guidelines
This command enables the banner to be displayed on the screen of an idle terminal. The vacant-message
command without any arguments restores the default message.
Follow this command with one or more blank spaces and a delimiting character of your choice. Then
enter one or more lines of text, terminating the message with the second occurrence of the delimiting
character.
Note
Examples
For a rotary group, you need to define only the message for the first line in the group.
The following example turns on the system banner and displays this message:
line 0
vacant-message #
Welcome to Cisco Systems, Inc.
FR-164
78-11740-02
FR-165
FR-166
78-11740-02
FR-167
international
If you are using Telnet to access a Cisco IOS platform and you want to display 8-bit and multibyte
international characters (for example, Kanji) and print the Escape character as a single character instead
of as the caret and bracket symbols (^[), use the international line configuration command. To display
characters in 7-bit format, use the no form of this command.
international
no international
Syntax Description
Defaults
Disabled
Command Modes
Line configuration
Command History
Release
Modification
11.3
Usage Guidelines
If you are configuring a Cisco IOS platform using the Cisco Web browser UI, this feature is enabled
automatically when you enable the Cisco Web browser UI using the ip http server global configuration
command.
Examples
The following example enables a Cisco IOS platform to display 8-bit and multibyte characters and print
the Escape character as a single character instead of as the caret and bracket symbols (^[) when you are
using Telnet to access the platform:
line vty 4
international
Related Commands
Command
Description
terminal international
Prints the Escape character as a single character instead of as the caret and
bracket symbols (^[) for a current Telnet session in instances when you
are using Telnet to access a Cisco IOS platform and you want to display
8-bit and multibyte international characters (for example, Kanji).
FR-168
78-11740-02
ip http access-class
To assign an access list to the HTTP server used by the Cisco IOS ClickStart software or the Cisco Web
browser UI, use the ip http access-class global configuration command. To remove the assigned access
list, use the no form of this command.
ip http access-class {access-list-number | access-list-name}
no ip http access-class {access-list-number | access-list-name}
Syntax Description
access-list-number
access-list-name
Defaults
Command Modes
Global configuration
Command History
Release
Modification
11.2
Usage Guidelines
If this command is configured, the specified access list is assigned to the HTTP server. Before the HTTP
server accepts a connection, it checks the access list. If the check fails, the HTTP server does not accept
the request for a connection.
Examples
The following example assigns the access list named marketing to the HTTP server:
ip http access-class marketing
ip access-list standard marketing
permit 192.168.34.0 0.0.0.255
permit 172.16.0.0 0.0.255.255
permit 10.0.0.0 0.255.255.255
! (Note: all other access implicitly denied)
Related Commands
Command
Description
ip access-list
ip http server
FR-169
ip http authentication
To specify a particular authentication method for HTTP server users, use the ip http authentication
global configuration command. To disable a configured authentication method, use the no form of this
command.
ip http authentication {aaa | enable | local | tacacs}
no ip http authentication {aaa | enable | local | tacacs}
Syntax Description
aaa
enable
Indicates that the enable password method, which is the default method of HTTP
server user authentication, is used for authentication.
local
Indicates that the local user database as defined on the Cisco router or access
server is used for authentication.
tacacs
Defaults
The default method of authentication for the HTTP server interface is the enable password method.
Command Modes
Global configuration
Command History
Release
Modification
11.2 F
Usage Guidelines
The ip http authentication command specifies the authentication method to be used for login when a
client connects to the HTTP server. Use of the ip http authentication aaa command option is
recommended. The enable, local, and tacacs methods should be specified using the aaa authentication
login command.
The enable password method is the default HTTP server authentication method. If the enable password
is used as the HTTP server login authentication method, the client connects to the HTTP server with a
default privilege level of 15.
Note
When the enable password is used as the HTTP server login authentication method, any username
entered will be ignored; the server will only verify the enable password. This may make it easier for
an attacker to access the router. Because a username and password pair is more secure than using only a
password for authentication, using only enable password for authentication is strongly discouraged.
Instead, use of the local or tacacs authentication options, configured as part of a global Authentication,
Authorization, and Accounting (AAA) framework, is recommended.
To configure HTTP access as part of a AAA policy, use the ip http authentication aaa command option.
The local, tacacs, or enable authentication methods should then be configured using the aaa
authentication login command.
FR-170
78-11740-02
For information about adding users into the local username database, refer to the Cisco IOS Security
Configuration Guide.
Examples
The following example specifies that the method configured for AAA should be used for authentication
for HTTP server users. The AAA login method is configured as the local username/password
authentication method.
Router(config)# ip http authentication aaa
Router(config)# aaa authentication login default local
Related Commands
Command
Description
ip http server
FR-171
ip http port
To specify the port to be used by the Cisco IOS ClickStart software or the Cisco Web browser UI, use
the ip http port global configuration command. To use the default port, use the no form of this
command.
ip http port port-number
no ip http port
Syntax Description
port-number
Defaults
Command Modes
Global configuration
Command History
Release
Modification
11.2
Usage Guidelines
Use this command if ClickStart or the Cisco Web browser UI cannot use port 80.
Examples
The following example configures the router so that you can use ClickStart or the Cisco Web browser
UI through port 60:
ip http server
ip http port 60
Related Commands
Command
Description
ip http server
FR-172
78-11740-02
ip http server
To enable the Cisco Web browser UI on a router or access server, use the ip http server global
configuration command. To disable this feature, use the no form of this command.
ip http server
no ip http server
Syntax Description
Defaults
This feature is automatically enabled on Cisco 1003, Cisco 1004, and Cisco 1005 routers that have not
yet been configured. For Cisco 1003, Cisco 1004, and Cisco 1005 routers that have already been
configured, and for all other routers, this feature is disabled.
The HTTP server is disabled on the Cisco Catalyst 4000 series switch. The HTTP server is enabled for
clustering and on the following Cisco switches: Catalyst 3700 series, Catalyst 3750 series, Catalyst 3550
series, Catalyst 3560 series, and Catalyst 2950 series.
Command History
Release
Modification
11.2
Command Modes
Global configuration
Usage Guidelines
This command enables a simple HTTP server on your system. The HTTP server in Cisco IOS software
is used primarily for the Cisco Web browser user interface (UI) and ClickStart.
The Cisco Web browser UI allows configuration and monitoring of a router or access server using any
web browser. Enabling the Cisco Web browser UI also allows Cisco 1003, Cisco 1004, and Cisco 1005
routers to be configured from a browser using ClickStart.
To view the home page of the router, use a Web browser pointed to http://x.y.z.t, where x.y.z.t is the IP
address of your router or access server, or, if a name has been set, use http://router-name. Varying forms
of authentication for login can be set using the ip http authentication command, but the default login
method is entering the enable password when prompted.
For information on accessing a router Web page at a privilege level other the default of 15 (privileged
EXEC mode), see the Using the Cisco Web Browser to Issue Commands section of the Cisco IOS
Configuration Fundamentals Configuration Guide.
Examples
The following example enables the HTTP server on the router, allowing use of the Cisco Web browser
UI to monitor the router and issue commands to it:
ip http server
FR-173
Related Commands
Command
Description
ip http access-class
Assigns an access list to the HTTP server used by the Cisco IOS ClickStart
software or the Cisco Web browser UI.
Specifies the port to be used by the Cisco IOS ClickStart software or the
Cisco Web browser UI.
FR-174
78-11740-02
terminal international
If you are using Telnet to access a Cisco IOS platform and you want to display 8-bit and multibyte
international characters (for example, Kanji) and print the Escape character as a single character instead
of as the caret and bracket symbols (^[) for a current Telnet session, use the terminal international
EXEC command. To display characters in 7-bit format for a current Telnet session, use the no form of
this command.
terminal international
no terminal international
Syntax Description
Defaults
Disabled
Command Modes
EXEC
Command History
Release
Modification
11.3
Usage Guidelines
If you are configuring a Cisco IOS platform using the Cisco Web browser UI, this feature is enabled
automatically when you enable the Cisco Web browser UI using the ip http server global configuration
command.
Examples
The following example enables a Cisco IOS platform to display 8-bit and multibyte characters and print
the Escape character as a single character instead of as the caret and bracket symbols (^[) when you are
using Telnet to access the platform for the current Telnet session:
Router# terminal international
Related Commands
Command
Description
international
Prints the Escape character as a single character instead of as the caret and
bracket symbols (^[) in instances when you are using Telnet to access a
Cisco IOS platform and you want to display 8-bit and multibyte international
characters (for example, Kanji).
FR-175
FR-176
78-11740-02
Prefix
Description
ftp:
rcp:
tftp:
Table 19 lists the available suffix options (file indentification suffixes) for the URL prefixes used in
Table 18.
Table 19
Prefix
Suffix Options
ftp:
[[//[username[:password]@]location]/directory]/filename
For example:
ftp://network-config (prefix://filename)
ftp://jeanluc:[email protected]/ship-config
rcp:
rcp:[[//[username@]location]/directory]/filename
tftp:
tftp:[[//location]/directory]/filename
Table 20 lists common URL prefixes used to indicate memory locations on the system.
FR-179
Table 20
Prefix
Description
bootflash:
Bootflash memory.
disk0:
flash:
Flash memory. This prefix is available on most platforms. For platforms that do
[partition-number] not have a device named flash:, the prefix flash: is aliased to slot0:.
Therefore, you can use the prefix flash: to refer to the main Flash memory
storage area on all platforms
flh:
null:
Null destination for copies. You can copy a remote file to null to determine its
size.
nvram:
slavebootflash:
slavenvram:
slaveslot0:
slaveslot1:
slot0:
slot1:
xmodem:
Obtain the file from a network machine using the Xmodem protocol.
ymodem:
Obtain the file from a network machine using the Ymodem protocol.
For details about the Cisco IFS, and for IFS configuration tasks, refer to the Configuring the Cisco IOS
File System chapter in the Release 12.2 Cisco IOS Configuration Fundamentals Configuration Guide.
For details about Flash File System types (Class A, B, and C), refer to PCMCIA Filesystem
Compatibility Matrix and Filesystem Information Tech Note on Cisco.com
FR-180
78-11740-02
cd
To change the default directory or file system, use the cd EXEC command.
cd [filesystem:]
Syntax Description
filesystem:
Defaults
The initial default file system is flash:. For platforms that do not have a physical device named flash:,
the keyword flash: is aliased to the default Flash device.
If you do not specify a directory on a file system, the default is the root directory on that file system.
Command Modes
EXEC
Command History
Release
Modification
11.0
Usage Guidelines
For all EXEC commands that have an optional filesystem argument, the system uses the file system
specified by the cd command when you omit the optional filesystem argument. For example, the dir
EXEC command, which displays a list of files on a file system, contain an optional filesystem argument.
When you omit this argument, the system lists the files on the file system specified by the cd command.
Examples
In the following example, the cd command is used to set the default file system to the Flash memory card
inserted in slot 0:
Router# pwd
bootflash:/
Router# cd slot0:
Router# pwd
slot0:/
Related Commands
Command
Description
copy
delete
dir
pwd
undelete
FR-181
configure network
The configure network command was replaced by the copy {rcp | tftp} running-config command in
Cisco IOS Release 11.0. To maintain backward compatibility, the configure network command
continues to function in Cisco IOS Release 12.2 for most systems, but support for this command may be
removed in a future release.
The copy {rcp | tftp} running-config command was replaced by the
copy {ftp: | rcp: | tftp:}[filename] system:running-config command in Cisco IOS Release 12.1.
The copy {ftp: | rcp: | tftp:}[filename] system:running-config command specifies that a configuration
file should be copied from a FTP, rcp, or TFTP source to the running configuration. See the description
of the copy in this chapter command for more information.
FR-182
78-11740-02
copy
To copy any file from a source to a destination, use the copy EXEC command.
copy [/erase] source-url destination-url
Syntax Description
/erase
source-url
destination-url
The exact format of the source and destination URLs varies according to the file or directory location.
You may enter either an alias keyword for a particular file or an alias keyword for a file system type (not
a file within a type).
Timesaver
Aliases are used to cut down on the amount of typing you need to perform. For example, it is easier
to type copy run start (the abbreviated form of the copy running-config startup-config command)
than it is to type copy system:r nvram:s (the abbreviated form of the copy system:running-config
nvram:startup-config command). These aliases also allow you to continue using some of the
common commands used in previous versions of Cisco IOS software.
Table 21 shows two keyword shortcuts to URLs.
Table 21
Keyword
Source or Destination
running-config
startup-config
The following tables list aliases by file system type. If you do not specify an alias, the router looks for
a file in the current directory.
Table 22 lists URL aliases for Special (opaque) file systems. Table 23 lists them for network file systems,
and Table 24 lists them for local writable storage.
FR-183
Table 22
Alias
Source or Destination
flh:
modem:
nvram:
null:
Null destination for copies or files. You can copy a remote file to
null to determine its size.
system:
xmodem:
Source destination for the file from a network machine that uses the
Xmodem protocol.
ymodem:
Source destination for the file from a network machine that uses the
Xmodem protocol.
Table 23
Alias
Source or Destination
ftp:
rcp:
tftp:
Table 24
Alias
Source or Destination
bootflash:
flash:
slavebootflash:
slaveram:
slaveslot0:
FR-184
78-11740-02
Table 24
URL Prefix Aliases for Local Writable Storage File Systems (continued)
Alias
Source or Destination
slaveslot1:
slot0:
slot1:
Command Modes
EXEC
Command History
Release
Modification
11.3 T
Usage Guidelines
You can enter on the command line all necessary source- and destination-URL information and the
username and password to use, or you can enter the copy command and have the router prompt you for
any missing information.
If you enter information, choose one of the following three options: running-config, startup-config, or
a file system alias (see previous tables.) The location of a file system dictates the format of the source
or destination URL.
The colon is required after the alias. However, earlier commands not requiring a colon remain supported,
but are unavailable in context-sensitive help.
The entire copying process may take several minutes and differs from protocol to protocol and from
network to network.
In the alias syntax for ftp:, rcp:, and tftp:, the location is either an IP address or a host name. The
filename is specified relative to the directory used for file transfers.
This section contains usage guidelines for the following topics:
Understanding Partitions
Using rcp
Using FTP
Verifying Images
FR-185
Some invalid combinations of source and destination exist. Specifically, you cannot copy the following:
From a device to the same device (for example, the copy flash: flash: command is invalid)
Table 25 describes the characters that you may see during processing of the copy command.
Table 25
Character
Description
For network transfers, a period indicates that the copy process timed out.
Many periods in a row typically mean that the copy process may fail.
Understanding Partitions
You cannot copy an image or configuration file to a Flash partition from which you are currently running.
For example, if partition 1 is running the current system image, copy the configuration file or image to
partition 2. Otherwise, the copy operation will fail.
You can identify the available Flash partitions by entering the show file system EXEC command.
Using rcp
The rcp protocol requires a client to send a remote username upon each rcp request to a server. When
you copy a configuration file or image between the router and a server using rcp, the Cisco IOS software
sends the first valid username it encounters in the following sequence:
1.
2.
The username set by the ip rcmd remote-username global configuration command, if the command
is configured.
3.
The remote username associated with the current tty (terminal) process. For example, if the user is
connected to the router through Telnet and was authenticated through the username command, the
router software sends the Telnet username as the remote username.
4.
FR-186
78-11740-02
For the rcp copy request to process, an account must be defined on the network server for the remote
username. If the network administrator of the destination server did not establish an account for the
remote username, this command will not run. If the server has a directory structure, the configuration
file or image is written to or copied from the directory associated with the remote username on the server.
For example, if the system image resides in the home directory of a user on the server, specify that user
name as the remote username.
If you are writing to the server, the rcp server must be properly configured to accept the rcp write request
from the user on the router. For UNIX systems, add an entry to the .rhosts file for the remote user on the
rcp server. Suppose the router contains the following configuration lines:
hostname Rtr1
ip rcmd remote-username User0
If the router IP address translates to Router1.company.com, then the .rhosts file for User0 on the rcp
server should contain the following line:
Router1.company.com Rtr1
Refer to the documentation for your rcp server for more details.
If you are using a personal computer as a file server, the computer must support the remote shell protocol
(rsh).
Using FTP
The FTP protocol requires a client to send a remote username and password upon each FTP request to a
server. When you copy a configuration file from the router to a server using FTP, the Cisco IOS software
sends the first valid username that it encounters in the following sequence:
1.
2.
The username set by the ip ftp username command, if the command is configured.
3.
Anonymous.
The router sends the first valid password in the following list:
1.
2.
The password set by the ip ftp password command, if the command is configured.
3.
The username and password must be associated with an account on the FTP server. If you are writing to
the server, the FTP server must be properly configured to accept the FTP write request from the user on
the router.
If the server has a directory structure, the configuration file or image is written to or copied from the
directory associated with the username on the server. For example, if the system image resides in the
home directory of a user on the server, specify that user name as the remote username.
Refer to the documentation for your FTP server for more details.
Use the ip ftp username and ip ftp password global configuration commands to specify a username
and password for all copies. Include the username in the copy command if you want to specify a
username for that copy operation only.
FR-187
Use the copy flash: destination-url command (for example, copy flash: tftp:) to copy a system image
or boot image from Flash memory to a network server. Use the copy of the image as a backup copy. Also,
use it to verify that the copy in Flash memory is the same as that in the original file.
Copying from a Server to Flash Memory
Use the copy destination-url flash: command (for example, copy tftp: flash:) to copy an image from a
server to Flash memory.
On Class B file system platforms, the system provides an option to erase existing Flash memory before
writing onto it.
Note
When copying a new image to your router, you should confirm that the image was not corrupted during
the copy process. Depending on the destination filesystem type, a checksum for the image file may be
displayed when the copy command completes. You can verify this checksum by comparing it to the
checksum value provided for your image file on Cisco.com.
Caution
If the checksum values do not match, do not reboot the router. Instead, reissue the copy command
and compare the checksums again. If the checksum is repeatedly wrong, copy the original image back
into Flash memory before you reboot the router from Flash memory. If you have a corrupted image
in Flash memory and try to boot from Flash memory, the router will start the system image contained
in ROM (assuming booting from a network server is not configured). If ROM does not contain a fully
functional system image, the router might not function and will need to be reconfigured through a
direct console port connection.
An alternate method for file verification is to use the UNIX 'diff' command. This method can also be
applied to file types other than Cisco IOS images. If you suspect that a file is corrupted, copy the suspect
file and the original file to a Unix server. (The file names may need to be modified if you try to save the
files in the same directory.) Then run the Unix 'diff' command on the two files. If there is no difference,
then the file has not been corrupted.
Copying a Configuration File from a Server to the Running Configuration
Use the copy {ftp: | rcp: | tftp:} running-config command to load a configuration file from a network
server to the running configuration of the router (note that running-config is the alias for the
system:running-config keyword). The configuration will be added to the running configuration as if the
commands were typed in the command-line interface (CLI). Thus, the resulting configuration file will
be a combination of the previous running configuration and the loaded configuration file, with the loaded
configuration file having precedence.
You can copy either a host configuration file or a network configuration file. Accept the default value of
host to copy and load a host configuration file containing commands that apply to one network server in
particular. Enter network to copy and load a network configuration file containing commands that apply
to all network servers on a network.
FR-188
78-11740-02
Use the copy {ftp: | rcp: | tftp:} nvram:startup-config command to copy a configuration file from a
network server to the router startup configuration. These commands replace the startup configuration file
with the copied configuration file.
Storing the Running or Startup Configuration on a Server
Use the copy system:running-config {ftp: | rcp: | tftp:} command to copy the current configuration
file to a network server using FTP, rcp, or TFTP. Use the copy nvram:startup-config {ftp: | rcp: | tftp:}
command to copy the startup configuration file to a network server.
The configuration file copy can serve as a backup copy.
Saving the Running Configuration to the Startup Configuration
Note
Some specific commands might not get saved to NVRAM. You will need to enter these commands
again if you reboot the machine. These commands are noted in the documentation. We recommend
that you keep a listing of these settings so you can quickly reconfigure your router after rebooting.
If you issue the copy system:running-config nvram:startup-config command from a bootstrap system
image, a warning will instruct you to indicate whether you want your previous NVRAM configuration
to be overwritten and configuration commands to be lost. This warning does not appear if NVRAM
contains an invalid configuration or if the previous configuration in NVRAM was generated by a
bootstrap system image.
On all platforms except Class A file system platforms, the copy system:running-config
nvram:startup-config command copies the currently running configuration to NVRAM.
On the Class A Flash file system platforms, the copy system:running-config nvram:startup-config
command copies the currently running configuration to the location specified by the CONFIG_FILE
environment variable. This variable specifies the device and configuration file used for initialization.
When the CONFIG_FILE environment variable points to NVRAM or when this variable does not exist
(such as at first-time startup), the software writes the current configuration to NVRAM. If the current
configuration is too large for NVRAM, the software displays a message and stops executing the
command.
When the CONFIG_FILE environment variable specifies a valid device other than nvram: (that is,
flash:, bootflash:, slot0:, or slot1:), the software writes the current configuration to the specified device
and filename, and stores a distilled version of the configuration in NVRAM. A distilled version is one
that does not contain access list information. If NVRAM already contains a copy of a complete
configuration, the router prompts you to confirm the copy.
Using CONFIG_FILE, BOOT, and BOOTLDR Environment Variables
For the Class A Flash file system platforms, specifications are as follows:
The CONFIG_FILE environment variable specifies the configuration file used during router
initialization.
The BOOT environment variable specifies a list of bootable images on various devices.
The BOOT environment variable specifies a list of bootable images on various devices.
The BOOTLDR environment variable specifies the Flash device and filename containing the rxboot
image that ROM uses for booting.
FR-189
Cisco 3600 routers do not use a dedicated boot helper image (rxboot), which many other routers use
to help with the boot process. Instead, the BOOTLDR ROM monitor environment variable identifies
the Flash memory device and filename that are used as the boot helper; the default is the first system
image in Flash memory.
To view the contents of environment variables, use the show bootvar EXEC command. To modify the
CONFIG_FILE environment variable, use the boot config global configuration command. To modify the
BOOTLDR environment variable, use the boot bootldr global configuration command. To modify the
BOOT environment variable, use the boot system global configuration command. To save your
modifications, use the copy system:running-config nvram:startup-config command.
When the destination of a copy command is specified by the CONFIG_FILE or BOOTLDR environment
variable, the router prompts you for confirmation before proceeding with the copy. When the destination
is the only valid image in the BOOT environment variable, the router also prompts you for confirmation
before proceeding with the copy.
Using the Copy Command with the Dual RSP Feature
The Dual RSP feature allows you to install two Route/Switch Processor (RSP) cards in a single router
on the Cisco 7507 and Cisco 7513 platforms.
On a Cisco 7507 or Cisco 7513 router configured for Dual RSPs, if you copy a file to
nvram:startup-configuration with automatic synchronization disabled, the system asks if you also
want to copy the file to the slave startup configuration. The default answer is yes. If automatic
synchronization is enabled, the system automatically copies the file to the slave startup configuration
each time you use a copy command with nvram:startup-configuration as the destination.
Examples
Copying an Image from the Master RSP Card to the Slave RSP Card Example
The following three examples use a copy rcp:, copy tftp:, or copy ftp: command to copy an image file
from a server to Flash memory:
Copying an Image from a Server to a Flash Memory Using Flash Load Helper Example
FR-190
78-11740-02
This example copies a system image named file1 from the remote rcp server with an IP address of
172.16.101.101 to Flash memory. On Class B file system platforms, the Cisco IOS software allows you
to first erase the contents of Flash memory to ensure that enough Flash memory is available to
accommodate the system image.
Router# copy rcp://[email protected]/file1 flash:file1
Destination file name [file1]?
Accessing file 'file1' on 172.16.101.101...
Loading file1 from 172.16.101.101 (via Ethernet0): ! [OK]
Erase flash device before writing? [confirm]
Flash contains files. Are you sure you want to erase? [confirm]
Copy 'file1' from server
as 'file1' into Flash WITH erase? [yes/no] yes
Erasing device... eeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee...erased
Loading file1 from 172.16.101.101 (via Ethernet0): !
[OK - 984/8388608 bytes]
Verifying checksum... OK (0x14B3)
Flash copy took 0:00:01 [hh:mm:ss]
Copying an Image from a Server to a Flash Memory Using Flash Load Helper Example
The following example copies a system image into a partition of Flash memory. The system will prompt
for a partition number only if there are two or more read/write partitions or one read-only and one
read/write partition and dual Flash bank support in boot ROMs. If the partition entered is not valid, the
process terminates. You can enter a partition number, a question mark (?) for a directory display of all
partitions, or a question mark and a number (?number) for directory display of a particular partition. The
default is the first read/write partition. In this case, the partition is read-only and has dual Flash bank
support in boot ROM, so the system uses Flash Load Helper.
Router# copy tftp: flash:
System flash partition information:
Partition
Size
Used
Free
1
4096K
2048K
2048K
2
4096K
2048K
2048K
Bank-Size
2048K
2048K
State
Read Only
Read/Write
Copy-Mode
RXBOOT-FLH
Direct
FR-191
The following example copies the file c3600-i-mz from the rcp server at IP address 172.23.1.129 to the
Flash memory card in slot 0 of a Cisco 3600 series router, which has only one partition. As the operation
progresses, the Cisco IOS software asks you to erase the files on the Flash memory PC card to
accommodate the incoming file. This entire operation takes 18 seconds to perform, as indicated at the
end of the example.
Router# copy rcp: slot0:
PCMCIA Slot0 flash
Partition
1
2
3
4
Size
4096K
4096K
4096K
4096K
Used
3068K
1671K
0K
3825K
Free
1027K
2424K
4095K
270K
Bank-Size
4096K
4096K
4096K
4096K
State
Read/Write
Read/Write
Read/Write
Read/Write
Copy Mode
Direct
Direct
Direct
Direct
FR-192
78-11740-02
The following four examples use copy commands to copy image files to a server for storage:
Copying an Image from a Flash Memory File System to an FTP Server Example
The following example copies a system image from Flash Memory to an rcp server using the default
remote username. Because the rcp server address and filename are not included in the command, the
router prompts for it.
Router# copy flash: rcp:
IP address of remote host [255.255.255.255]? 172.16.13.110
Name of file to copy? gsxx
writing gsxx - copy complete
The following example copies an image from a particular partition of Flash memory to an rcp server
using a remote username of netadmin1.
The system will prompt if there are two or more partitions. If the partition entered is not valid, the
process terminates. You have the option to enter a partition number, a question mark (?) for a directory
display of all partitions, or a question mark and a number (?number) for a directory display of a
particular partition. The default is the first partition.
Router# configure terminal
Router# ip rcmd remote-username netadmin1
Router# end
Router# copy flash: rcp:
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
[Type ?<number> for partition directory; ? for full directory; q to abort]
Which partition? [1] 2
System flash directory, partition 2:
File Length
Name/status
1
3459720 master/igs-bfpx.100-4.3
[3459784 bytes used, 734520 available, 4194304 total]
Address or name of remote host [ABC.CISCO.COM]?
Source file name? master/igs-bfpx.100-4.3
Destination file name [master/igs-bfpx.100-4.3]?
Verifying checksum for 'master/igs-bfpx.100-4.3' (file # 1)... OK
Copy 'master/igs-bfpx.100-4.3' from Flash to server
as 'master/igs-bfpx.100-4.3'? [yes/no] yes
!!!!...
Upload to server done
Flash copy took 0:00:00 [hh:mm:ss]
Copying an Image from a Flash Memory File System to an FTP Server Example
The following example copies the file c3600-i-mz from partition 1 of the Flash memory card in slot 0 to
an FTP server at IP address 172.23.1.129.
FR-193
The following example copies an image from boot Flash memory to a TFTP server:
Router# copy bootflash:file1 tftp://192.168.117.23/file1
Verifying checksum for 'file1' (file # 1)... OK
Copy 'file1' from Flash to server
as 'file1'? [yes/no]y
!!!!...
Upload to server done
Flash copy took 0:00:00 [hh:mm:ss]
The following example copies and runs a configuration filename host1-confg from the netadmin1
directory on the remote server with an IP address of 172.16.101.101:
Router# copy rcp://[email protected]/host1-confg system:running-config
Configure using host1-confg from 172.16.101.101? [confirm]
Connected to 172.16.101.101
Loading 1112 byte file host1-confg:![OK]
Router#
%SYS-5-CONFIG: Configured from host1-config by rcp from 172.16.101.101
The following example copies a configuration file host2-confg from a remote FTP server to the startup
configuration. The IP address is172.16.101.101, the remote username is netadmin1, and the remote
password is ftppass.
Router# copy ftp://netadmin1:[email protected]/host2-confg nvram:startup-config
Configure using rtr2-confg from 172.16.101.101?[confirm]
Connected to 172.16.101.101
Loading 1112 byte file rtr2-confg:![OK]
[OK]
Router#
%SYS-5-CONFIG_NV:Non-volatile store configured from rtr2-config by
FTP from 172.16.101.101
The following example specifies a remote username of netadmin1. Then it copies the running
configuration file named rtr2-confg to the netadmin1 directory on the remote host with an IP address of
172.16.101.101.
FR-194
78-11740-02
The following example copies the running configuration to the startup configuration. On a Class A Flash
file system platform, this command copies the running configuration to the startup configuration
specified by the CONFIG_FILE variable.
copy system:running-config nvram:startup-config
The following example shows the warning that the system provides if you try to save configuration
information from bootstrap into the system:
Router(boot)# copy system:running-config nvram:startup-config
Warning: Attempting to overwrite an NVRAM configuration written
by a full system image. This bootstrap software does not support
the full configuration command set. If you perform this command now,
some configuration commands may be lost.
Overwrite the previous NVRAM configuration?[confirm]
On some routers, you can store copies of configuration files on a Flash memory device. Five examples
follow.
Copying the Startup Configuration to a Flash Memory Device Example
The following example copies the startup configuration file (specified by the CONFIG_FILE
environment variable) to a Flash memory card inserted in slot 0:
copy nvram:startup-config slot0:router-confg
The following example copies the running configuration from the router to the Flash memory PC card
in slot 0:
Router# copy system:running-config slot0:berlin-cfg
Building configuration...
FR-195
The following example copies the file named ios-upgrade-1 from the Flash memory card in slot 0 to the
running configuration:
Router# copy slot0:4:ios-upgrade-1 system:running-config
Copy 'ios-upgrade-1' from flash device
as 'running-config' ? [yes/no] yes
The following example copies the router-image file from the Flash memory to the startup configuration:
copy flash:router-image nvram:startup-config
The following example copies the file running-config from the first partition in internal Flash memory
to the Flash memory PC card in slot 1. The checksum of the file is verified, and its copying time of 30
seconds is displayed.
Router# copy flash: slot1:
System flash
Partition
1
2
Size
4096K
16384K
Used
3070K
1671K
Free
1025K
14712K
Bank-Size
4096K
8192K
State
Read/Write
Read/Write
Copy Mode
Direct
Direct
FR-196
78-11740-02
Copying an Image from the Master RSP Card to the Slave RSP Card Example
The following example copies the router-image file from the Flash memory card inserted in slot 1 of the
master RSP card to slot 0 of the slave RSP card in the same router:
copy slot1:router-image slaveslot0:
Related Commands
Command
Description
boot config
Specifies the device and filename of the configuration file from which the
router configures itself during initialization (startup).
boot system
cd
delete
dir
erase
ip rcmd
remote-username
reload
show bootvar
Displays the contents of the BOOT environment variable, the name of the
configuration file pointed to by the CONFIG_FILE environment variable,
the contents of the BOOTLDR environment variable, and the
configuration register setting.
verify bootflash:
FR-197
delete
To delete a file from a Flash memory device or NVRAM, use the delete EXEC command.
delete URL [/force | /recursive]
Syntax Description
URL
/force
/recursive
Use this keyword with caution: the system will not ask you to
confirm the file deletion.
Command Modes
EXEC
Command History
Release
Modification
11.0
Usage Guidelines
If you attempt to delete the configuration file or image specified by the CONFIG_FILE or BOOTLDR
environment variable, the system prompts you to confirm the deletion. Also, if you attempt to delete the
last valid system image specified in the BOOT environment variable, the system prompts you to confirm
the deletion.
When you delete a file in Flash memory, the software simply marks the file as deleted, but it does not
erase the file. To later recover a deleted file in Flash memory (Class A only), use the undelete EXEC
command. You can delete and undelete a file up to 15 times.
To permanently delete all files marked deleted on a linear Flash memory device, use the squeeze
EXEC command.
Examples
The following example deletes the file named test from the Flash filesystem:
Router# delete flash:test
Delete flash:test? [confirm]
Related Commands
Command
Description
cd
dir
FR-198
78-11740-02
Command
Description
show bootvar
Displays the contents of the BOOT environment variable, the name of the
configuration file pointed to by the CONFIG_FILE environment variable,
the contents of the BOOTLDR environment variable, and the configuration
register setting.
squeeze
undelete
FR-199
dir
To display a list of files on a file system, use the dir EXEC command.
dir [/all] [filesystem: ][file-url]
Syntax Description
/all
(Optional) Lists deleted files, undeleted files, and files with errors.
filesystem:
file-url
Defaults
The default file system is specified by the cd command. When you omit the /all keyword, the Cisco IOS
software displays only undeleted files.
Command Modes
EXEC
Command History
Release
Modification
11.0
Usage Guidelines
Use the show (Flash file system) command to display more detail about the files in a particular file
system.
Examples
-rw-rw-rw-rw-
4720148
4767328
639
639
Aug
Oct
Oct
Oct
29
01
02
02
1997
1997
1997
1997
17:49:36 hampton/nitro/c7200-j-mz
18:42:53 c7200-js-mz
12:09:32 rally
12:37:13 the_time
-rw-rw-rw-rw-
4720148
4767328
7982828
639
Aug
Oct
Oct
Oct
29
01
01
02
1997
1997
1997
1997
17:49:36
18:42:53
18:48:14
12:09:17
hampton/nitro/c7200-j-mz
c7200-js-mz
[rsp-jsv-mz]
[the_time]
FR-200
78-11740-02
5
6
7
-rw-rw-rw-
639
639
639
rally
[the_time]
the_time
Related Commands
Field
Description
-rw-
ddirectory
rreadable
wwritable
xexecutable
4720148
hampton/nitro/c7200-j-mz
Command
Description
cd
delete
undelete
FR-201
erase
To erase a file system, use the erase EXEC command. The erase nvram: command replaces the write
erase command and the erase startup-config command.
erase filesystem:
Syntax Description
filesystem:
Command Modes
EXEC
Command History
Release
Modification
11.0
Usage Guidelines
When a file system is erased, none of the files in the file system can be recovered.
The erase command can be used on both Class B and Class C Flash file systems only. To reclaim space
on Flash file systems after deleting files using the delete command, you must use the erase command.
This command erases all of the files in the Flash file system.
Class A Flash file systems cannot be erased. You can delete individual files using the delete EXEC
command and then reclaim the space using the squeeze EXEC command. You can use the format EXEC
command to format the Flash file system.
On Class C Flash file systems, space is dynamically reclaimed when you use the delete command. You
can also use either the format or erase command to reinitialize a Class C Flash file system.
The erase nvram: command erases NVRAM. On Class A file system platforms, if the CONFIG_FILE
variable specifies a file in Flash memory, the specified file will be marked deleted.
Examples
The following example erases the NVRAM, including the startup configuration located there:
erase nvram:
The following example erases Flash memory when Flash is partitioned, but no partition is specified in
the command:
FR-202
78-11740-02
Bank-Size
2048K
2048K
State
Read Only
Read/Write
Copy-Mode
RXBOOT-FLH
Direct
The system will prompt only if there are two or more read/write partitions. If the partition entered is not
valid or is the read-only partition, the process terminates. You can enter a partition number, a question
mark (?) for a directory display of all partitions, or a question mark and a number (?number) for
directory display of a particular partition. The default is the first read/write partition.
System flash directory, partition 2:
File Length
Name/status
1
3459720 master/igs-bfpx.100-4.3
[3459784 bytes used, 734520 available, 4194304 total]
Erase flash device, partition 2? [confirm] <Return>
Related Commands
Command
Description
boot config
Specifies the device and filename of the configuration file from which
the router configures itself during initialization (startup).
delete
more
nvram:startup-config
show bootvar
undelete
FR-203
erase bootflash
The erase bootflash: and erase bootflash commands have identical functions. See the description of the
erase command in this chapter for more information.
FR-204
78-11740-02
file prompt
To specify the level of prompting, use the file prompt global configuration command.
file prompt [alert | noisy | quiet]
Syntax Description
alert
noisy
quiet
Defaults
alert
Command Modes
Global configuration
Command History
Release
Modification
11.0
Usage Guidelines
Use this command to change the amount of confirmation needed for different file operations.
This command affects only prompts for confirmation of operations. The router will always prompt for
missing information.
Examples
The following example configures confirmation prompting for all file operations:
file prompt noisy
FR-205
format
To format a Class A or Class C Flash file system, use the format EXEC command.
Class C Flash File System
format filesystem1:
Class A Flash File System
Caution
Syntax Description
Reserve a certain number of memory sectors as spares, so that if some sectors fail, most of the Flash
memory card can still be used. Otherwise, you must reformat the Flash card when some of the sectors
fail.
spare
spare-number
filesystem1:
filesystem2:
monlib-filename
(Optional) Name of the ROM monitor library file (monlib file) to use
for formatting the filesystem1 argument. The default monlib file is the
one bundled with the system software.
When used with HSA and you do not specify the monlib-filename
argument, the system takes ROM monitor library file from the slave
image bundle. If you specify the monlib-filename argument, the
system assumes that the files reside on the slave devices.
Defaults
The default monlib file is the one bundled with the system software.
The default number of spare sectors is zero (0).
Command Modes
EXEC
Command History
Release
Modification
11.0
Usage Guidelines
FR-206
78-11740-02
In some cases, you might need to insert a new PCMCIA Flash memory card and load images or backup
configuration files onto it. Before you can use a new Flash memory card, you must format it.
Sectors in Flash memory cards can fail. Reserve certain Flash memory sectors as spares by using the
optional spare argument on the format command to specify 0 to 16 sectors as spares. If you reserve a
small number of spare sectors for emergencies, you can still use most of the Flash memory card. If you
specify 0 spare sectors and some sectors fail, you must reformat the Flash memory card, thereby erasing
all existing data.
The monlib file is the ROM monitor library. The ROM monitor uses this file to access files in the Flash
file system. The Cisco IOS system software contains a monlib file.
In the command syntax, filesystem1: specifies the device to format and filesystem2: specifies the optional
device containing the monlib file used to format filesystem1:. If you omit the optional filesystem2: and
monlib-filename arguments, the system formats filesystem1: using the monlib file already bundled with
the system software. If you omit only the optional filesystem2: argument, the system formats
filesystem1: using the monlib file from the device you specified with the cd command. If you omit only
the optional monlib-filename argument, the system formats filesystem1: using the filesystem2: monlib
file. When you specify both argumentsfilesystem2: and monlib-filenamethe system formats
filesystem1: using the monlib file from the specified device. You can specify filesystem1:s own monlib
file in this argument. If the system cannot find a monlib file, it terminates its formatting.
Caution
Examples
You can read from or write to Flash memory cards formatted for Cisco 7000 series Route Processor
(RP) cards in your Cisco 7200 and 7500 series routers, but you cannot boot the Cisco 7200 and 7500
series routers from a Flash memory card formatted for the Cisco 7000 series routers. Similarly, you
can read from or write to Flash memory cards formatted for the Cisco 7200 and 7500 series routers
in your Cisco 7000 series routers, but you cannot boot the Cisco 7000 series routers from a Flash
memory card formatted for the Cisco 7200 and 7500 series routers.
When the console returns to the EXEC prompt, the new Flash memory card is formatted and ready for
use.
Related Commands
Command
Description
cd
copy
delete
FR-207
Command
Description
squeeze
undelete
FR-208
78-11740-02
fsck
To check a Class C Flash file system for damage and repair any problems, use the fsck EXEC command.
fsck [/nocrc] filesystem:
Syntax Description
/nocrc
filesystem:
Command Modes
EXEC
Command History
Release
Modification
11.3 AA
Usage Guidelines
Examples
FR-209
mkdir
To create a new directory in a Class C Flash file system, use the mkdir EXEC command.
mkdir directory
Syntax Description
directory
Command Modes
EXEC
Command History
Release
Modification
11.3 AA
Usage Guidelines
Examples
drwx
newdir
Related Commands
Command
Description
dir
rmdir
FR-210
78-11740-02
more
To display a file, use the more EXEC command.
more [/ascii | /binary | /ebcdic] file-url
Syntax Description
/ascii
/binary
/ebcdic
file-url
Command Modes
EXEC
Command History
Release
Modification
11.3 AA
Usage Guidelines
The more system:running-config command displays the same output as the show running-config
command. The more nvram:startup-config command replaces the show startup-config command and
the show configuration command.
You can use this command to display configuration files, as follows:
The more nvram:startup-config command displays the startup configuration file contained in
NVRAM or specified by the CONFIG_FILE environment variable. The Cisco IOS software informs
you whether the displayed configuration is a complete configuration or a distilled version. A
distilled configuration is one that does not contain access lists.
These commands show the version number of the software used when you last changed the configuration
file.
You can display files on remote systems using the more command.
Examples
The following partial sample output displays the configuration file named startup-config in NVRAM:
Router# more nvram:startup-config
!
! No configuration change since last restart
! NVRAM config last updated at 02:03:26 PDT Thu Oct 2 1997
!
version 12.1
service timestamps debug uptime
service timestamps log uptime
service password-encryption
service udp-small-servers
service tcp-small-servers
.
FR-211
.
.
end
The following is partial sample output from the more nvram:startup-config command when the
configuration file has been compressed:
Router# more nvram:startup-config
Using 21542 out of 65536 bytes, uncompressed size = 142085 bytes
!
version 12.1
service compress-config
!
hostname rose
!
.
.
.
Related Commands
Command
Description
boot config
Specifies the device and filename of the configuration file from which the
router configures itself during initialization (startup).
service
compress-config
show bootvar
Displays the contents of the BOOT environment variable, the name of the
configuration file pointed to by the CONFIG_FILE environment variable,
the contents of the BOOTLDR environment variable, and the configuration
register setting.
FR-212
78-11740-02
pwd
To show the current setting of the cd command, use the pwd EXEC command.
pwd
Syntax Description
Command Modes
EXEC
Command History
Release
Modification
11.0
Usage Guidelines
Use the pwd command to show which directory or file system is specified as the default by the cd
command. For all EXEC commands that have an optional filesystem argument, the system uses the file
system specified by the cd command when you omit the optional filesystem argument.
For example, the dir command contains an optional filesystem argument and displays a list of files on a
particular file system. When you omit this filesystem argument, the system shows a list of the files on
the file system specified by the cd command.
Examples
The following example shows that the present working file system specified by the cd command is slot 0:
Router> pwd
slot0:/
The following example uses the cd command to change the present file system to slot 1 and then uses
the pwd command to display that present working file system:
Router> cd slot1:
Router> pwd
slot1:/
Related Commands
Command
Description
cd
dir
FR-213
rename
To rename a file in a Class C Flash file system, use the rename EXEC command.
rename url1 url2
Syntax Description
url1
url2
Command Modes
EXEC
Command History
Release
Modification
11.3 AA
Usage Guidelines
Examples
-rw-rw-rw-rw-rw-
0
0
0
0
165
Jan
Jan
Jan
Jan
Jan
21
21
21
21
21
1998
1998
1998
1998
1998
09:51:29
09:51:29
09:51:29
09:51:31
09:53:17
Karen.1
Karen.2
Karen.3
Karen.4
Karen.cur
-rw-rw-rw-rw-rw-
0
0
0
165
0
Jan
Jan
Jan
Jan
Apr
21
21
21
21
24
1998
1998
1998
1998
1998
09:51:29
09:51:29
09:51:31
09:53:17
09:49:19
Karen.2
Karen.3
Karen.4
Karen.cur
test
FR-214
78-11740-02
rmdir
To remove an existing directory in a Class C Flash file system, use the rmdir EXEC command.
rmdir directory
Syntax Description
directory
Command Modes
EXEC
Command History
Release
Modification
11.3 AA
Directory to delete.
Usage Guidelines
Examples
drwx
newdir
Related Commands
Command
Description
dir
mkdir
FR-215
show configuration
The show configuration command is replaced by the show startup-config and more
nvram:startup-config commands. See the description of the show startup-config and more commands
for more information.
FR-216
78-11740-02
Syntax Description
Command Modes
EXEC
Command History
Release
Modification
11.3 AA
Usage Guidelines
File descriptors are the internal representations of open files. You can use this command to learn if
another user has a file open.
Examples
The following is sample output from the show file descriptors command:
Router# show file descriptors
File Descriptors:
FD
0
1
Position
187392
184320
Open
0001
030A
PID
2
2
Path
tftp://dirt/hampton/c4000-i-m.a
flash:c4000-i-m.a
Field
Description
FD
Position
Open
PID
Path
FR-217
Syntax Description
file-url
Command Modes
EXEC
Command History
Release
Modification
11.3 AA
Examples
The following is sample output from the show file information command:
Router# show file information tftp://dirt/hampton/c2500-j-l.a
tftp://dirt/hampton/c2500-j-l.a:
type is image (a.out) [relocatable, run from flash]
file size is 8624596 bytes, run size is 9044940 bytes [8512316+112248+420344]
Foreign image
Router# show file information slot0:c7200-js-mz
slot0:c7200-js-mz:
type is image (elf) []
file size is 4770316 bytes, run size is 4935324 bytes
Runnable image, entry point 0x80008000, run from ram
Router1# show file information nvram:startup-config
nvram:startup-config:
type is ascii text
Types
Description
image (a.out)
image (elf)
ascii text
coff
ebcdic
lzw compression
tar
FR-218
78-11740-02
Syntax Description
Command Modes
EXEC
Command History
Release
Modification
11.3 AA
Usage Guidelines
Use this command to learn the alias names (Prefixes) of the file systems your router supports.
Examples
The following is sample output from the show file systems command:
Router# show file systems
File Systems:
Size(b)
4194304
131066
-
Free(b)
Type
opaque
opaque
opaque
opaque
network
network
network
4190616
flash
129185
nvram
opaque
Flags
rw
rw
ro
ro
rw
rw
rw
rw
rw
wo
Prefixes
null:
system:
xmodem:
ymodem:
tftp:
rcp:
ftp:
flash:
nvram:
lex:
Type
Description
Size(b)
Free(b)
Type
Flags
Prefixes
disk
flash
FR-219
Table 29
Type
Description
network
The file system is a network file system (TFTP, rcp, FTP, and so
on).
nvram
opaque
rom
tty
unknown
Flag
Description
ro
wo
rw
FR-220
78-11740-02
squeeze
To permanently erase files tagged as deleted or error on Class A Flash file systems, use the squeeze
command in EXEC mode.
squeeze [/nolog] [/quiet] filesystem:
Syntax Description
/nolog
/quiet
filesystem:
Command Modes
EXEC
Command History
Release
Modification
11.1
12.2(1)
This command was implemented in images for the Cisco 2600 and Cisco
3600 series.
12.2(4)XL
This command was implemented in images for the Cisco 1700 series.
12.1(9), 12.0(17)S
12.0(17)ST, 12.2(2),
12.2(2)T, 12.2(2)B,
12.1(9)E
Usage Guidelines
When Flash memory is full, you might need to rearrange the files so that the space used by the files
marked deleted can be reclaimed. (This squeeze process is required for linear Flash memory cards
to make sectors contiguous; the free memory must be in a block to be usable.)
When you enter the squeeze command, the router copies all valid files to the beginning of Flash memory
and erases all files marked deleted. After the squeeze process is completed, you can write to the
reclaimed Flash memory space.
Caution
After performing the squeeze process you cannot recover deleted files using the undelete EXEC
mode command.
In addition to removing deleted files, the squeeze command removes any files that the system has
marked as error. An error file is created when a file write fails (for example, the device is full). To
remove error files, you must use the squeeze command.
Rewriting Flash memory space during the squeeze operation may take several minutes.
Using the /nolog keyword disables the log for the squeeze process. In most cases this will speed up the
squeeze process. However, if power is lost or the Flash card is removed during the squeeze process, all
the data on the Flash card will be lost, and the device will have to be reformatted.
FR-221
Note
Examples
Step 1
If the Flash file system has multiple partitions, enter the no partition command to remove the partitions.
The reason for removing partitions is to ensure that the entire Flash file system is erased. The squeeze
command can be used in a Flash file system with partitions after the Flash file system is erased once.
Step 2
In the following example, the file named config1 is deleted, and then the squeeze command is used to
reclaim the space used by that file. The /nolog option is used to speed up the squeeze process.
Router# delete config1
Delete filename [config1]?
Delete slot0:conf? [confirm]
Router# dir slot0:
! Note that the deleted file name appears in square brackets
Directory of slot0:/
1 -rw4300244
Apr 02 2001 03:18:07 c7200-boot-mz.122-0.14
2 -rw2199
Apr 02 2001 04:45:15 [config1]
3 -rw4300244
Apr 02 2001 04:45:23 image
20578304 bytes total (11975232 bytes free)
!20,578,304 - 4,300,244 - 4,300,244 - 2,199 - 385 = 11975232
-rw-rw-
4300244
4300244
c7200-boot-mz.122-0.14
image
FR-222
78-11740-02
Related Commands
Command
Description
delete
dir
undelete
FR-223
undelete
To recover a file marked deleted on a Class A Flash file system, use the undelete EXEC command.
undelete index [filesystem:]
Syntax Description
index
filesystem:
Defaults
Command Modes
EXEC
Command History
Release
Modification
11.0
This command was introduced for Class A Flash File Systems (platforms
include the Cisco 7500 series and Cisco 12000 series).
Usage Guidelines
For Class A Flash file systems, when you delete a file, the Cisco IOS software simply marks the file as
deleted, but it does not erase the file. This command allows you to recover a deleted file on a specified
Flash memory device. You must undelete a file by its index because you could have multiple deleted files
with the same name. For example, the deleted list could contain multiple configuration files with the
name router-config. You undelete by index to indicate which of the many router-config files from the list
to undelete. Use the dir command to learn the index number of the file you want to undelete.
You cannot undelete a file if a valid (undeleted) file with the same name exists. Instead, you first delete
the existing file and then undelete the file you want. For example, if you had an undeleted version of the
router-config file and you wanted to use a previous, deleted version instead, you could not simply
undelete the previous version by index. You would first delete the existing router-config file and then
undelete the previous router-config file by index. You can delete and undelete a file up to 15 times.
On Class A Flash file systems, if you try to recover the configuration file pointed to by the
CONFIG_FILE environment variable, the system prompts you to confirm recovery of the file. This
prompt reminds you that the CONFIG_FILE environment variable points to an undeleted file. To
permanently delete all files marked deleted on a Flash memory device, use the squeeze EXEC
command.
Examples
The following example recovers the deleted file whose index number is 1 to the Flash memory card
inserted in slot 0:
undelete 1 slot0:
Related Commands
FR-224
78-11740-02
Command
Description
delete
dir
squeeze
FR-225
verify
To verify the checksum of a file on a Flash memory file system, use the verify EXEC command.
verify filesystem:[file-url]
Syntax Description
filesystem:
file-url
Defaults
Command Modes
EXEC
Command History
Release
Modification
11.0
Usage Guidelines
This command replaces the copy verify and copy verify flash commands.
Use the verify command to verify the checksum of a file before using it.
Each software image that is distributed on disk uses a single checksum for the entire image. This
checksum is displayed only when the image is copied into Flash memory; it is not displayed when the
image file is copied from one disk to another.
To display the contents of Flash memory, use the show flash command. The Flash contents listing does
not include the checksum of individual files. To recompute and verify the image checksum after the
image has been copied into Flash memory, use the verify command.
Note
The verify command only performs a check on the integrity of the file after it has been saved in the file
system. It is possible for a corrupt image to be transferred to the router and saved in the file system
without detection.
To verify that a Cisco IOS software image was not corrupted while it was transfered to the router, copy
the image from where it is stored on your router to a Unix server. Also copy the same image from CCO
(Cisco.com) to the same Unix server. (The name may need to be modified if you try to save the image
in the same directory as the image that you copied from the router.) Then run a Unix diff command on
the two Cisco IOS software images. If there is no difference then the image stored on the router has not
been corrupted.
FR-226
78-11740-02
Examples
The following example verifies that the file named c7200-js-mz is on the Flash memory card inserted in
slot 0:
Router# dir slot0:
Directory of slot0:/
1
2
5
7
-rw-rw-rw-rw-
4720148
4767328
639
639
Aug
Oct
Oct
Oct
29
01
02
02
1997
1997
1997
1997
17:49:36
18:42:53
12:09:32
12:37:13
hampton/nitro/c7200-j-mz
c7200-js-mz
rally
the_time
The following example also verifies that the file named c7200-js-mz is on the Flash memory card
inserted in slot 0:
Router# verify slot0:?
slot0:c7200-js-mz slot0:rally slot0:hampton/nitro/c7200-j-mz
slot0:the_time
Related Commands
Command
Description
cd
copy
dir
pwd
FR-227
write erase
The write erase command is replaced by the erase nvram: command. See the description of the erase
command in this chapter for more information.
FR-228
78-11740-02
write terminal
The more system:running-config command replaces the write terminal command. See the description
of the more command in this chapter for more information.
FR-229
FR-230
78-11740-02
Type
Platforms
Class A
Class B
Cisco 1003, Cisco 1004, Cisco 1005, Cisco 2500 series, Cisco 3600
series, and Cisco 4000 series routers, and Cisco AS5200 access servers
Class C
Replaced Commands
Some commands found in this chapter in previous releases of this book have been replaced. Older
commands generally continue to provide the same functionality in the current release, but are no longer
documented. Support for the older version of these commands may already be removed on your system,
or may be removed in a future Cisco IOS software release.
Table 32 maps the old commands to their replacements.
FR-231
Table 32
Replaced Commands
Old Command
New Command
configure network
copy ftp:[[[//[username[:password]@]location]/directory]/filename]
system:running-config
configure
overwrite-network
copy ftp:[[[//[username[:password]@]location]/directory]/filename]
nvram:startup-config
copy rcp:[[[//[username@]location]/directory]/filename]
system:running-config
copy system:running-config
rcp:[[[//[username@]location]/directory]/filename]
copy running-config
startup-config
erase startup-config
erase nvram:
show configuration
more nvram:startup-config
show file
more
show running-config
more system:running-config
Note
Note
show startup-config
more nvram:startup-config
Note
write erase
erase nvram:
write memory
FR-232
78-11740-02
Table 32
Old Command
New Command
write network
copy system:running-config
ftp:[[[//[username[:password]@]location]/directory]/filename]
write terminal
show running-config
or
more system:running-config
For more information about these command replacements, see the description of the Cisco IOS File
System (IFS) in the Using the Cisco IOS File System chapter in the Release 12.2 Cisco IOS
Configuration Fundamentals Configuration Guide.
FR-233
boot buffersize
The boot buffersize global configuration command no longer functions.
Executing this command has no effect on the system. Using this command will not generate CLI errors;
the boot buffersize command syntax is still allowed to be entered at the CLI and in configuration files
in order to accommodate existing configuration scripts used by customers.
FR-234
78-11740-02
boot config
To specify the device and filename of the configuration file from which the router configures itself
during initialization (startup), use the boot config global configuration command. This command is only
available on Class A file system platforms. To remove the specification, use the no form of this
command.
boot config file-system-prefix:[directory/]filename
no boot config
Syntax Description
file-system-prefix:
directory/
filename
Defaults
NVRAM (nvram:)
Command Modes
Global configuration
Command History
Release
Modification
11.0
Usage Guidelines
Note
When you use this global configuration command, you affect only the running configuration. You must
save the environment variable setting to your startup configuration to place the information under ROM
monitor control and to have the environment variable function as expected. Use the copy
system:running-config nvram:startup-config command to save the environment variable from your
running configuration to your startup configuration.
The software displays an error message and does not update the CONFIG_FILE environment variable in
the following situations:
You specify nvram: as the file system, and it contains only a distilled version of the configuration.
(A distilled configuration is one that does not contain access lists.)
You specify a configuration file in the filename argument that does not exist or is not valid.
FR-235
The router uses the NVRAM configuration during initialization when the CONFIG_FILE environment
variable does not exist or when it is null (such as at first-time startup). If the software detects a problem
with NVRAM or the configuration it contains, the device enters setup mode. See the Setup Command
chapter in this publication for more information on the setup command facility.
When you use the no form of this command, the router returns to using the default NVRAM
configuration file as the startup configuration.
Examples
In the following example, the first line specifies that the router should use the configuration file named
router-config located in internal Flash memory to configure itself during initialization. The third line
copies the specification to the startup configuration, ensuring that this specification will take effect upon
the next reload.
Router(config)# boot config flash:router-config
Router(config)# end
Router# copy system:running-config nvram:startup-config
The following example instructs a Cisco 7500 series router to use the configuration file named
router-config located on the Flash memory card inserted in the second PCMCIA slot of the RSP card
during initialization. The third line copies the specification to the startup configuration, ensuring that
this specification will take effect upon the next reload.
Router (config)# boot config slot1:router-config
Router (config)# end
Router# copy system:running-config nvram:startup-config
Related Commands
Command
Description
show bootvar
Displays the contents of the BOOT environment variable, the name of the
configuration file pointed to by the CONFIG_FILE environment variable,
the contents of the BOOTLDR environment variable, and the configuration
register setting.
FR-236
78-11740-02
boot host
To specify the host-specific configuration file to be used at the next system startup, use the boot host
global configuration command. To restore the host configuration filename to the default, use the no form
of this command.
boot host remote-url
no boot host remote-url
Syntax Description
remote-url
ftp:[[[//[username[:password]@]location]/directory]/filename]
rcp:[[[//[username@]location]/directory]/filename]
tftp:[[[//location]/directory]/filename]
Defaults
If you do not specify a filename using this command, the router uses its configured host name to request
a configuration file from a remote server. To form the configuration filename, the router converts its
name to all lowercase letters, removes all domain information, and appends -confg or -config.
Command Modes
Global configuration
Command History
Release
Modification
10.0
Usage Guidelines
This command instructs the system to Boot using network configuration file x, where x is the filename
specified in the remote-url argument. This command specifies the remote location and filename of the
network configuration file to be used at the next system startup, as well as the protocol to be used to
obtain the file.
When booting from a network server, routers ignore routing information, static IP routes, and bridging
information. As a result, intermediate routers are responsible for handling FTP, rcp, or TFTP requests.
Before booting from a network server, verify that a server is available by using the ping command.
Use the service config command to enable the loading of the specified configuration file at reboot time.
Without this command, the router ignores the boot network command and uses the configuration
information in NVRAM. If the configuration information in NVRAM is invalid or missing, the service
config command is enabled automatically.
The network server will attempt to load two configuration files from remote hosts. The first is the
network configuration file containing commands that apply to all network servers on a network. Use the
boot network command to identify the network configuration file. The second is the host configuration
file containing commands that apply to one network server in particular. Use the boot host command to
identify the host configuration file.
FR-237
Note
In releases prior to Cisco IOS Release 12.3(2)T and 12.3(1)B, the service config command is used in
conjunction with the boot host or boot network command. To enable the router to automatically
configure the system from the file specified by the boot host or boot network command you must enter
the service config command.
With Cisco IOS Release 12.3(2)T , 12.3(1)B, and later, you no longer have to specify the service config
command for the boot host or boot network command to be active.
If you specify both the no service config command and the boot host command, the router attempts to
find the specified host configuration file.
The service config command can also be used without the boot host or boot network command. If you
do not specify host or network configuration filenames, the router uses the default configuration files.
The default network configuration file is network-confg. The default host configuration file is
host-confg, where host is the hostname of the router. If the Cisco IOS software cannot resolve its
hostname, the default host configuration file is router-confg.
Loading a Configuration File Using rcp
The rcp software requires that a client send the remote username on each rcp request to the network
server. If the server has a directory structure (such as UNIX systems), the rcp implementation searches
for the configuration files starting in the directory associated with the remote username.
When you load a configuration file from a server using rcp, the Cisco IOS software sends the first valid
username in the following list:
Note
1.
2.
The username set by the ip rcmd remote-username command, if the command is configured.
3.
An account for the username must be defined on the destination server. If the network administrator of
the destination server did not establish an account for the username, this command will not execute
successfully.
Loading a Configuration File Using FTP
The FTP protocol requires a client to send a remote username and password on each FTP request to a
server. The username and password must be associated with an account on the FTP server. If the server
has a directory structure, the configuration file or image copied from the directory associated with the
username on the server. Refer to the documentation for your FTP server for more details.
When you load a configuration file from a server using FTP, the Cisco IOS software sends the first valid
username in the following list:
1.
2.
The username set by the ip ftp username command, if the command is configured.
3.
Anonymous.
The router sends the first valid password in the following list:
1.
2.
The password set by the ip ftp password command, if the command is configured.
FR-238
78-11740-02
3.
Examples
The following example sets the host filename to wilma-confg at address 192.168.7.19:
Router(config)# boot host tftp://192.168.7.19/usr/local/tftpdir/wilma-confg
Router(config)# service config
Related Commands
Command
Description
boot network
Specifies the remote location and filename of the network configuration file
to be used at the next system boot (startup).
service config
FR-239
boot network
To change the default name of the network configuration file from which to load configuration
commands, use the boot network global configuration command. To restore the network configuration
filename to the default, use the no form of this command.
boot network remote-url
no boot network remote-url
Syntax Description
remote-url
ftp:[[[//[username[:password]@]location]/directory]/filename]
rcp:[[[//[username@]location]/directory]/filename]
tftp:[[[//location]/directory]/filename]
Defaults
Command Modes
Global configuration
Command History
Release
Modification
10.0
Usage Guidelines
This command instructs the system to Boot using network configuration file x, where x is the filename
specified in the remote-url argument. This command specifies the remote location and filename of the
network configuration file to be used at the next system startup, as well as the protocol to be used to
obtain the file.
When booting from a network server, routers ignore routing information, static IP routes, and bridging
information. As a result, intermediate routers are responsible for handling FTP, rcp, or TFTP requests.
Before booting from a network server, verify that a server is available by using the ping command.
Use the service config command to enable the loading of the specified configuration file at reboot time.
Without this command, the router ignores the boot network command and uses the configuration
information in NVRAM. If the configuration information in NVRAM is invalid or missing, the service
config command is enabled automatically.
The network server will attempt to load two configuration files from remote hosts. The first is the
network configuration file containing commands that apply to all network servers on a network. Use the
boot network command to identify the network configuration file. The second is the host configuration
file containing commands that apply to one network server in particular. Use the boot host command to
identify the host configuration file.
FR-240
78-11740-02
Note
In releases prior to Cisco IOS Release 12.3(2)T and 12.3(1)B, the service config command is used in
conjunction with the boot host or boot network command. To enable the router to automatically
configure the system from the file specified by the boot host or boot network command you must enter
the service config command.
With Cisco IOS Release 12.3(2)T , 12.3(1)B, and later, you no longer have to specify the service config
command for the boot host or boot network command to be active.
If you specify both the no service config command and the boot host command, the router attempts to
find the specified host configuration file.
The service config command can also be used without the boot host or boot network command. If you
do not specify host or network configuration filenames, the router uses the default configuration files.
The default network configuration file is network-confg. The default host configuration file is
host-confg, where host is the hostname of the router. If the Cisco IOS software cannot resolve its
hostname, the default host configuration file is router-confg.
Loading a Configuration File Using rcp
The rcp software requires that a client send the remote username on each rcp request to the network
server. If the server has a directory structure (such as UNIX systems), the rcp implementation searches
for the configuration files starting in the directory associated with the remote username.
When you load a configuration file from a server using rcp, the Cisco IOS software sends the first valid
username in the following list:
Note
1.
2.
The username set by the ip rcmd remote-username command, if the command is configured.
3.
An account for the username must be defined on the destination server. If the network administrator of
the destination server did not establish an account for the username, this command will not execute
successfully.
Loading a Configuration File Using FTP
The FTP protocol requires a client to send a remote username and password on each FTP request to a
server. The username and password must be associated with an account on the FTP server. If the server
has a directory structure, the configuration file or image copied from the directory associated with the
username on the server. Refer to the documentation for your FTP server for more details.
When you load a configuration file from a server using FTP, the Cisco IOS software sends the first valid
username in the following list:
1.
2.
The username set by the ip ftp username command, if the command is configured.
3.
Anonymous.
The router sends the first valid password in the following list:
1.
2.
The password set by the ip ftp password command, if the command is configured.
FR-241
3.
Examples
The following example changes the network configuration filename to bridge_9.1 and uses the default
broadcast address:
Router(config)# boot network tftp:bridge_9.1
Router(config)# service config
The following example changes the network configuration filename to bridge_9.1, specifies that rcp is
to be used as the transport mechanism, and gives 172.16.1.111 as the IP address of the server on which
the network configuration file resides:
Router(config)# service config
Router(config)# boot network rcp://172.16.1.111/bridge_9.1
Related Commands
Command
Description
boot host
service config
FR-242
78-11740-02
Syntax Description
Defaults
Command Modes
Privileged EXEC
Command History
Release
Modification
12.1(5)T
Usage Guidelines
The Parser Cache feature optimizes the parsing (translation and execution) of Cisco IOS software
configuration command lines by remembering how to parse recently encountered command lines,
decreasing the time required to process large configuration files.
The clear parser cache command will free the system memory used by the Parser Cache feature and
will erase the hit/miss statistics stored for the output of the show parser statistics EXEC command. This
command is only effective when the Parser Cache feature is enabled.
Examples
Related Commands
Command
Description
parser cache
show parser statistics Displays statistics about the last configuration file parsed and the status of
the Parser Cache feature.
FR-243
configure terminal
To enter global configuration mode or to configure the system from the system memory, use the
configure terminal privileged EXEC command.
configure terminal
Syntax Description
Command Modes
Privileged EXEC
Command History
Release
Modification
10.0
Usage Guidelines
Use this command to enter global configuration mode. Note that commands in this mode are written to
the running configuration file as soon as you enter them (using the Enter key or Carriage Return).
After you enter the configure command, the system prompt changes from <router-name># to
indicating that the router is in global configuration mode. To leave global
configuration mode and return to the privileged EXEC prompt, type end or press Ctrl-Z.
<router-name>(config)#,
To view the changes to the configuration you have made, use the more system:running-config
command or show running-config command in EXEC mode.
Examples
Related Commands
Command
Description
boot config
Specifies the device and filename of the configuration file from which
the router configures itself during initialization (startup).
copy system:running-config Saves the running configuration as the startup configuration file.
nvram:startup-config
more
system:running-config
FR-244
78-11740-02
configure memory
To configure the system from the system memory, use the configure memory privileged EXEC
command.
configure memory
Syntax Description
Command Modes
Privileged EXEC
Command History
Release
Modification
10.0
Usage Guidelines
On all platforms except Class A Flash file system platforms, this command executes the commands
located in in the configuration file in NVRAM (the startup configuration file).
On Class A Flash file system platforms, if you specify the configure memory command, the router
executes the commands pointed to by the CONFIG_FILE environment variable. The CONFIG_FILE
environment variable specifies the location of the configuration file that the router uses to configure
itself during initialization. The file can be located in NVRAM or any of the Flash file systems supported
by the platform.
When the CONFIG_FILE environment variable specifies NVRAM, the router executes the NVRAM
configuration only if it is an entire configuration, not a distilled version. A distilled configuration is one
that does not contain access lists.
To view the contents of the CONFIG_FILE environment variable, use the show bootvar EXEC
command. To modify the CONFIG_FILE environment variable, use the boot config command and then
save your changes by issuing the copy system:running-config nvram:startup-config command.
After you enter the configure terminal command, the system prompt changes from <router-name># to
<router-name>(config)#, indicating that the router is in global configuration mode. To leave global
configuration mode and return to the privileged EXEC prompt, use the end command.
Examples
In the following example, a router is configured from the configuration file in the memory location
pointed to by the CONFIG_FILE environment variable:
Router# configure memory
Related Commands
Command
Description
boot config
Specifies the device and filename of the configuration file from which
the router configures itself during initialization (startup).
FR-245
Command
Description
copy system:running-config Saves the running configuration as the startup configuration file.
nvram:startup-config
show bootvar
FR-246
78-11740-02
configure overwrite-network
The configure overwrite-network has been replaced by the copy {ftp-url | rcp-url | tftp-url}
nvram:startup-config command. See the description of the copy command in the Cisco IOS File
System Commands chapter for more information.
FR-247
parser cache
To reenable the Cisco IOS software parser cache after disabling it, use the parser cache global
configuration command. To disable the parser cache, use the no form of this command.
parser cache
no parser cache
Syntax Description
Defaults
Command Modes
Global configuration
Command History
Release
Modification
12.1(5)T
Usage Guidelines
The Parser Cache feature optimizes the parsing (translation and execution) of Cisco IOS software
configuration command lines by remembering how to parse recently encountered command lines,
decreasing the time required to process large configuration files.
The parser cache is enabled by default. However, if you wish to disable the parser cache, you may do so
using the no parser cache command in global configuration mode. To reenable the parser cache after it
has been disabled, use the parser cache command.
When the no parser cache is issued, the command line appears in the running configuration file.
However, if the parser cache is reenabled, no command line appears in the running configuration file.
Examples
In the following example, the Cisco IOS software Parser Cache feature is disabled:
Router(config)# no parser cache
Related Commands
Command
Description
Clears the parse cache entries and hit/miss statistics stored for the Parser
Cache feature.
Displays statistics about the last configuration file parsed and the status of
the Parser Cache feature.
FR-248
78-11740-02
service compress-config
To compress startup configuration files, use the service compress-config global configuration
command. To disable compression, use the no form of this command.
service compress-config
no service compress-config
Syntax Description
Defaults
Disabled
Command Modes
Global configuration
Command History
Release
Modification
10.0
Usage Guidelines
After you configure the service compress-config command, the router will compress configuration files
every time you save a configuration to the startup configuration. For example, when you enter the copy
system:running-config nvram:startup-config command, the running configuration will be
compressed before storage in NVRAM.
If the file compression succeeds, the following message is displayed:
Compressing configuration from configuration-size to compressed-size
[OK]
If the boot ROMs do not recognize a compressed configuration, the following message is displayed:
Boot ROMs do not support NVRAM compression Config NOT written to NVRAM
One way to determine whether a configuration file will be compressed enough to fit into NVRAM is to
use a text editor to enter the configuration, then use the UNIX compress command to check the
compressed size. To get a closer approximation of the compression ratio, use the UNIX compress -b12
command.
Once the configuration file has been compressed, the router functions normally. At boot time, the system
recognizes that the configuration file is compressed, uncompresses it, and proceeds normally. A
partition nvram:startup-config command uncompresses the configuration before displaying it.
To disable compression of the configuration file, enter configuration mode and specify the no service
compress-config command. Then, exit global configuration mode and enter the copy
system:running-config nvram:startup-config command. The router displays an OK message if it is
FR-249
able to write the uncompressed configuration to NVRAM. Otherwise, the router displays an error
message indicating that the configuration is too large to store. If the configuration file is larger than the
physical NVRAM, the following message is displayed:
##Configuration too large to fit uncompressed in NVRAM Truncate configuration? [confirm]
When the file is truncated, commands at the end of the file are erased. Therefore, you will lose part of
your configuration. To truncate and save the configuration, type Y. To not truncate and not save the
configuration, type N.
Examples
Related Commands
Command
Description
partition nvram:startup-config
FR-250
78-11740-02
service config
To enable autoloading of configuration files from a network server, use the service config global
configuration command. To restore the default, use the no form of this command.
service config
no service config
Syntax Description
Defaults
Disabled, except on systems without NVRAM or with invalid or incomplete information in NVRAM. In
these cases, autoloading of configuration files from a network server is enabled automatically.
Command Modes
Global configuration
Command History
Release
Modification
10.0
Usage Guidelines
Usually, the service config command is used in conjunction with the boot host or boot network
command. You must enter the service config command to enable the router to automatically configure
the system from the file specified by the boot host or boot network command.
With IOS software versions 12.3(2)T , 12.3(1)B, and later, you no longer have to specify the service
config command for the boot host or boot network command to be active.
If you specify both the no service config command and the boot host command, the router attempts to
find the specified host configuration file. The service config command can also be used without the boot
host or boot network command. If you do not specify host or network configuration filenames, the
router uses the default configuration files. The default network configuration file is network-confg. The
default host configuration file is host-confg, where host is the hostname of the router. If the Cisco IOS
software cannot resolve its hostname, the default host configuration file is router-confg.
Examples
In the following example, a router is configured to autoload the default network and host configuration
files. Because no boot host or boot network commands are specified, the router uses the broadcast
address to request the files from a TFTP server.
Router(config)# service config
FR-251
The following example changes the network configuration filename to bridge_9.1, specifies that rcp is
to be used as the transport mechanism, and gives 172.16.1.111 as the IP address of the server on which
the network configuration file resides:
Router(config)# service config
Router(config)# boot network rcp://172.16.1.111/bridge_9.1
Related Commands
Command
Description
boot host
Changes the default name of the host configuration filename from which to
load configuration commands.
boot network
Changes the default name of the network configuration file from which to
load configuration commands.
FR-252
78-11740-02
show configuration
The show configuration command has been replaced by the show startup-config and
more nvram:startup-config commands. See the description of the more command in the Cisco IOS
File System Commands chapter for more information.
FR-253
show derived-config
To display the composite results of all the configuration commands that apply to an interface, including
commands that come from sources such as static templates, dynamic templates, dialer interfaces, and
authentication, authorization, and accounting (AAA) per-user attributes, use the show derived-config
command in privileged EXEC mode.
show derived-config [interface type number]
Syntax Description
Command Modes
Privileged EXEC
Command History
Release
Modification
12.1
Usage Guidelines
Configuration commands can be applied to an interface from sources such as static templates, dynamic
templates bound by resource pooling, dialer interfaces, AAA per-user attributes and the configuration of
the physical interface. The show derived-config command displays all the commands that apply to an
interface.
The output for the show derived-config command is nearly identical to that of the show running-config
command. It differs when the configuration for an interface is derived from a template, a dialer interface,
or some per-user configuration. In those cases, the commands derived from the template, dialer
interface, and so on, will be displayed for the affected interface.
If the same command is configured differently in two different sources that apply to the same interface,
the command coming from the source that has the highest precedence will appear in the display.
Examples
The following examples show sample output for the show running-config and show derived-config
commands for serial interface 0:23 and dialer interface 0. The output of the show running-config and
show derived-config commands is the same for dialer interface 0 because none of the commands that
apply to that interface are derived from any sources other than the configuration of the dialer interface.
The output for the show running-config and show derived-config commands for serial interface 0:23
differs because some of the commands that apply to serial interface 0:23 come from dialer interface 0.
Router# show running-config interface Serial0:23
Building configuration...
Current configuration :296 bytes
!
interface Serial0:23
description PRI to ADTRAN (#4444150)
ip unnumbered Loopback0
encapsulation ppp
FR-254
78-11740-02
dialer rotary-group 0
isdn switch-type primary-dms100
isdn incoming-voice modem
isdn calling-number 4444150
peer default ip address pool old_pool
end
Router# show running-config interface Dialer0
Building configuration...
Current configuration :257 bytes
!
interface Dialer0
description Dialin Users
ip unnumbered Loopback0
no ip proxy-arp
encapsulation ppp
dialer in-band
dialer idle-timeout 30
dialer-group 1
peer default ip address pool new_pool
ppp authentication pap chap callin
end
Router# show derived-config interface Serial0:23
Building configuration...
Derived configuration :332 bytes
!
interface Serial0:23
description PRI to ADTRAN (#4444150)
ip unnumbered Loopback0
encapsulation ppp
dialer rotary-group 0
isdn switch-type primary-dms100
isdn incoming-voice modem
isdn calling-number 4444150
peer default ip address pool new_pool
ppp authentication pap chap callin
end
Router# show derived-config interface Dialer0
Building configuration...
Derived configuration :257 bytes
!
interface Dialer0
description Dialin Users
ip unnumbered Loopback0
no ip proxy-arp
encapsulation ppp
dialer in-band
dialer idle-timeout 30
dialer-group 1
peer default ip address pool new_pool
ppp authentication pap chap callin
end
FR-255
Related Commands
Command
Description
show running-config
FR-256
78-11740-02
show file
The show file command has been replaced by the more command. See the description of the more
command in the Cisco IOS File System Commands chapter for more information.
FR-257
Syntax Description
Defaults
Command Modes
Privileged EXEC
Command History
Release
Modification
12.1(5)T
Usage Guidelines
The number of commands in the configuration file that was last copied into the running
configuration, and the time it took for the system to parse them (a configuration file can be loaded
into the running configuration at system startup, or by issuing commands such as the copy source
running-config command).
The status of the Parser Cache feature (enabled or disabled) and the number of command matches
(indicated by hits/misses) since the system was started or since the parser cache was cleared.
The Parser Cache feature optimizes the parsing (translation and execution) of Cisco IOS software
configuration command lines by remembering how to parse recently encountered command lines,
decreasing the time required to process large configuration files.
Examples
The following example shows sample output from the show parser statistics command:
Router# show parser statistics
Last configuration file parsed:Number of Commands:1484, Time:1272 ms
Parser cache:disabled, 0 hits, 2 misses
In this example, the Parser Cache feature is disabled, but shows the hit/miss statistics for the two
commands issued while the parser cache was last enabled.
FR-258
78-11740-02
Number of commands:
Time:
Parser cache:
hits
misses
In the following example the show parser statistics command is used to compare the parse-time of a
large configuration file with the Parser Cache feature disabled and enabled. In this example, a
configuration file with 1484 access list commands is loaded into the running configuration.
Router# configure terminal
!parser cache is disabled
Router(config)# no parser cache
!configuration file is loaded into the running configuration
Router# copy slot0:acl_list running-config
. . .
Router# show parser statistics
Last configuration file parsed:Number of Commands:1484, Time:1272 ms
Parser cache:disabled, 0 hits, 2 misses
!the parser cache is reenabled
Router(config)# parser cache
!configuration file is loaded into the running configuration
Router# copy slot0:acl_list running-config
. . .
Router# show parser statistics
Last configuration file parsed:Number of Commands:1484, Time:820 ms
Parser cache:enabled, 1460 hits, 26 misses
These results show an improvement to the load time for the same configuration file from
1272 milliseconds (ms) to 820 ms when the Parser Cache feature was enabled. As indicated in the hits
field of the show command output, 1460 commands were able to be parsed more efficiently by the parser
cache.
FR-259
Related Commands
Command
Description
Clears the parse cache entries and hit/miss statistics stored for the Parser
Cache feature.
parser cache
FR-260
78-11740-02
show running-config
To display the contents of the currently running configuration file or the configuration for a specific class
map, interface, map class, policy map, or virtual circuit (VC) class, use the show running-config
command in privileged EXEC mode.
show running-config [options]
Syntax Description
options
(Optional) One of the following options can be entered with the command:
Defaults
The show running-config command without any arguments or keywords displays the entire contents of
the running configuration file.
Command Modes
Privileged EXEC
Command History
Release
Modification
11.0
12.0
FR-261
Usage Guidelines
12.0(1)T
12.2(4)T
Examples
The following example shows the configuration for Ethernet interface 0/0. Line numbers are displayed
in the output.
Router# show running-config interface ethernet 0/0 linenum
Building configuration...
Current configuration : 104 bytes
1 : !
2 : interface Ethernet0/0
3 : ip address 10.4.2.63 255.255.255.0
4 : no ip route-cache
5 : no ip mroute-cache
6 : end
The following example shows how to set line numbers in the command output, and then use the output
modifier to start the display at line 10:
Router# show running-config linenum | begin 10
10
11
12
13
14
15
16
17
:
:
:
:
:
:
:
:
boot-start-marker
boot-end-marker
!
no logging buffered
enable password #####
!
spe 1/0 1/7
firmware location bootflash:mica-modem-pw.2.7.1.0.bin
FR-262
78-11740-02
18 : !
19 : !
20 : resource-pool disable
21 : !
22 : no aaa new-model
23 : ip subnet-zero
24 : ip domain name cisco.com
25 : ip name-server 172.16.11.48
26 : ip name-server 172.16.2.133
27 : !
28 : !
29 : isdn switch-type primary-5ess
30 : !
.
.
.
126 : end
Related Commandsd
Command
Description
boot config
Specifies the device and filename of the configuration file from which
the router configures itself during initialization (startup).
configure terminal
copy running-config
startup-config
show running-config
map-class
show startup-config
Displays the contents of NVRAM (if present and valid) or displays the
configuration file pointed to by the CONFIG_FILE environment variable.
(Command alias for the more:nvram startup-config command.)
FR-263
Syntax Description
atm
dialer
frame-relay
map-class-name
Defaults
Command Modes
Privileged EXEC
Command History
Release
Modification
12.1
12.1(2)T
Usage Guidelines
Examples
Use the show running-config map-class command to display the following information from the
running configuration file:
The following output examples assume that a user has configured 2 Frame Relay map classes named
"cir60" and "cir70," 1 ATM map class named "vc100," and 1 dialer map class named "dialer1."
All Map Classes Configured on the Router Example
Router# show running-config map-class
Building configuration...
Current configuration:
!
map-class frame-relay cir60
frame-relay bc 16000
frame-relay adaptive-shaping becn
FR-264
78-11740-02
!
map-class frame-relay cir70
no frame-relay adaptive-shaping
frame-relay priority-group 2
!
map-class atm vc100
atm aal5mux
!
map-class dialer dialer1
dialer idle-timeout 10
end
Related Commands
Command
Description
map-class atm
map-class dialer
map-class frame-relay
Specifies a map class to define QoS values for a Frame Relay VC.
more
system:running-config
FR-265
show startup-config
To display the contents of the configuration file that will be used at the next system startup, use the show
startup-config or more nvram:startup-config command in Privileged EXEC mode.
show startup-config [| {begin | exclude | include} string]
Syntax Description
| begin string
(Optional) Begin the output from the first line to match the specified string.
The pipe (|) is required.
| exclude string
(Optional) Exclude from the output any line that matches the specified
string. The pipe (|) is required.
| include string
(Optional) Displays only lines that match the specified string. The pipe (|) is
required.
Defaults
None.
Command Modes
Privileged EXEC
Command History
Release
Modification
11.0
Usage Guidelines
The show startup-config command displays the contents of NVRAM (if present and valid) or displays the
configuration file pointed to by the CONFIG_FILE environment variable.
As with all show commands, you can specify the output you are interested in more precisely using the
pipe (|) option combined with the begin, include, and exclude keywords. For more information on these
options, see the documentation of the more begin, more exclude, more include, show begin, show
exclude, and show include commands.
In Cisco IOS Release 12.0 the show startup-config command was deprecated in favor of the
more nvram:startup-config command. Although more commands are recommended (due to their
uniform structure across platforms and their expandable syntax), the show startup-config command
remains enabled to accommodate its widespread use, and to allow typing shortcuts such as show start.
Related Commands
Command
Description
boot config
Specifies the device and filename of the configuration file from which
the router configures itself during initialization (startup).
copy running-config
startup-config
FR-266
78-11740-02
Type
Platforms
Class A
Class B
Cisco 1003, Cisco 1004, Cisco 1005, Cisco 2500 series, Cisco 3600
series, and Cisco 4000 series routers, and Cisco AS5200
access servers
Class C
FR-267
Replaced Commands
Some commands found in this chapter in previous releases of this book have been replaced. Older
commands generally continue to provide the same functionality in the current release, but are no longer
documented. Support for the older version of these commands may already be removed on your system,
or may be removed in a future Cisco IOS software release.
Table 35 maps the old commands to their replacements.
Table 35
Replaced Commands
Old Command
New Command
copy verify
verify
verify bootflash:
verify flash:
copy xmodem
xmodem
copy ymodem
xmodem -y
show flh-log
verify bootflash
verify bootflash:
verify flash
verify flash:
For a description of the copy and verify commands, see the Cisco IOS File System Commands
chapter.
FR-268
78-11740-02
FR-269
copy verify
The copy verify command has been replaced by the verify command. See the description of the verify
command in the Cisco IOS File System Commands chapter for more information.
FR-270
78-11740-02
FR-271
FR-272
78-11740-02
copy xmodem:
To copy a Cisco IOS image from a local or remote computer (such as a PC, Macintosh, or UNIX
workstation) to Flash memory on a Cisco 3600 series router using the Xmodem protocol, use the copy
xmodem: EXEC command.
copy xmodem: flash-filesystem:
Syntax Description
flash-filesystem:
Command Modes
EXEC
Command History
Release
Modification
11.2 P
Usage Guidelines
This command is a form of the copy command. The copy xmodem: and copy xmodem commands are
identical. See the description of the copy command for more information.
Copying a file using FTP, rcp, or TFTP is much faster than copying a file using Xmodem. Use the
copy xmodem: command only if you do not have access to an FTP, TFTP, or rcp server.
This copy operation is performed through the console or AUX port. The AUX port, which supports
hardware flow control, is recommended.
No output is displayed on the port over which the transfer is occurring. You can use the logging buffered
command to log all router messages sent to the console port during the file transfer.
Examples
The following example initiates a file transfer from a local or remote computer to the routers internal
Flash memory using the Xmodem protocol:
copy xmodem: flash:
Related Commands
Command
Description
copy
copy ymodem:
Copies a Cisco IOS image from a local or remote computer (such as a PC,
Macintosh, or UNIX workstation) to Flash memory on a Cisco 3600 series
router using the Ymodem protocol.
FR-273
copy ymodem:
To copy a Cisco IOS image from a local or remote computer (such as a PC, Macintosh, or UNIX
workstation) to Flash memory on a Cisco 3600 series router using the Ymodem protocol, use the copy
ymodem: EXEC command.
copy ymodem: flash-filesystem:
Syntax Description
flash-filesystem:
Command Modes
EXEC
Command History
Release
Modification
11.2 P
Usage Guidelines
The copy ymodem: and copy ymodem commands are identical. See the description of the copy
command for more information.
Copying a file using FTP, rcp, or TFTP is much faster than copying a file using Ymodem. Use the
copy ymodem: command only if you do not have access to an FTP, rcp, or TFTP server.
This copy operation is performed through the console or AUX port. The AUX port, which supports
hardware flow control, is recommended.
No output is displayed on the port over which the transfer is occurring. You can use the logging buffered
command to log all router messages sent to the console port during the file transfer.
Examples
The following example initiates a file transfer from a local or remote computer to the routers internal
Flash memory using the Ymodem protocol:
copy ymodem: flash:
Related Commands
Command
Description
copy xmodem:
Copies a Cisco IOS image from a local or remote computer (such as a PC,
Macintosh, or UNIX workstation) to Flash memory on a Cisco 3600 series
router using the Xmodem protocol.
FR-274
78-11740-02
erase flash:
The erase flash: and erase flash commands are identical. See the description of the erase command in
the Cisco IOS File System Commands chapter for more information.
FR-275
microcode (7000/7500)
To specify the location of the microcode that you want to download from Flash memory into the writable
control store (WCS) on Cisco 7000 series (including RSP based routers) or Cisco 7500 series routers,
use the microcode global configuration command. To load the microcode bundled with the system
image, use the no form of this command.
microcode interface-type {flash-filesystem:filename [slot] | rom | system [slot]]}
no microcode interface-type {flash-filesystem:filename [slot] | rom | system [slot]}
Syntax Description
interface-type
One of the following interface processor names: aip, cip, eip, feip, fip, fsip, hip,
mip, sip, sp, ssp, trip, vip, or vip2.
flash-filesystem:
Flash file system, followed by a colon. Valid file systems are bootflash, slot0,
and slot1.
Slave devices such as slaveslot0 are invalid. The slaves file system is not
available during microcode reloads.
filename
slot
rom
If ROM is specified, the router loads from the onboard ROM microcode.
system
If the system keyword is specified, the router loads the microcode from the
microcode bundled into the system image you are running for that interface type.
Defaults
The default is to load from the microcode bundled in the system image.
Command Modes
Global configuration
Command History
Release
Modification
10.3
Usage Guidelines
If you do not use the microcode reload command after using the microcode command, the microcode
reload command will be written to the configuration file automatically.
When using Dual RSPs for simple hardware backup, ensure that the master and slave RSP card contain
the same microcode image in the same location when the router is to load the interface processor
microcode from a Flash file system. Thus, if the slave RSP becomes the master, it will be able to find
the microcode image and download it to the interface processor.
Examples
In the following example, all FIP cards will be loaded with the microcode found in Flash memory
file fip.v141-7 when the system is booted, when a card is inserted or removed, or when the microcode
reload global configuration command is issued. The configuration is then written to the startup
configuration file.
FR-276
78-11740-02
Related Commands
Command
Description
more flh:logfile
Displays the system console output generated during the Flash load helper
operation.
FR-277
microcode (7200)
To configure a default override for the microcode that is downloaded to the hardware on a Cisco 7200
series router, use the microcode global configuration command. To revert to the default microcode for
the current running version of the Cisco IOS software, use the no form of this command.
microcode {ecpa | pcpa} location
no microcode {ecpa | pcpa}
Syntax Description
ecpa
pcpa
location
Defaults
If the default or no form of the command is specified, the driver uses the default microcode for the
current running version of the Cisco IOS software.
Command Modes
Global configuration
Command History
Release
Modification
11.3(3)T
Usage Guidelines
If there are any default overrides when the configuration is written, then the microcode reload command
will be written to the configuration automatically. This action enables the configured microcode to be
downloaded at system startup.
The CPA microcode image is preloaded on Flash memory cards for Cisco 7200-series routers for
Cisco IOS Release 11.3(3)T and later releases. You may be required to copy a new image to Flash
memory when a new microcode image becomes available.
For more information on the CPA configuration and maintenance, refer to the Configuring Cisco
Mainframe Channel Connection Adapters chapter in the Release 12.2 Cisco IOS Bridging and IBM
Networking Configuration Guide.
Examples
The following example instructs the Cisco IOS software to load the microcode from an individual
microcode image that is stored as a file on the Flash card inserted in Flash card slot 0:
microcode ecpa slot0:xcpa26-1
FR-278
78-11740-02
Related Commands
Command
Description
microcode reload (7200) Resets and reloads the specified hardware in a Cisco 7200 series router.
show microcode
FR-279
microcode (12000)
To load a Cisco IOS software image on a line card from Flash memory or the GRP card on a
Cisco 12000 series Gigabit Switch Router (GSR), use the microcode global configuration command. To
load the microcode bundled with the GRP system image, use the no form of this command.
microcode {oc12-atm | oc12-pos | oc3-pos4} {flash file-id [slot] | system [slot]}
no microcode {oc12-atm | oc12-pos | oc3-pos4} [flash file-id [slot] | system [slot]]
Syntax Description
file-id
slot
(Optional) Slot number of the line card that you want to copy the
software image to. Slot numbers range from 0 to 11 for the
Cisco 12012 router and 0 to 7 for the Cisco 12008 router. If you do
not specify a slot number, the Cisco IOS software image is
downloaded on all line cards.
system
Loads the image from the software image on the GRP card.
Defaults
The default is to load the image from the GRP card (system).
Command Modes
Global configuration
Command History
Release
Modification
11.2 GS
Usage Guidelines
In addition to the Cisco IOS image that resides on the GRP card, each line card on a Cisco 12000 series
has a Cisco IOS image. When the router is reloaded, the specified image is loaded onto the GRP card
and then automatically downloaded to all the line cards.
Normally, you want the same Cisco IOS image on the GRP card and all line cards. However, if you want
to upgrade a line card with a new version of microcode for testing or to fix a defect, you might need to
load a Cisco IOS image that is different from the one on the line card. Additionally, you might need to
load a new image on the line card to work around a problem that is affecting only one of the line cards.
FR-280
78-11740-02
To load a Cisco IOS image on a line card, first use the copy tftp command to download the Cisco IOS
image to a slot on one of the PCMCIA Flash memory cards. Then use the microcode command to
download the image to the line card, followed by the microcode reload command to start the image.
Immediately after you enter the microcode reload command and press Return, the system reloads all
microcode. Global configuration mode remains enabled. After the reloading is complete, enter the exit
command to return to the EXEC system prompt.
To verify that the correct image is running on the line card, use the execute-on slot slot show version
command.
For additional information on GSR configuration, refer to the documentation specific to your Cisco IOS
software release.
Examples
In the following example, the Cisco IOS software image in slot 0 is downloaded to the line card in
slot 10. This software image is used when the system is booted, a line card is inserted or removed, or the
microcode reload global configuration command is issued.
microcode oc3-POS-4 flash slot0:fip.v141-7 10
microcode reload 10
In this example, the user would issue the execute-on slot 10 show version command to verify that the
correct version is loaded.
Related Commands
Command
Description
FR-281
Syntax Description
Defaults
Command Modes
Global configuration
Command History
Release
Modification
10.3
Usage Guidelines
Note
Examples
This command reloads the microcode without rebooting the router. Immediately after you enter the
microcode reload command and press Return, the system reloads all microcode. Global configuration
mode remains enabled.
If you modify the system configuration to load a microcode image, the microcode reload command
will be written to the configuration file automatically following the use of a microcode command.
This action enables the configured microcode to be downloaded at system startup.
In the following example, all controllers are reset, and the microcode specified in the current
configuration is loaded:
microcode reload
Related Commands
Command
Description
microcode (7000/7500)
FR-282
78-11740-02
Syntax Description
all
ecpa
Resets and reloads only those slots that contain hardware type ecpa.
pcpa
Resets and reloads only those slots that contain hardware type pcpa.
slot slot#
(Optional) Resets and reloads only the slot specified, and only if it
contains the hardware specified.
Defaults
Command Modes
Privileged EXEC
Command History
Release
Modification
11.3(3)T
Usage Guidelines
Hardware types that do not support downloadable microcode are unaffected by the microcode reload
all command.
You will be prompted for confirmation before the microcode reload command is executed.
Examples
The following example reloads the ESCON CPA microcode in slot 5 with the currently configured
microcode:
microcode reload ecpa slot 5
Related Commands
Command
Description
microcode (7200)
show microcode
Displays the microcode bundled into a Cisco 7000 series with RSP7000,
Cisco 7200 series, or Cisco 7500 series router.
FR-283
Syntax Description
slot-number
Command Modes
Global configuration
Command History
Release
Modification
11.2 GS
Usage Guidelines
(Optional) Slot number of the line card that you want to reload the
Cisco IOS software image on. Slot numbers range from 0 to 11 for the
Cisco 12012 and from 0 to 7 for the Cisco 12008 router. If you do not
specify a slot number, the Cisco IOS software image is reloaded on all
line cards.
In addition to the Cisco IOS image that resides on the GRP card, each line card on Cisco 12000 series
routers has a Cisco IOS image. When the router is reloaded, the specified Cisco IOS image is loaded
onto the GRP card and automatically downloaded to all the line cards.
Normally, you want the same Cisco IOS image on the GRP card and all line cards. However, if you want
to upgrade a line card with a new version of microcode for testing or to fix a defect, you might need to
load a different Cisco IOS image. Additionally, you might need to load a new image on the line card to
work around a problem affecting only one of the line cards.
To load a Cisco IOS image on a line card, first use the copy tftp command to download the Cisco IOS
image to a slot on one of the PCMCIA Flash memory cards. Then use the microcode command to
download the image to the line card, followed by the microcode reload command to start the image. To
verify that the correct image is running on the line card, use the execute-on slot slot show version
command.
For additional information on GSR configuration, refer to the Observing System Startup and
Performing a Basic Configuration chapter in the Cisco 12000 series installation and configuration
guides.
The microcode reload (12000) command allows you to issue another command immediately.
Note
Issuing a microcode reload command on any of the line cards in a Cisco 12000 GSR immediately
returns the console command prompt. This allows you to issue a subsequent command immediately
to the reloading line card. However, any commands entered at this time will not execute, and often
no indication will be given that such a command failed to run. Verify that the microcode has reloaded
before issuing new commands.
FR-284
78-11740-02
Examples
In the following example, the Cisco IOS software is reloaded on the line card in slot 10:
microcode reload 10
Related Commands
Command
Description
microcode (12000)
Loads a Cisco IOS software image on a line card from Flash memory
or the GRP card on a Cisco 12000 series GSR.
FR-285
more flh:logfile
To view the system console output generated during the Flash load helper operation, use the
more flh:logfile privileged EXEC command.
more flh:logfile
Syntax Description
Command Modes
Privileged EXEC
Command History
Release
Modification
11.3 AA
Usage Guidelines
If you are a remote Telnet user performing the Flash upgrade without a console connection, this
command allows you to retrieve console output when your Telnet connection has terminated due to the
switch to the ROM image. The output indicates what happened during the download, and is particularly
useful if the download fails.
This command is a form of the more command. See the more command for more information.
Examples
FR-286
78-11740-02
Related Commands
Command
Description
more
Displays a file.
FR-287
show flh-log
The show flh-log command has been replaced by the more flh:logfile command. See the description of
the more flh:logfile command in this chapter for more information.
FR-288
78-11740-02
show microcode
To display microcode image information available on line cards, use the show microcode EXEC
command.
show microcode
Syntax Description
Command Modes
EXEC
Command History
Release
Modification
10.0
Examples
Microcode
Version
--------2.3
1.1
1.2
1.4
1.1
1.1
1.1
Target Hardware
Version
--------------11.x
1.x
1.x
2.x
1.x
1.x
1.x
Description
----------SP version 2.3
EIP version 1.1
TRIP version 1.2
FIP version 1.4
HIP version 1.1
SIP version 1.1
FSIP version 1.1
In the following example for the Cisco 7200 series router, the output from the show microcode
command lists the hardware types that support microcode download. For each type, the default
microcode image name is displayed. If there is a configured default override, that name also is displayed.
router# show microcode
Microcode images for downloadable hardware
HW Type
Microcode image names
-----------------------------------------ecpa
default
slot0:xcpa26-0
configured slot0:xcpa26-2
pcpa
default
slot0:xcpa26-4
FR-289
Related Commands
Command
Description
microcode (7000/7500)
microcode (7200)
FR-290
78-11740-02
xmodem
To copy a Cisco IOS image to a router using the ROM monitor and the Xmodem or Ymodem protocol,
use the xmodem ROM monitor command.
xmodem [-c] [-y] [-e] [-f] [-r] [-x] [-s data-rate] [filename]
Syntax Description
-c
-y
-e
(Optional) Erases the first partition in Flash memory before starting the download.
This option is only valid for the Cisco 1600 series.
-f
(Optional) Erases all of Flash memory before starting the download. This option is
only valid for the Cisco 1600 series.
-r
-x
-s data-rate
(Optional) Sets the console ports data rate during file transfer. Values are 1200,
2400, 4800, 9600, 19200, 38400, and 115200 bps. The default rate is specified in
the configuration register. This option is only valid for the Cisco 1600 series.
filename
Defaults
Xmodem protocol with 8-bit CRC, file downloaded into Flash memory and executed on completion.
Command Modes
ROM monitor
Command History
Release
Modification
11.2 P
Usage Guidelines
The Cisco 3600 series routers does not support XBOOT functionality. If your Cisco IOS image is erased
or damaged, you cannot load a new image over the network.
Use the xmodem ROM monitor command to download a new system image to your router from a local
personal computer (such as a PC, Mac, or UNIX workstation), or a remote computer over a modem
connection, to the routers console port. The computer must have a terminal emulation application that
supports these protocols.
Cisco 3600 Series Routers
Your router must have enough DRAM to hold the file being transferred, even if you are copying to Flash
memory. The image is copied to the first file in internal Flash memory. Any existing files in Flash
memory are erased. There is no support for partitions or copying as a second file.
FR-291
If you include the -r option, your router must have enough DRAM to hold the file being transferred. To
run from Flash, an image must be positioned as the first file in Flash memory. If you are copying a new
image to boot from Flash, erase all existing files first.
Caution
Note
Examples
A modem connection from the telephone network to your console port introduces security issues that
you should consider before enabling the connection. For example, remote users can dial in to your
modem and access the routers configuration settings.
If the file to be downloaded is not a valid router image, the copy operation is automatically
terminated.
The following example uses the xmodem -c filename ROM monitor command to copy the file named
new-ios-image from a remote or local computer:
rommon > xmodem -c new-ios-image
Do not start the sending program yet...
File size
Checksum
File name
1738244 bytes (0x1a8604)
0xdd25 george-admin/c3600-i-mz
WARNING: All existing data in bootflash will be lost!
Invoke this application only for disaster recovery.
Do you wish to continue? y/n [n]: yes
Ready to receive file new-ios-image ...
Related Commands
Command
Description
copy xmodem:
Copies a Cisco IOS image from a local or remote computer (such as a PC,
Macintosh, or UNIX workstation) to Flash memory on a Cisco 3600 series
router using the Xmodem protocol.
copy ymodem:
Copies a Cisco IOS image from a local or remote computer (such as a PC,
Macintosh, or UNIX workstation) to Flash memory on a Cisco 3600 series
router using the Ymodem protocol.
FR-292
78-11740-02
Type
Platforms
Class A
Class B
Class C
FR-293
memory scan
To enable the Memory Scan feature on a Cisco 7500 series router, use the memory scan command. To
restore the router configuration to the default, use the no form of this command.
memory scan
no memory scan
Syntax Description
Defaults
Command Modes
Global configuration
Command History
Release
Modification
12.0(4)XE
12.0(7)T
Usage Guidelines
The Memory Scan feature adds a low-priority background process that searches all installed dynamic
random-access memory (DRAM) for possible parity errors. If errors are found in memory areas that are
not in use, this feature attempts to scrub (remove) the errors. The time to complete one memory scan and
scrub cycle can range from 10 minutes to several hours, depending on the amount of installed memory.
The impact of the Memory Scan feature on the central processing unit (CPU) is minimal. To view the
status of the memory scan feature on your router, use the show memory scan command in EXEC mode.
Examples
The following example enables the Memory Scan feature on a Cisco 7500 series router:
Router(config)# memory scan
Related Commands
Command
Description
Displays the number and type of parity errors on your system (Cisco 7500
series only).
FR-294
78-11740-02
memory-size iomem
To reallocate the percentage of DRAM to use for I/O memory and processor memory on Cisco 3600
series routers, use the memory-size iomem global configuration command. To revert to the default
memory allocation, use the no form of this command.
memory-size iomem i/o-memory-percentage
no memory-size iomem i/o-memory-percentage
Syntax Description
i/o-memory-percentage
Defaults
The default memory allocation is 25 percent I/O memory and 75 percent processor memory.
Note
If the smartinit process has been enabled, the default memory allocation of 25% to I/O does not
apply. Instead, smartinit examines the network modules and then calculates the I/O memory
required.
Command Modes
Global configuration
Command History
Release
Modification
11.2 P
Usage Guidelines
When you specify the percentage of I/O memory in the command line, processor memory automatically
acquires the remaining percentage of DRAM memory.
Examples
The following example allocates 40 percent of the DRAM memory to I/O memory and the remaining
60 percent to processor memory:
Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# memory-size iomem 40
Router(config)# exit
Router# copy system:running-config nvram:startup-config
Building configuration...
[OK]
Router# reload
rommon 1 > boot
program load complete, entry point: 0x80008000, size: 0x32ea24
FR-295
FR-296
78-11740-02
partition
To separate Flash memory into partitions on Class B file system platforms, use the partition global
configuration command. To undo partitioning and to restore Flash memory to one partition, use the no
form of this command.
Cisco 1600 Series and Cisco 3600 Series Routers
Syntax Description
Defaults
flash-filesystem:
number-of-partitions
partition-size
partitions
size1
size2
Command Modes
Global configuration
Command History
Release
Modification
10.3
FR-297
Usage Guidelines
For the Cisco 1600 series and Cisco 3600 series routers, to undo partitioning, use the partition
flash-filesystem:1 or no partition flash-filesystem: command. For other Class B platforms, use either the
partition flash 1 or no partition flash command. If there are files in a partition other than the first, you
must use the erase flash-filesystem:partition-number command to erase the partition before reverting to
a single partition.
When creating two partitions, you must not truncate a file or cause a file to spill over into the second
partition.
Examples
The following example divides the Flash memory card in slot 0 into two partitions, each 8 MB in size
on a Cisco 3600 series router:
Router(config)# partition slot0: 2 8 8
The following example creates four partitions of equal size in the card on a Cisco 1600 series router:
Router(config)# partition flash: 4
FR-298
78-11740-02
show flash-filesystem:
Syntax Description
flash-filesystem:
all
chips
filesys
(Optional) Displays the Device Info Block, the Status Info, and the
Usage Info.
partition number
detailed
err
summary
FR-299
Command Modes
EXEC
Command History
Release
Modification
11.3 AA
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
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:
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 37 describes the
significant fields shown in the display.
The following is sample output from the show flash: command.
Router# show flash:
-#- ED --type-- --crc--- -seek-- nlen -length- -----date/time------ name
1
.. unknown 317FBA1B 4A0694
24 4720148 Aug 29 1997 17:49:36
hampton/nitro/c7200-j-mz
FR-300
78-11740-02
2
3
4
5
6
7
..
.D
.D
..
.D
..
unknown
unknown
unknown
unknown
unknown
unknown
9237F3FF
71AB01F1
96DACD45
96DACD45
96DACD45
96DACD45
92C574
10C94E0
10C97E0
10C9AE0
10C9DE0
10CA0E0
11
10
8
3
8
8
4767328
7982828
639
639
639
639
Oct
Oct
Oct
Oct
Oct
Oct
01
01
02
02
02
02
1997
1997
1997
1997
1997
1997
18:42:53
18:48:14
12:09:17
12:09:32
12:37:01
12:37:13
c7200-js-mz
rsp-jsv-mz
the_time
the_time
the_time
the_time
Table 37
Field
Description
ED
type
crc
seek
nlen
length
date/time
name
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):
Config Status Reg (4002):
Card Status
Reg (4100):
Write Protect Reg (4104):
Voltage Cntrl Reg (410C):
Rdy/Busy Mode Reg (4140):
2
0
1
4
0
2
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
FR-301
8 :
16 :
24 :
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
B0B0
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 -------Device Number = 0
DEVICE INFO BLOCK:
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
Num Spare Sectors
= 0
Spares:
STATUS INFO:
Writable
NO File Open for Write
Complete Stats
No Unrecovered Errors
No Squeeze in progress
USAGE INFO:
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
FR-302
78-11740-02
The following example shows detailed information about the second partition in internal Flash memory:
RouterB# show flash: partition 2
System flash directory, partition 2:
File Length
Name/status
1
1711088 dirt/images/c3600-i-mz
[1711152 bytes used, 15066064 available, 16777216 total]
16384K bytes of processor board System flash (Read/Write)
Field
Description
addr
available
Bank
Bank number.
Bank-Size
bytes used
ccksum
Computed checksum.
Chip
Chip number.
Code
Code number.
Copy-Mode
fcksum
File
Free
Length
Name
FR-303
Table 38
Field
Description
Name/status
Partition
Size
State
total
Used
The following is sample output from the show flash: all command:
RouterB> show flash: all
Partition
Size
Used
1
16384K
4040K
Free
12343K
Bank-Size
4096K
State
Read/Write
Copy Mode
Direct
Bank
1
1
1
1
2
2
2
2
3
3
3
3
4
4
4
4
Code
01D5
01D5
01D5
01D5
01D5
01D5
01D5
01D5
01D5
01D5
01D5
01D5
01D5
01D5
01D5
01D5
Size
1024KB
1024KB
1024KB
1024KB
1024KB
1024KB
1024KB
1024KB
1024KB
1024KB
1024KB
1024KB
1024KB
1024KB
1024KB
1024KB
Name
AMD
AMD
AMD
AMD
AMD
AMD
AMD
AMD
AMD
AMD
AMD
AMD
AMD
AMD
AMD
AMD
29F080
29F080
29F080
29F080
29F080
29F080
29F080
29F080
29F080
29F080
29F080
29F080
29F080
29F080
29F080
29F080
FR-304
78-11740-02
The following is sample output from the show flash: all command on a router with Flash memory
partitioned:
Router# show flash: all
System flash partition information:
Partition
Size
Used
Free
1
4096K
3459K
637K
2
4096K
3224K
872K
Bank-Size
4096K
4096K
State
Read Only
Read/Write
Copy-Mode
RXBOOT-FLH
Direct
Bank
2
2
2
2
Code
89A2
89A2
89A2
89A2
Size
1024KB
1024KB
1024KB
1024KB
Name
INTEL
INTEL
INTEL
INTEL
28F008SA
28F008SA
28F008SA
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)
Chip
1
2
3
4
1
2
3
4
1
2
3
4
1
2
3
4
Bank
1
1
1
1
2
2
2
2
3
3
3
3
4
4
4
4
Code
01D5
01D5
01D5
01D5
01D5
01D5
01D5
01D5
01D5
01D5
01D5
01D5
01D5
01D5
01D5
01D5
Size
1024KB
1024KB
1024KB
1024KB
1024KB
1024KB
1024KB
1024KB
1024KB
1024KB
1024KB
1024KB
1024KB
1024KB
1024KB
1024KB
Name
AMD
AMD
AMD
AMD
AMD
AMD
AMD
AMD
AMD
AMD
AMD
AMD
AMD
AMD
AMD
AMD
29F080
29F080
29F080
29F080
29F080
29F080
29F080
29F080
29F080
29F080
29F080
29F080
29F080
29F080
29F080
29F080
The following is sample output from the show flash: detailed command:
FR-305
The following is sample output from the show flash: err command:
RouterB> show flash: err
System flash directory:
File Length
Name/status
1
4137888 c3640-c2is-mz.Feb24
[4137952 bytes used, 12639264 available, 16777216 total]
16384K bytes of processor board System flash (Read/Write)
Chip
1
2
3
4
1
2
3
4
1
2
3
4
1
2
3
4
Bank
1
1
1
1
2
2
2
2
3
3
3
3
4
4
4
4
Code
01D5
01D5
01D5
01D5
01D5
01D5
01D5
01D5
01D5
01D5
01D5
01D5
01D5
01D5
01D5
01D5
Size
1024KB
1024KB
1024KB
1024KB
1024KB
1024KB
1024KB
1024KB
1024KB
1024KB
1024KB
1024KB
1024KB
1024KB
1024KB
1024KB
Name
AMD
AMD
AMD
AMD
AMD
AMD
AMD
AMD
AMD
AMD
AMD
AMD
AMD
AMD
AMD
AMD
erase
29F080
29F080
29F080
29F080
29F080
29F080
29F080
29F080
29F080
29F080
29F080
29F080
29F080
29F080
29F080
29F080
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
write
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
See Table 38 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
1
4096K
2048K
2048K
2
4096K
2048K
2048K
Related Commands
Bank-Size
2048K
2048K
State
Read Only
Read/Write
Copy-Mode
RXBOOT-FLH
Direct
Command
Description
more
Displays the contents of any file in the Cisco IOS File System.
FR-306
78-11740-02
Syntax Description
Defaults
Command Modes
EXEC
Command History
Release
Modification
12.0(4)XE
12.0(7)T
Examples
If errors are detected in the system, the show memory scan command generates an error report. In the
following example, memory scan detected a parity error:
Router# show memory scan
Memory scan is on.
Total Parity Errors 1.
AddressBlockPtrBlckSizeDispositRegion Timestamp
6115ABCD60D5D0909517A4ScrubedLocal 16:57:09 UTC Thu
Mar 18
Field
Description
Address
BlockPtr
BlckSize
FR-307
Table 39
Field
Description
Disposit
Region
Timestamp
IBSSimage BSS
IDataimagedata
ITextimagetext
localheap
FR-308
78-11740-02
write memory
The write memory command has been replaced by the copy system:running-config nvram:
startup-config command. See the description of the copy command in this Cisco IOS File System
Commands chapter for more information.
FR-309
write network
The write network command is replaced by the copy system:running-config destination-url. See the
description of the copy command in this Cisco IOS File System Commands chapter for more
information.
FR-310
78-11740-02
Booting Commands
This chapter provides detailed descriptions of the commands used to modify the rebooting procedures
of the router.
For configuration information and examples, refer to the Rebooting chapter in the Release 12.2
Cisco IOS Configuration Fundamentals Configuration Guide.
Type
Platforms
Class A
Class B
Class C
FR-311
Booting Commands
boot
boot
To boot the router manually, use the boot ROM monitor command. The syntax of this command varies
according to the platform and ROM monitor version.
boot
boot file-url
boot filename [tftp-ip-address]
boot flash [flash-fs:][partition-number:][filename]
Cisco 7000 Series, 7200 Series, 7500 Series Routers
boot flash-fs:[filename]
Cisco 1600 and Cisco 3600 Series Routers
boot [flash-fs:][partition-number:][filename]
Syntax Description
file-url
filename
tftp-ip-address
flash
Boots the router from Flash memory. Note that this keyword is
required in some boot images.
FR-312
78-11740-02
Booting Commands
boot
flash-fs:
partition-number:
Defaults
(Optional) Specifies the partition number of the file system the file
should be loaded from. This argument is not available on all
platforms.
For most platforms, if you enter the boot command and press Return, the router boots from ROM by
default. However, for some platforms, such as the Cisco 3600 series routers, if you enter the boot
command and press Return, the router boots the first image in Flash memory. Refer to the documentation
for your platform for information about the default image.
If the partition-number is not specified, the first partition is used.
If the filename is not specified, the first file in the partition or file system is used.
For other defaults, see the Syntax Description section.
Command Modes
ROM monitor
Command History
Release
Modification
10.3
Usage Guidelines
To determine which form of this command to use, refer to the documentation for your platform or use
the CLI help (?) feature.
Use this command only when your router cannot find the boot configuration information needed in
NVRAM. To enter ROM monitor mode, use one of the following methods:
Enter the reload EXEC command, then press the Break key during the first 60 seconds of startup.
Set the configuration register bits 0 to 3 to zero (for example, set the configuration register to 0x0)
and enter the reload command.
The ROM Monitor prompt is either > or, for newer platforms, rommon x>. Enter only lowercase
commands.
These commands work only if there is a valid image to boot. Also, from the ROM monitor prompt,
issuing a prior reset command is necessary for the boot to be consistently successful.
Refer to your hardware documentation for information on correct jumper settings for your platform.
FR-313
Booting Commands
boot
Note
Examples
For some platforms the flash keyword is now required. If your attempts to use the boot command are
failing using the older boot flash:x:[filename] syntax, try using the boot flash flash:x:[filename]
syntax.
In the following example, a router boots the file named routertest from a network server with the IP
address 172.16.15.112 using the file-url syntax:
> boot tftp://172.16.15.112/routertest
F3
(ROM Monitor copyrights)
The following example shows the boot flash command without the filename argument. The first valid
file in Flash memory is loaded.
> boot flash
F3: 1858656+45204+166896 at 0x1000
Booting gs7-k from flash memory RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR [OK - 1903912/13765276 bytes]
F3: 1858676+45204+166896 at 0x1000
(ROM Monitor copyrights)
The following example boots from Flash memory using the file named gs7-k:
> boot flash gs7-k
F3: 1858656+45204+166896 at 0x1000
Booting gs7-k from flash memory RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
RRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRRR
RRRRRRRRRRRRRR [OK - 1903912/13765276 bytes]
F3: 1858676+45204+166896 at 0x1000
(ROM Monitor copyrights)
In the following example, the boot flash flash: command boots the relocatable image file named
igs-bpx-l from partition 2 in Flash memory:
> boot flash flash:2:igs-bpx-l
F3: 3562264+98228+303632 at 0x30000B4
(ROM Monitor copyrights)
In the following command, the Cisco 7000 family router accepts the flash keyword for compatibility but
ignores it, and boots from slot 0:
> boot flash slot0:gs7-k-mz.103-9
F3: 8468+3980384+165008 at 0x1000
FR-314
78-11740-02
Booting Commands
boot
In the following example, the command did not function because it must be entered in lowercase:
rommon 10 > BOOT
command BOOT not found
The following example boots the first file in the first partition of internal Flash memory of a Cisco 3600
series router:
> boot flash:
The following example boots the first image file in the first partition of the Flash memory card in slot 0
of a Cisco 3600 series router:
> boot slot0:
The following example shows the ROM monitor booting the first file in the first Flash memory partition
on a Cisco 1600 series router:
> boot flash:
Related Commands
Command
Description
continue
Returns to EXEC mode from ROM monitor mode by completing the boot
process.
FR-315
Booting Commands
boot bootldr
boot bootldr
To specify the location of the boot image that ROM uses for booting, use the boot bootldr global
configuration command. To remove this boot image specification, use the no form of this command.
boot bootldr file-url
no boot bootldr
Syntax Description
file-url
Defaults
Refer to your platform documentation for the location of the default boot image.
Command Modes
Global configuration
Command History
Release
Modification
11.0
Usage Guidelines
Note
The boot bootldr command sets the BOOTLDR variable in the current running configuration. You must
specify both the Flash file system and the filename.
When you use this global configuration command, you affect only the running configuration. You
must save the variable setting to your startup configuration to place the information under ROM
monitor control and to have the variable function as expected. Use the copy system:running-config
nvram:startup-config command to save the variable from your running configuration to your
startup configuration.
The no form of the command sets the BOOTLDR variable to a null string. On the Cisco 7000 family
routers, a null string causes the first image file in boot flash memory to be used as the boot image that
ROM uses for booting.
Use the show boot command to display the current value for the BOOTLDR variable.
Examples
In the following example, the internal Flash memory contains the boot image:
boot bootldr bootflash:boot-image
The following example specifies that the Flash memory card inserted in slot 0 contains the boot image:
boot bootldr slot0:boot-image
FR-316
78-11740-02
Booting Commands
boot bootldr
Related Commands
Command
Description
FR-317
Booting Commands
boot bootstrap
boot bootstrap
To configure the filename that is used to boot a secondary bootstrap image, use the boot bootstrap
global configuration command. To disable booting from a secondary bootstrap image, use the no form
of this command.
boot bootstrap file-url
no boot bootstrap file-url
boot bootstrap flash [filename]
no boot bootstrap flash [filename]
boot bootstrap [tftp] filename [ip-address]
no boot bootstrap [tftp] filename [ip-address]
Syntax Description
file-url
flash
filename
(Optional with flash) Name of the system image to boot from a network server or
from Flash memory. If you omit the filename when booting from Flash memory,
the router uses the first system image stored in Flash memory.
tftp
(Optional) Boots the router from a system image stored on a TFTP server.
ip-address
(Optional) IP address of the TFTP server on which the system image resides. If
omitted, this value defaults to the IP broadcast address of 255.255.255.255.
Defaults
No secondary bootstrap
Command Modes
Global configuration
Command History
Release
Modification
10.0
Usage Guidelines
The boot bootstrap command causes the router to load a secondary bootstrap image over the network.
The secondary bootstrap image then loads the specified system image file. See the appropriate hardware
installation guide for details on the configuration register and secondary bootstrap filename.
Use this command when you have attempted to load a system image but have run out of memory even
after compressing the system image. Secondary bootstrap allows you to load a larger system image
through a smaller secondary image.
FR-318
78-11740-02
Booting Commands
boot bootstrap
Examples
In the following example, the system image file named sysimage-2 will be loaded by using a secondary
bootstrap image:
boot bootstrap bootflash:sysimage-2
FR-319
Booting Commands
boot system
boot system
To specify the system image that the router loads at startup, use one of the following boot system global
configuration commands. To remove the startup system image specification, use the no form of the
command.
boot system file-url
no boot system file-url
boot system flash [flash-fs:][partition-number:][filename]
no boot system flash [flash-fs:][partition-number:][filename]
boot system mop filename [mac-address] [interface]
no boot system mop filename [mac-address] [interface]
boot system rom
no boot system rom
boot system {rcp | tftp | ftp} filename [ip-address]
no boot system {rcp | tftp | ftp} filename [ip-address]
no boot system
Syntax Descriptionn
file-url
flash
On all platforms except the Cisco 1600 series, Cisco 3600 series, and
Cisco 7000 family routers, this keyword boots the router from internal
Flash memory. If you omit all arguments that follow this keyword, the
system searches internal Flash for the first bootable image.
On the Cisco 1600 series, Cisco 3600 series, and Cisco 7000 family
routers, this keyword boots the router from a Flash device, as specified
by the device: argument. On the Cisco 1600 series and Cisco 3600 series
routers, if you omit all optional arguments, the router searches internal
Flash memory for the first bootable image. On the Cisco 7000 family
routers, when you omit all arguments that follow this keyword, the
system searches the PCMCIA slot 0 for the first bootable image.
FR-320
78-11740-02
Booting Commands
boot system
flash-fs:
partition-number:
filename
(Optional when used with the boot system flash command) Name of the
system image to load at startup. It is case sensitive. If you do not specify
a filename, the router loads the first valid file in the specified Flash file
system, the specified partition of Flash memory, or the default Flash file
system if you also omit the flash-fs: argument.
mop
Boots the router from a system image stored on a Digital MOP server.
Do not use this keyword with the Cisco 3600 series or Cisco 7000 family
routers.
mac-address
interface
(Optional) Interface the router uses to send out MOP requests to the
MOP server. The interface options are async, dialer, ethernet, serial,
and tunnel. If you do not specify the interface argument, the router
sends a request out on all interfaces that have MOP enabled. The
interface that receives the first response is the interface the router uses
to load the software.
rom
Boots the router from ROM. Do not use this keyword with the
Cisco 3600 series or the Cisco 7000 family routers.
rcp
Boots the router from a system image stored on a network server using
rcp.
tftp
ftp
ip-address
FR-321
Booting Commands
boot system
Defaults
If you configure the router to boot from a network server but do not specify a system image file with the
boot system command, the router uses the configuration register settings to determine the default system
image filename. The router forms the default boot filename by starting with the word cisco and then
appending the octal equivalent of the boot field number in the configuration register, followed by a
hyphen (-) and the processor type name (cisconn-cpu). Refer to the appropriate hardware installation
guide for details on the configuration register and default filename. See also the config-register or
confreg command. For additional information about defaults, see the preceding Syntax Description
section.
Command Modes
Global configuration
Command History
Release
Modification
10.0
Usage Guidelines
For this command to work, the config-register command must be set properly.
Enter several boot system commands to provide a fail-safe method for booting your router. The router
stores and executes the boot system commands in the order in which you enter them in the configuration
file. If you enter multiple boot commands of the same typefor example, if you enter two commands
that instruct the router to boot from different network serversthen the router tries them in the order in
which they appear in the configuration file. If a boot system command entry in the list specifies an
invalid device, the router omits that entry. Use the boot system rom command to specify use of the ROM
system image as a backup to other boot commands in the configuration.
For some platforms, the boot image must be loaded before the system image is loaded. However, on
many platforms, the boot image is loaded only if the router is booting from a network server or if the
Flash file system is not specified. If the file system is specified, the router will boot faster because it need
not load the boot image first.
This section contains the following usage guideline sections:
Cisco 1600 Series, Cisco 3600 Series, and Cisco 7000 Family Notes
To remove a single entry from the bootable image list, use the no form of the command with an
argument. For example, to remove the entry that specifies a bootable image on a Flash memory card
inserted in the second slot, use the no boot system flash slot1:[filename] command. All other entries in
the list remain.
To eliminate all entries in the bootable image list, use the no boot system command. At this point, you
can redefine the list of bootable images using the previous boot system commands. Remember to save
your changes to your startup configuration by issuing the copy system:running-config
nvram:startup-config command.
FR-322
78-11740-02
Booting Commands
boot system
Each time you write a new software image to Flash memory, you must delete the existing filename in the
configuration file with the no boot system flash filename command. Then add a new line in the
configuration file with the boot system flash filename command.
Note
If you want to rearrange the order of the entries in the configuration file, you must first issue the no
boot system command and then redefine the list.
Boot Compressed Images
You can boot the router from a compressed image on a network server. When a network server boots
software, both the image being booted and the running image must fit into memory. Use compressed
images to ensure that enough memory is available to boot the router. You can compress a software image
on any UNIX platform using the compress command. Refer to your UNIX platforms documentation for
the exact usage of the compress command. (You can also uncompress data with the UNIX uncompress
command.)
Understand the rcp Protocol
The rcp protocol requires a client to send the remote username in an rcp request to a server. When the
router executes the boot system rcp command, the Cisco IOS software sends the host name as both the
remote and local usernames by default. For the rcp protocol to execute properly, an account must be
defined on the network server for the remote username configured on the router.
If the server has a directory structure, the rcp software searches for the system image to boot from the
remote server relative to the directory of the remote username.
By default, the router software sends host name as the remote username. You can override the default
remote username by using the ip rcmd remote-username command. For example, if the system image
resides in the home directory of a user on the server, you can specify that users name as the remote
username.
Understand TFTP
You need a TFTP server running in order to retrieve the router image from the host.
Understand FTP
You need to an FTP server running in order to fetch the router image from the host. You also need an
account on the server or anonymous file access to the server.
Stop Booting and Enter ROM Monitor Mode
During the first 60 seconds of startup, you can force the router to stop booting by pressing the Break key.
The router will enter ROM Monitor mode, where you can change the configuration register value or boot
the router manually.
Cisco 1600 Series, Cisco 3600 Series, and Cisco 7000 Family Notes
For the Cisco 3600 series and Cisco 7000 family, the boot system command modifies the BOOT variable
in the running configuration. The BOOT variable specifies a list of bootable images on various devices.
Note
When you use the boot system global configuration command on the Cisco 1600 series, Cisco 3600
series, and Cisco 7000 family, you affect only the running configuration. You must save the BOOT
variable settings to your startup configuration to place the information under ROM monitor control
FR-323
Booting Commands
boot system
and to have the variable function as expected. Use the copy system:running-config
nvram:startup-config EXEC command to save the variable from your running configuration to your
startup configuration.
To view the contents of the BOOT variable, use the show bootenv EXEC command.
Examples
The following example illustrates a list specifying two possible internetwork locations for a system
image, with the ROM software being used as a backup:
boot system tftp://192.168.7.24/cs3-rx.90-1
boot system tftp://192.168.7.19/cs3-rx.83-2
boot system rom
The following example boots the system boot relocatable image file named igs-bpx-l from partition 2 of
the Flash device:
boot system flash:2:igs-bpx-l
The following example instructs the router to boot from an image located on the Flash memory card
inserted in slot 0 of the Cisco 7000 RSP7000 card, Cisco 7200 NPE card, or Cisco 7500 series RSP card:
boot system slot0:new-config
The following example specifies the file named new-ios-image as the system image for a Cisco 3600
series router to load at startup. This file is located in the fourth partition of the Flash memory card in
slot 0.
Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# boot system slot0:4:dirt/images/new-ios-image
This example boots from the image file named c1600-y-l in partition 2 of Flash memory of a Cisco 1600
series router:
Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)# boot system flash:2:c1600-y-l
Related Commands
Command
Description
config-register
copy
show bootvar
FR-324
78-11740-02
Booting Commands
config-register
config-register
To change the configuration register settings, use the config-register global configuration command.
config-register value
Syntax Description
value
Defaults
Refer to the documentation for your platform for the default configuration register value. For many
newer platforms, the default is 0x2102, which causes the router to boot from Flash memory and the
Break key to be ignored.
Command Modes
Global configuration
Command History
Release
Modification
10.0
Usage Guidelines
This command applies only to platforms that use a software configuration register.
The lowest four bits of the configuration register (bits 3, 2, 1, and 0) form the boot field. The boot field
determines if the router boots manually, from ROM, or from Flash or the network.
To change the boot field value and leave all other bits set to their default values, follow these guidelines:
If you set the configuration register boot field value to 0x0, you must boot the operating system
manually with the boot command.
If you set the configuration register boot field value to 0x1, the router boots using the default ROM
software.
If you set the configuration register boot field to any value from 0x2 to 0xF, the router uses the boot
field value to form a default boot filename for booting from a network server.
For more information about the configuration register bit settings and default filenames, refer to the
appropriate router hardware installation guide.
Examples
In the following example, the configuration register is set to boot the system image from Flash memory:
config-register 0x2102
Related Commands
Command
Description
boot system
confreg
FR-325
Booting Commands
config-register
Command
Description
Lists the value of the boot field (bits 0 to 3) in the configuration register.
show version
Displays the configuration of the system hardware, the software version, the
names and sources of configuration files, and the boot images.
FR-326
78-11740-02
Booting Commands
confreg
confreg
To change the configuration register settings while in ROM monitor mode, use the confreg ROM
monitor command.
confreg [value]
Syntax Description
value
Defaults
Refer to your platform documentation for the default configuration register value.
Command Modes
ROM monitor
Command History
Release
Modification
10.0
Usage Guidelines
Not all versions in the ROM monitor support this command. Refer to your platform documentation for
more information on ROM monitor mode.
If you use this command without specifying the configuration register value, the router prompts for each
bit of the configuration register.
The lowest four bits of the configuration register (bits 3, 2, 1, and 0) form the boot field. The boot field
determines if the router boots manually, from ROM, or from Flash or the network.
To change the boot field value and leave all other bits set to their default values, follow these guidelines:
If you set the configuration register boot field value to 0x0, you must boot the operating system
manually with the boot command.
If you set the configuration register boot field value to 0x1, the router boots using the default ROM
software.
If you set the configuration register boot field to any value from 0x2 to 0xF, the router uses the boot
field value to form a default boot filename for booting from a network server.
For more information about the configuration register bit settings and default filenames, refer to the
appropriate router hardware installation guide.
Examples
In the following example, the configuration register is set to boot the system image from Flash memory:
confreg 0x210F
In the following example, no configuration value is entered, so the system prompts for each bit in the
register:
rommon 7 > confreg
FR-327
Booting Commands
confreg
Configuration Summary
enabled are:
console baud: 9600
boot: the ROM Monitor
do you wish to change the configuration? y/n [n]:
enable "diagnostic mode"? y/n [n]: y
enable "use net in IP bcast address"? y/n [n]:
enable "load rom after netboot fails"? y/n [n]:
enable "use all zero broadcast"? y/n [n]:
enable "break/abort has effect"? y/n [n]:
enable "ignore system config info"? y/n [n]:
change console baud rate? y/n [n]: y
enter rate: 0 = 9600, 1 = 4800, 2 = 1200, 3 = 2400
change the boot characteristics? y/n [n]: y
enter to boot:
0 = ROM Monitor
1 = the boot helper image
2-15 = boot system
[0]: 0
[0]:
Configuration Summary
enabled are:
diagnostic mode
console baud: 9600
boot: the ROM Monitor
do you wish to change the configuration? y/n
[n]:
You must reset or power cycle for new config to take effect.
rommon 8>
FR-328
78-11740-02
Booting Commands
continue
continue
To return to EXEC mode from ROM monitor mode, use the continue ROM monitor command.
continue
Syntax Description
Defaults
Command Modes
ROM monitor
Command History
Release
Modification
11.0
Usage Guidelines
Caution
Examples
Use this command to return to EXEC mode from ROM monitor mode, to use the system image instead
of reloading. On older platforms, the angle bracket (>) indicates that the router is in ROM monitor mode.
On newer platforms, rommon number> is the default ROM monitor prompt. Typically, the router is in
ROM monitor mode when you manually load a system image or perform diagnostic tests. Otherwise, the
router will most likely never be in this mode.
While in ROM monitor mode, the Cisco IOS system software is suspended until you issue either a
reset or the continue command.
In the following example, the continue command switches the router from ROM monitor to EXEC
mode:
> continue
Router#
Related Commands
Command
Description
boot
FR-329
Booting Commands
reload
reload
To reload the operating system, use the reload EXEC command.
reload [text | in [hh:]mm [text] | at hh:mm [month day | day month] [text] | cancel]
Syntax Description
text
in [hh:]mm
(Optional) Schedule a reload of the software to take effect in the specified minutes or
hours and minutes. The reload must take place within approximately 24 days.
at hh:mm
(Optional) Schedule a reload of the software to take place at the specified time (using
a 24-hour clock). If you specify the month and day, the reload is scheduled to take
place at the specified time and date. If you do not specify the month and day, the reload
takes place at the specified time on the current day (if the specified time is later than
the current time), or on the next day (if the specified time is earlier than the current
time). Specifying 00:00 schedules the reload for midnight. The reload must take place
within approximately 24 days.
month
day
cancel
Command Modes
EXEC
Command History
Release
Modification
10.0
Usage Guidelines
The reload command halts the system. If the system is set to restart on error, it reboots itself. Use the
reload command after configuration information is entered into a file and saved to the startup
configuration.
You cannot reload from a virtual terminal if the system is not set up for automatic booting. This prevents
the system from dropping to the ROM monitor and thereby taking the system out of the remote users
control.
If you modify your configuration file, the system prompts you to save the configuration. During a save
operation, the system asks you if you want to proceed with the save if the CONFIG_FILE variable points
to a startup configuration file that no longer exists. If you say yes in this situation, the system goes to
setup mode upon reload.
When you schedule a reload to occur at a later time, it must take place within approximately 24 days.
The at keyword can be used only if the system clock has be set on the router (either through NTP, the
hardware calendar, or manually). The time is relative to the configured time zone on the router. To
schedule reloads across several routers to occur simultaneously, the time on each router must be
synchronized with NTP.
To display information about a scheduled reload, use the show reload EXEC command.
FR-330
78-11740-02
Booting Commands
reload
Examples
The following example reloads the software on the router at 1:00 p.m. today:
Router# reload at 13:00
Router# Reload scheduled for 13:00:00 PDT Fri Apr 21 1996 (in 1 hour and 2 minutes)
Proceed with reload? [confirm]
Router#
The following example reloads the software on the router on April 20 at 2:00 a.m.:
Router# reload at 02:00 apr 20
Router# Reload scheduled for 02:00:00 PDT Sat Apr 20 1996 (in 38 hours and 9 minutes)
Proceed with reload? [confirm]
Router#
Related Commands
Command
Description
copy system:running-config
nvram:startup-config
show reload
FR-331
Booting Commands
show boot
show boot
The show boot command has been replaced by the show bootvar command. See the description of the
show bootvar command in this chapter for more information.
FR-332
78-11740-02
Booting Commands
show bootvar
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 EXEC command.
show bootvar
Syntax Description
Command Modes
EXEC
Command History
Release
Modification
11.3 AA
Usage Guidelines
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
In the sample output, the BOOT variable contains a null string. That is, a list of bootable images is not
specified.
FR-333
Booting Commands
show bootvar
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:
Router# show bootvar
BOOT variable =
CONFIG_FILE variable =
Current CONFIG_FILE variable =
BOOTLDR variable does not exist
Configuration register is 0x0
current slave is in slot 7
BOOT variable =
CONFIG_FILE variable =
BOOTLDR variable does not exist
Configuration register is 0x0
Router#
Related Commands
Command
Description
boot bootstrap
boot config
Specifies the device and filename of the configuration file from which the
router configures itself during initialization (startup).
boot system
show version
Displays the configuration of the system hardware, the software version, the
names and sources of configuration files, and the boot images.
FR-334
78-11740-02
Booting Commands
show reload
show reload
To display the reload status on the router, use the show reload EXEC command.
show reload
Syntax Description
Command Modes
EXEC
Command History
Release
Modification
11.2
Usage Guidelines
You can use the show reload command to display a pending software reload. To cancel the reload, use
the reload cancel privileged EXEC command.
Examples
The following sample output from the show reload command shows that a reload is schedule for
12:00 a.m. (midnight) on Saturday, April 20:
Router# show reload
Reload scheduled for 00:00:00 PDT Sat April 20 (in 12 hours and 12 minutes)
Router#
Related Commands
Command
Description
reload
FR-335
Booting Commands
show version
show version
To display information about the currently loaded software version along with hardware and device
information, use the show version command in EXEC mode.
show version
Syntax Description
Defaults
Command Modes
User EXEC
Privileged EXEC
Command History
Usage Guidelines
Release
Modification
9.0
12.3(4)T
12.2(25)S
This command displays information about the Cisco IOS software version currently running on a routing
device, the ROM Monitor and Bootflash software versions, and information about the hardware
configuration, including the amount of system memory. Because this command displays both software and
hardware information, the output of this command is the same as the output of the show hardware command.
(The show hardware command is a command alias for the show version command.)
Specifically, the show version command provides the following information:
Software information
Main Cisco IOS image version
Main Cisco IOS image capabilities (feature set)
Location and name of bootfile in ROM
Bootflash image version (depending on platform)
Device-specific information
Device name
System uptime
System reload reason
Config-register setting
Config-register settings for after the next reload (depending on platform)
FR-336
78-11740-02
Booting Commands
show version
Hardware information
Platform type
Processor type
Processor hardware revision
Amount of main (processor) memory installed
Amount I/O memory installed
Amount of Flash memory installed on different types (depending on platform)
Processor board ID
<software-type>
<router-name> uptime is <w> weeks, <d> days, <h> hours, <m> minutes
System returned to ROM by reload at <time> <day> <date>
System image file is "<filesystem-location>/<software-image-name>"
Last reload reason: <reload-reason>
Cisco <platform-processor-type> processor (revision <processor-revision-id>) with
<free-DRAM-memory>K/<packet-memory>K bytes of memory.
Processor board ID <ID-number>
<CPU-type> CPU at <clock-speed>Mhz, Implementation <number>, Rev <Revision-number>,
<kilobytes-Processor-Cache-Memory>KB <cache-Level> Cache
See the Examples section for descriptions of the fields in this output.
Examples
The following is sample output from the show version command issued on a Cisco 3660 running Cisco
IOS Release 12.3(4)T:
Router# show version
Cisco IOS Software, 3600 Software (C3660-I-M), Version 12.3(4)T
TAC Support: http://www.cisco.com/tac
Copyright (c) 1986-2003 by Cisco Systems, Inc.
Compiled Thu 18-Sep-03 15:37 by ccai
ROM: System Bootstrap, Version 12.0(6r)T, RELEASE SOFTWARE (fc1)
ROM:
C3660-1 uptime is 1 week, 3 days, 6 hours, 41 minutes
System returned to ROM by power-on
System image file is "slot0:tftpboot/c3660-i-mz.123-4.T"
Cisco 3660 (R527x) processor (revision 1.0) with 57344K/8192K bytes of memory.
Processor board ID JAB055180FF
R527x CPU at 225Mhz, Implementation 40, Rev 10.0, 2048KB L2 Cache
FR-337
Booting Commands
show version
The following is sample output from the show version command issued on a Cisco 7200 router running
Cisco IOS Release 12.4(4)T. This output shows the total bandwidth capacity and the bandwith capacity
that is configured on the Cisco 7200. Displaying bandwidth capacity is available in Cisco IOS Release
12.2 and later releases.
Router# show version
Cisco IOS Software, 7200 Software (C7200-JS-M), Version 12.4(4)T, RELEASE SOFTW)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2005 by Cisco Systems, Inc.
Compiled Thu 27-Oct-05 05:58 by ccai
ROM: System Bootstrap, Version 12.1(20000710:044039) [nlaw-121E_npeb 117], DEVEE
BOOTLDR: 7200 Software (C7200-KBOOT-M), Version 12.3(16), RELEASE SOFTWARE (fc4)
router uptime is 5 days, 18 hours, 2 minutes
System returned to ROM by reload at 02:45:12 UTC Tue Feb 14 2006
System image file is "disk0:c7200-js-mz.124-4.T"
Last reload reason: Reload Command
4 Ethernet interfaces
2 FastEthernet interfaces
2 ATM interfaces
125K bytes of NVRAM.
62976K bytes of ATA PCMCIA card at slot 0 (Sector size 512 bytes).
125952K bytes of ATA PCMCIA card at slot 1 (Sector size 512 bytes).
8192K bytes of Flash internal SIMM (Sector size 256K).
Configuration register is 0x2002
Router#
FR-338
78-11740-02
Booting Commands
show version
Field
Description
Example:
Cisco IOS Software, 7200
Software (C7200-G4JS-M),
Version 12.3(4)T
BOOTFLASH:
Example:
C3660-1 uptime is 1 week, 3
days, 6 hours, 41 minutes
FR-339
Booting Commands
show version
Table 41
Field
Description
Shows the last recorded reason for a system reload, and time of last
reload.
Example:
System returned to ROM by
reload at 20:56:53 UTC Tue
Nov 4 2003
Last reload reason:
<reload-reason>
Example:
Last reload reason: Reload
command
Last reset from
<reset-reason>
Example:
Last reset from power-on
Example:
System image file is
"slot0:tftpboot/c3660-i-mz.1
23-3.9.T2"
FR-340
78-11740-02
Booting Commands
show version
Table 41
Field
Description
Cisco <platform>
(<processor-type>) processor
(revision
<processor-revision-id>)
with
<free-DRAM-memory>K/<packetmemory>K bytes of memory.
Two values, separated by a slash, are given for DRAM: The first
value tells you how DRAM is available for system processing, and
the second value tells you how much DRAM is being used for
Packet memory.
The first value, Main Processor memory, is either:
Note
The 4000, 4500, 4700, and 7500 series routers have separate
DRAM and Packet memory, so you only need to look at the first
number to determine total DRAM. In the example to the left for the
Cisco RSP4, the first value shows that the router has 65536K
(65,536 kilobytes, or 64 megabytes) of DRAM. The second value,
8192K, is the Packet memory.
Combined DRAM and Packet Memory
The 2500, 2600, 3600, and 7200 series routers require a minimum
amount of I/O memory to support certain interface processors.
The 1600, 2500, 2600, 3600, and 7200 series routers use a fraction
of DRAM as Packet memory, so you need to add both numbers to
find out the real amount of DRAM. In the example to the left for the
Cisco 3660, the router has 57,344 kilobytes (KB) of free DRAM
and 8,192 KB dedicated to Packet memory. Adding the two
numbers together gives you 57,344K + 8,192K = 65,536K, or 64
megabytes (MB) of DRAM.
FR-341
Booting Commands
show version
Table 41
Field
Description
For more details on memory requirements, see the document How
to Choose a Cisco IOS Software Release on Cisco.com.
Configuration register is
<value>
Example:
Configuration register is
0x2142 (will be 0x2102 at
next reload)
Related Commands
Command
Description
show inventory
FR-342
78-11740-02
FR-343
async-bootp
To configure extended BOOTP requests for asynchronous interfaces as defined in RFC 1084, use the
async-bootp global configuration command. To restore the default, use the no form of this command.
async-bootp tag [:hostname] data
no async-bootp
Syntax Description
tag
:hostname
(Optional) This entry applies only to the host specified. The :hostname argument
accepts both an IP address and a logical host name.
data
Table 42
Keyword
Description
bootfile
Specifies use of a server boot file from which to download the boot
program. Use the optional :hostname argument and the data argument to
specify the filename.
subnet-mask mask
time-offset offset
Signed 32-bit integer specifying the time offset of the local subnetwork
in seconds from Coordinated Universal Time (UTC).
gateway address
time-server address
IEN116-server
address
nbns-server address
DNS-server address
log-server address
quote-server address
lpr-server address
impress-server
address
FR-344
78-11740-02
Table 42
Keyword
Description
rlp-server address
hostname name
The name of the client, which may or may not be domain qualified,
depending upon the site.
bootfile-size value
Defaults
If no extended BOOTP commands are entered, the Cisco IOS software generates a gateway and subnet
mask appropriate for the local network.
Command Modes
Global configuration
Command History
Release
Modification
10.0
Usage Guidelines
Use the show async-bootp EXEC command to list the configured parameters. Use the no async-bootp
command to clear the list.
Examples
The following example illustrates how to specify different boot files: one for a PC, and one for a
Macintosh. With this configuration, a BOOTP request from the host on 172.30.1.1 results in a reply
listing the boot filename as pcboot. A BOOTP request from the host named mac results in a reply listing
the boot filename as macboot.
async-bootp bootfile :172.30.1.1 pcboot
async-bootp bootfile :mac macboot
The following example specifies a negative time offset of the local subnetwork of 3600 seconds:
async-bootp time-offset -3600
Related Commands
Command
Description
Displays the extended BOOTP request parameters that have been configured
for asynchronous interfaces.
FR-345
ip ftp passive
To configure the router to use only passive File Transfer Protocol (FTP) connections, use the ip ftp
passive global configuration command. To allow all types of FTP connections, use the no form of this
command.
ip ftp passive
no ip ftp passive
Syntax Description
Defaults
Command Modes
Global configuration
Command History
Release
Modification
10.3
Examples
The following example configures the router to use only passive FTP connections:
ip ftp passive
Related Commands
Command
Description
ip ftp password
ip ftp source-interface
ip ftp username
FR-346
78-11740-02
ip ftp password
To specify the password to be used for File Transfer Protocol (FTP) connections, use the ip ftp password
global configuration command. To return the password to its default, use the no form of this command.
ip ftp password [type] password
no ip ftp password
Syntax Description
type
password
Defaults
The router forms a password [email protected]. The variable username is the username
associated with the current session, routername is the configured host name, and domain is the domain
of the router.
Command Modes
Global configuration
Command History
Release
Modification
10.3
Examples
The following example configures the router to use the username red and the password blue for FTP
connections:
ip ftp username red
ip ftp password blue
Related Commands
Command
Description
ip ftp password
ip ftp source-interface
ip ftp username
FR-347
ip ftp source-interface
To specify the source IP address for File Transfer Protocol (FTP) connections, use the ip ftp
source-interface global configuration command. To use the address of the interface where the
connection is made, use the no form of this command.
ip ftp source-interface interface
no ip ftp source-interface
Syntax Description
interface
Defaults
The FTP source address is the IP address of the interface the FTP packets use to leave the router.
Command Modes
Global configuration
Command History
Release
Modification
10.3
The interface type and number to use to obtain the source address for
FTP connections.
Usage Guidelines
Use this command to set the same source address for all FTP connections.
Examples
The following example configures the router to use the IP address associated with the Ethernet 0
interface as the source address on all FTP packets, regardless of which interface is actually used to send
the packet:
ip ftp source-interface ethernet 0
Related Commands
Command
Description
ip ftp passive
ip ftp password
ip ftp username
FR-348
78-11740-02
ip ftp username
To configure the username for File Transfer Protocol (FTP) connections, use the ip ftp username global
configuration command. To configure the router to attempt anonymous FTP, use the no form of this
command.
ip ftp username username
no ip ftp username
Syntax Description
username
Defaults
Command Modes
Global configuration
Command History
Release
Modification
10.3
Usage Guidelines
The remote username must be associated with an account on the destination server.
Examples
In the following example, the router is configured to use the username red and the password blue
for FTP connections:
Router(config)# ip ftp username red
Router(config)# ip ftp password blue
Related Commands
Command
Description
ip ftp passive
ip ftp password
ip ftp source-interface
FR-349
ip rarp-server
To enable the router to act as a Reverse Address Resolution Protocol (RARP) server, use the
ip rarp-server command in interface configuration mode. To restore the interface to the default of no
RARP server support, use the no form of this command.
ip rarp-server ip-address
no ip rarp-server ip-address
Syntax Description
ip-address
Defaults
Disabled
Command Modes
Interface configuration
Command History
Release
Modification
10.0
Usage Guidelines
IP address that is to be provided in the source protocol address field of the RARP
response packet. Normally, this is set to whatever address you configure as the
primary address for the interface.
This feature makes diskless booting of clients possible between network subnets where the client and
server are on separate subnets.
RARP server support is configurable on a per-interface basis, so that the router does not interfere with
RARP traffic on subnets that need no RARP assistance.
The Cisco IOS software answers incoming RARP requests only if both of the following two conditions
are met:
The ip rarp-server command has been configured for the interface on which the request was
received.
A static entry is found in the IP ARP table that maps the MAC address contained in the RARP
request to an IP address.
Use the show ip arp EXEC command to display the contents of the IP ARP cache.
Sun Microsystems, Inc. makes use of RARP and UDP-based network services to facilitate
network-based booting of SunOS on its workstations. By bridging RARP packets and using both the ip
helper-address interface configuration command and the ip forward-protocol global configuration
command, the Cisco IOS software should be able to perform the necessary packet switching to enable
booting of Sun workstations across subnets. Unfortunately, some Sun workstations assume that the
sender of the RARP response, in this case the router, is the host that the client can contact to TFTP load
the bootstrap image. This causes the workstations to fail to boot.
By using the ip rarp-server command, the Cisco IOS software can be configured to answer these RARP
requests, and the client machine should be able to reach its server by having its TFTP requests forwarded
through the router that acts as the RARP server.
FR-350
78-11740-02
In the case of RARP responses to Sun workstations attempting to diskless boot, the IP address specified
in the ip rarp-server interface configuration command should be the IP address of the TFTP server. In
addition to configuring RARP service, the Cisco IOS software must be configured to forward
UDP-based Sun portmapper requests to completely support diskless booting of Sun workstations. This
can be accomplished using configuration commands of the following form:
ip forward-protocol udp 111
interface interface name
ip helper-address target-address
Examples
The following partial example configures a router to act as a RARP server. The router is configured to
use the primary address of the specified interface in its RARP responses.
arp 172.30.2.5 0800.2002.ff5b arpa
interface ethernet 0
ip address 172.30.3.100 255.255.255.0
ip rarp-server 172.30.3.100
In the following example, a router is configured to act as a RARP server, with TFTP and portmapper
requests forwarded to the Sun server:
! Allow the router to forward broadcast portmapper requests
ip forward-protocol udp 111
! Provide the router with the IP address of the diskless sun
arp 172.30.2.5 0800.2002.ff5b arpa
interface ethernet 0
! Configure the router to act as a RARP server, using the Sun Server's IP
! address in the RARP response packet.
ip rarp-server 172.30.3.100
! Portmapper broadcasts from this interface are sent to the Sun Server.
ip helper-address 172.30.3.100
Related Commands
Command
Description
ip forward-protocol
ip helper-address
FR-351
ip rcmd domain-lookup
To reenable the basic DNS security check for rcp and rsh, use the ip rcmd domain-lookup global
configuration command. To disable the basic DNS security check for rcp and rsh, use the no form of this
command.
ip rcmd domain-lookup
no ip rcmd domain-lookup
Syntax Description
Defaults
Enabled
Command Modes
Global configuration
Command History
Release
Modification
10.3
Usage Guidelines
The abbreviation RCMD (remote command) is used to indicate both rsh and rcp.
DNS lookup for RCMD is enabled by default (provided general DNS services are enabled on the system
using the ip domain-lookup command).
The no ip rcmd domain-lookup command is used to disable the DNS lookup for RCMD. The ip rcmd
domain-lookup command is used to reenable the DNS lookup for RCMD.
DNS lookup for RCMD is performed as a basic security check. This check is performed using a host
authentication process. When enabled, the system records the address of the requesting client. That
address is mapped to a host name using DNS. Then a DNS request is made for the IP address for that
host name. The IP address received is then checked against the original requesting address. If the address
does not match with any of the addresses received from DNS, the RCMD request will not be serviced.
This reverse lookup is intended to help protect against spoofing. However, please note that the process
only confirms that the IP address is a valid routable address; it is still possible for a hacker to spoof
the valid IP address of a known host.
The DNS lookup is done after the TCP handshake but before the router (which is acting as a rsh/rcp
server) sends any data to the remote client.
The no ip rcmd domain-lookup will turn off DNS lookups for rsh and rcp only. The no ip
domain-lookup command takes precedence over the ip rcmd domain-lookup command. This means
that if the no ip domain-lookup command is in the current configuration, DNS will be bypassed for rcp
and rsh even if the ip rcmd domain-lookup command is enabled.
FR-352
78-11740-02
Examples
In the following example, the DNS security check is disabled for RCMD (rsh/rcp):
Router(config)# no ip rcmd domain-lookup
Related Commands
Command
Description
ip domain-lookup
FR-353
ip rcmd rcp-enable
To configure the Cisco IOS software to allow remote users to copy files to and from the router using
remote copy (rcp), use the ip rcmd rcp-enable global configuration command. To disable rcp on the
device, use the no form of this command.
ip rcmd rcp-enable
no ip rcmd rcp-enable
Syntax Description
Defaults
Command Modes
Global configuration
Command History
Release
Modification
10.3
Usage Guidelines
To allow a remote user to execute rcp commands on the router, you must also create an entry for the
remote user in the local authentication database using the ip rcmd remote-host command.
The no ip rcmd rcp-enable command does not prohibit a local user from using rcp to copy system
images and configuration files to and from the router.
To protect against unauthorized users copying the system image or configuration files, the router is not
enabled for rcp by default.
Examples
In the following example, the rcp service is enabled on the system, the IP address assigned to the
Loopback0 interface is used as the source address for outbound rcp and rsh packets, and access is granted
to the user netadmin3on the remote host 172.16.101.101:
Router(config)# ip rcmd rcp-enable
Router(config)# ip rcmd source-interface Loopback0
Router(config)# ip rcmd remote-host router1 172.16.101.101 netadmin3
Related Commands
Command
Description
ip rcmd remote-host
Creates an entry for the remote user in a local authentication database so that
remote users can execute commands on the router using rsh or rcp.
FR-354
78-11740-02
ip rcmd remote-host
To create an entry for the remote user in a local authentication database so that remote users can execute
commands on the router using rsh or rcp, use the ip rcmd remote-host command in global configuration
mode. To remove an entry for a remote user from the local authentication database, use the no form of
this command.
ip rcmd remote-host local-username {ip-address | host-name} remote-username [enable [level]]
no ip rcmd remote-host local-username {ip-address | host-name} remote-username [enable
[level]]
Syntax Description
local-username
Name of the user on the local router. You can specify the router name
as the username. This name needs to be communicated to the network
administrator or to the user on the remote system. To be allowed to
remotely execute commands on the router, the remote user must
specify this value correctly.
ip-address
IP address of the remote host from which the local router will accept
remotely executed commands. Either the IP address or the host name
is required.
host-name
Name of the remote host from which the local router will accept
remotely executed commands. Either the host name or the IP address
is required.
remote-username
Name of the user on the remote host from which the router will accept
remotely executed commands.
enable [level]
Defaults
Command Modes
Global configuration
Command History
Release
Modification
10.3
Usage Guidelines
A TCP connection to a router is established using an IP address. Using the host name is valid only when
you are initiating an rcp or rsh command from a local router. The host name is converted to an IP address
using DNS or host-name aliasing.
FR-355
To allow a remote user to execute rcp or rsh commands on a local router, you must create an entry for
the remote user in the local authentication database. You must also enable the router to act as an rsh or
rcp server.
To enable the router to act as an rsh server, issue the ip rcmd rsh-enable command. To enable the router
to act as an rcp server, issue the ip rcmd rcp-enable command.The router cannot act as a server for
either of these protocols unless you explicitly enable the capacity.
A local authentication database, which is similar to a UNIX .rhosts file, is used to enforce security on
the router through access control. Each entry that you configure in the authentication database identifies
the local user, the remote host, and the remote user. To permit a remote user of rsh to execute commands
in privileged EXEC mode or to permit a remote user of rcp to copy files to the router, specify the enable
keyword and level. For information on the enable level, refer to the privilege level global configuration
command in the Release 12.2 Cisco IOS Security Command Reference.
An entry that you configure in the authentication database differs from an entry in a UNIX .rhosts file
in the following aspect. Because the .rhosts file on a UNIX system resides in the home directory of a
local user account, an entry in a UNIX .rhosts file need not include the local username; the local
username is determined from the user account. To provide equivalent support on a router, specify the
local username along with the remote host and remote username in each authentication database entry
that you configure.
For a remote user to be able to execute commands on the router in its capacity as a server, the local
username, host address or name, and remote username sent with the remote client request must match
values configured in an entry in the local authentication file.
A remote client host should be registered with DNS. The Cisco IOS software uses DNS to authenticate
the remote hosts name and address. Because DNS can return several valid IP addresses for a host name,
the Cisco IOS software checks the address of the requesting client against all of the IP addresses for the
named host returned by DNS. If the address sent by the requester is considered invalid, that is, it does
not match any address listed with DNS for the host name, then the software will reject the
remote-command execution request.
Note that if no DNS servers are configured for the router, then that device cannot authenticate the host
in this manner. In this case, the Cisco IOS software sends a broadcast request to attempt to gain access
to DNS services on another server. If DNS services are not available, you must use the no ip
domain-lookup command to disable the attempt to gain access to a DNS server by sending a broadcast
request.
If DNS services are not available and, therefore, you bypass the DNS security check, the software will
accept the request to remotely execute a command only if all three values sent with the request match
exactly the values configured for an entry in the local authentication file.
Examples
The following example allows the remote user named netadmin3 on a remote host with the IP address
172.16.101.101 to execute commands on router1 using the rsh or rcp protocol. User netadmin3 is
allowed to execute commands in privileged EXEC mode.
ip rcmd remote-host router1 172.16.101.101 netadmin3 enable
Related Commands
Command
Description
ip rcmd rcp-enable
Configures the Cisco IOS software to allow remote users to copy files to and
from the router.
FR-356
78-11740-02
Command
Description
ip rcmd rsh-enable
ip domain-lookup
FR-357
ip rcmd remote-username
To configure the remote username to be used when requesting a remote copy using rcp, use the ip rcmd
remote-username global configuration command. To remove from the configuration the remote
username, use the no form of this command.
ip rcmd remote-username username
no ip rcmd remote-username username
Syntax Description
username
Defaults
If you do not issue this command, the Cisco IOS software sends the remote username associated with
the current tty process, if that name is valid, for rcp copy commands. For example, if the user is
connected to the router through Telnet and the user was authenticated through the username command,
then the software sends that username as the remote username.
Note
Name of the remote user on the server. This name is used for rcp copy
requests. All files and images to be copied are searched for or written
relative to the directory of the remote users account, if the server has
a directory structure, for example, as do UNIX systems.
The remote username must be associated with an account on the destination server.
If the username for the current tty process is not valid, the Cisco IOS software sends the host name as
the remote username. For rcp boot commands, the Cisco IOS software sends the access server host name
by default.
Note
For Cisco, tty lines are commonly used for access services. The concept of tty originated with UNIX.
For UNIX systems, each physical device is represented in the file system. Terminals are called tty
devices (tty stands for teletype, the original UNIX terminal).
Command Modes
Global configuration
Command History
Release
Modification
10.3
Usage Guidelines
The rcp protocol requires that a client send the remote username on an rcp request to the server. Use this
command to specify the remote username to be sent to the server for an rcp copy request. If the server
has a directory structure, as do UNIX systems, all files and images to be copied are searched for or
written relative to the directory of the remote users account.
FR-358
78-11740-02
Note
Examples
Cisco IOS Release 10.3 added the ip keyword to rcmd commands. If you are upgrading from Release
10.2 to Release 10.3 or a later release, this keyword is automatically added to any rcmd commands
you have in your Release 10.2 configuration files.
Related Commands
Command
Description
Changes the default name of the network configuration file from which to
load configuration commands.
bridge acquire
Forwards any frames for stations that the system has learned about
dynamically.
copy
FR-359
ip rcmd rsh-enable
To configure the router to allow remote users to execute commands on it using rsh, use the
ip rcmd rsh-enable global configuration command. To disable a router that is enabled for rsh, use the
no form of this command.
ip rcmd rsh-enable
no ip rcmd rsh-enable
Syntax Description
Defaults
Command Modes
Global configuration
Command History
Release
Modification
10.3
Usage Guidelines
Remote Shell (rsh), used as a client process, gives users the ability to remotely get router info (such as status)
without the need to connect into the router and then disconnect. This is valuable when looking at many
statistics on many different routers.
Use this command to enable the router to receive rsh requests from remote users. In addition to issuing
this command, you must create an entry for the remote user in the local authentication database to allow
a remote user to execute rsh commands on the router.
The no ip rcmd rsh-enable command does not prohibit a local user of the router from executing a
command on other routers and UNIX hosts on the network using rsh. The no form of this command only
disables remote access to rsh on the router.
Examples
Related Commands
Command
Description
ip rcmd remote-host
Creates an entry for the remote user in a local authentication database so that
remote users can execute commands on the router using rsh or rcp.
FR-360
78-11740-02
ip rcmd source-interface
To force rcp or rsh to use the IP address of a specified interface for all outgoing rcp/rsh communication
packets, use the ip rcmd source-interface command in global configuration mode. To disable a
previously configured ip rcmd source-interface command, use the no form of this command.
ip rcmd source-interface interface-id
no ip rcmd source-interface interface-id
Syntax Description
interface-id
Defaults
The address of the interface closest to the destination is used as the source interface for rcp/rsh
communications.
Command Modes
Global configuration
Command History
Release
Modification
11.3
Usage Guidelines
The name and number used to identify the interface. For example,
Loopback2.
If this command is not used, or if the interface specified in this command is not available (not up), the
Cisco IOS software uses the address of the interface closest to the destination as the source address.
Use this command to force the system to tag all outgoing rcp/rsh packets with the IP address associated
with the specified interface. This address is used as the source address as long as the interface is in the
up state.
This command is especially useful in cases where the router has many interfaces, and you want to ensure
that all rcp and/or rsh packets from this router have the same source IP address. A consistent address is
preferred so that the other end of the connection (the rcp/rsh server or client) can maintain a single
session. The other benefit of a consistent address is that an access list can be configured on the remote
device.
The specified interface must have an IP address associated with it. If the specified interface does not have
an IP address or is in a down state, then rcp/rsh reverts to the default. To avoid this, add an IP address to
the subinterface or bring the interface to the up state.
Examples
In the following example, the Loopback0 interface is assigned an IP address of 220.144.159.200, and
the ip rcmd source-interface command is used to specify that the source IP address for all rcp/rsh
packets will be the IP address assigned to the Loopback0 interface:
interface Loopback0
description Loopback interface
ip address 220.144.159.200 255.255.255.255
FR-361
no ip directed-broadcast
!
. . .
clock timezone GMT 0
ip subnet-zero
no ip source-route
no ip finger
ip rcmd source-interface Loopback0
ip telnet source-interface Loopback0
ip tftp source-interface Loopback0
ip ftp source-interface Loopback0
ip ftp username cisco
ip ftp password shhhhsecret
no ip bootp server
ip domain-name net.galaxy
ip name-server 220.144.159.1
ip name-server 220.144.159.2
ip name-server 219.10.2.1
!
. . .
Related Commands
Command
Description
ip rcmd remote-host
Creates an entry for the remote user in a local authentication database so that
remote users can execute commands on the router using rsh or rcp.
FR-362
78-11740-02
mop device-code
To identify the type of device sending Maintenance Operation Protocol (MOP) System Identification
(sysid) messages and request program messages, use the mop device-code global configuration
command. To set the identity to the default value, use the no form of this command.
mop device-code {cisco | ds200}
no mop device-code {cisco | ds200}
Syntax Description
cisco
ds200
Defaults
Command Modes
Global configuration
Command History
Release
Modification
10.0
Usage Guidelines
The sysid messages and request program messages use the identity information indicated by this
command.
Examples
The following example identifies a DECserver 200 device as sending MOP sysid and request program
messages:
mop device-code ds200
Related Commands
Command
Description
mop sysid
FR-363
mop retransmit-timer
To configure the length of time that the Cisco IOS software waits before resending boot requests to a
Maintenance Operation Protocol (MOP) server, use the mop retransmit-timer global configuration
command. To reinstate the default value, use the no form of this command.
mop retransmit-timer seconds
no mop retransmit-timer
Syntax Description
seconds
Defaults
4 seconds
Command Modes
Global configuration
Command History
Release
Modification
10.0
Sets the length of time (in seconds) that the software waits before resending a
message. The value is a number from 1 to 20.
Usage Guidelines
By default, when the software sends a request that requires a response from a MOP boot server and the
server does not respond, the message is re-sent after 4 seconds. If the MOP boot server and router are
separated by a slow serial link, it might take longer than 4 seconds for the software to receive a response
to its message. Therefore, you might want to configure the software to wait longer than 4 seconds before
resending the message if you are using such a link.
Examples
In the following example, if the MOP boot server does not respond within 10 seconds after the router
sends a message, the server will resend the message:
mop retransmit-timer 10
Related Commands
Command
Description
mop device-code
Identifies the type of device sending MOP sysid messages and requests
program messages.
mop enabled
FR-364
78-11740-02
mop retries
To configure the number of times the Cisco IOS software will resend boot requests to a Maintenance
Operation Protocol (MOP) server, use the mop retries global configuration command. To reinstate the
default value, use the no form of this command.
mop retries count
no mop retries
Syntax Description
count
Defaults
8 times
Command Modes
Global configuration
Command History
Release
Modification
10.0
Examples
Indicates the number of times the software will resend a MOP boot request. The
value is a number from 3 to 24.
In the following example, the software will attempt to resend a message to an unresponsive host 11 times
before declaring a failure:
mop retries 11
Related Commands
Command
Description
mop device-code
Identifies the type of device sending MOP sysid messages and requests
program messages.
mop enabled
mop retransmit-timer Configures the length of time that the Cisco IOS software waits before
resending boot requests to a MOP server.
FR-365
rsh
To execute a command remotely on a remote rsh host, use the rsh privileged EXEC command.
rsh {ip-address | host} [/user username] remote-command
Syntax Description
Defaults
ip-address
host
Name of the remote host on which to execute the command. Either the
host name or the IP address is required.
/user username
remote-command
If you do not specify the /user username keyword and argument, the Cisco IOS software sends a default
remote username. As the default value of the remote username, the software sends the username
associated with the current tty process, if that name is valid. For example, if the user is connected to the
router through Telnet and the user was authenticated through the username command, then the software
sends that username as the remote username. If the tty username is invalid, the software uses the host
name as the both the remote and local usernames.
Note
For Cisco, tty lines are commonly used for access services. The concept of tty originated with UNIX.
For UNIX systems, each physical device is represented in the file system. Terminals are sometimes
called tty devices (tty stands for teletype, the original UNIX terminal).
Command Modes
Privileged EXEC
Command History
Release
Modification
10.0
Usage Guidelines
Use the rsh command to execute commands remotely. The host on which you remotely execute the
command must support the rsh protocol, and the .rhosts files on the rsh host must include an entry that
permits you to remotely execute commands on that host.
For security reasons, the software does not default to a remote login if no command is specified, as does
UNIX. Instead, the router provides Telnet and connect services that you can use rather than rsh.
Examples
The following command specifies that the user named sharon attempts to remotely execute the UNIX ls
command with the -a argument on the remote host named mysys.cisco.com. The command output
resulting from the remote execution follows the command example:
Router1# rsh mysys.cisco.com /user sharon ls -a
.
FR-366
78-11740-02
..
.alias
.cshrc
.emacs
.exrc
.history
.login
.mailrc
.newsrc
.oldnewsrc
.rhosts
.twmrc
.xsession
jazz
FR-367
Syntax Description
Command Modes
Privileged EXEC
Command History
Release
Modification
10.0
Examples
The following is sample output from the show async bootp command:
Router# show async bootp
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
subnet-mask 255.255.0.0
time-offset -3600
time-server 192.168.1.1
Related Commands
Field
Description
bootfile... 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
Command
Description
async-bootp
FR-368
78-11740-02
tftp-server
To configure a router or a Flash memory device on the router as a TFTP server, use one of the following
tftp-server global configuration commands. This command replaces the tftp-server system command.
To remove a previously defined filename, use the no tftp-server command with the appropriate
filename.
tftp-server flash [partition-number:]filename1 [alias filename2] [access-list-number]
tftp-server rom alias filename1 [access-list-number]
no tftp-server {flash [partition-number:]filename1 | rom alias filename2}
Cisco 1600 Series and Cisco 3600 Series Routers
Syntax Description
flash
rom
filename1
Name of a file in Flash or in ROM that the TFTP server uses in answering TFTP
Read Requests.
alias
Specifies an alternate name for the file that the TFTP server uses in answering
TFTP Read Requests.
filename2
Alternate name of the file that the TFTP server uses in answering TFTP Read
Requests. A client of the TFTP server can use this alternate name in its Read
Requests.
access-list-number
(Optional) Basic IP access list number. Valid values are from 0 to 99.
partition-number:
FR-369
device:
filename
flashInternal Flash memory on the Cisco 1600 series and Cisco 3600
series routers. This is the only valid device for the Cisco 1600 series routers.
slot0First PCMCIA slot on the Cisco 3600 series and Cisco 7000 family
routers.
slot1Second PCMCIA slot on the Cisco 3600 series and Cisco 7000
family.
Name of the file on a Flash memory device that the TFTP server uses in
answering a TFTP Read Request. Use this argument only with the Cisco 1600
series, Cisco 3600 series, Cisco 7000 series, or Cisco 7500 series routers.
Defaults
Disabled
Command Modes
Global configuration
Command History
Release
Modification
11.0
Usage Guidelines
You can specify multiple filenames by repeating the tftp-server command. The system sends a copy of
the system image contained in ROM or one of the system images contained in Flash memory to any client
that issues a TFTP Read Request with this filename.
If the specified filename1 or filename2 argument exists in Flash memory, a copy of the Flash image is
sent. On systems that contain a complete image in ROM, the system sends the ROM image if the
specified filename1 or filename2 argument is not found in Flash memory.
Images that run from ROM cannot be loaded over the network. Therefore, it does not make sense to use
TFTP to offer the ROMs on these images.
On the Cisco 7000 family routers, the system sends a copy of the file contained on one of the Flash
memory devices to any client that issues a TFTP Read Request with its filename.
FR-370
78-11740-02
Examples
In the following example, the system uses TFTP to send a copy of the version-10.3 file located in Flash
memory in response to a TFTP Read Request for that file. The requesting host is checked against access
list 22.
tftp-server flash version-10.3 22
In the following example, the system uses TFTP to send a copy of the ROM image gs3-k.101 in response
to a TFTP Read Request for the gs3-k.101 file:
tftp-server rom alias gs3-k.101
In the following example, the system uses TFTP to send a copy of the version-11.0 file in response to a
TFTP Read Request for that file. The file is located on the Flash memory card inserted in slot 0.
tftp-server flash slot0:version-11.0
The following example enables a Cisco 3600 series router to operate as a TFTP server. The source
file c3640-i-mz is in the second partition of internal Flash memory.
Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
router(config)# tftp-server flash flash:2:dirt/gate/c3640-i-mz
In the following example, the source file is in the second partition of the Flash memory PC card in slot 0
on a Cisco 3600 series:
Router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
router(config)# tftp-server flash slot0:2:dirt/gate/c3640-j-mz
The following example enables a Cisco 1600 series router to operate as a TFTP server. The source
file c1600-i-mz is in the second partition of Flash memory:
router# configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
router(config)# tftp-server flash flash:2:dirt/gate/c1600-i-mz
Related Commands
Command
Description
access-list
FR-371
tftp-server system
The tftp-server system command has been replaced by the tftp-server command. See the description of
the tftp-server command in this chapter for more information.
FR-372
78-11740-02
FR-375
absolute
To specify an absolute time when a time range is in effect, use the absolute time-range configuration
command. To remove the time limitation, use the no form of this command.
absolute [start time date] [end time date]
no absolute
Syntax Description
(Optional) Absolute time and date that the permit or deny statement of the
associated access list starts going into effect. The time is expressed in 24-hour
notation, in the form of hours:minutes. For example, 8:00 is 8:00 a.m. and 20:00
is 8:00 p.m. The date is expressed in the format day month year. The minimum
start is 00:00 1 January 1993. If no start time and date are specified, the permit or
deny statement is in effect immediately.
(Optional) Absolute time and date that the permit or deny statement of the
associated access list is no longer in effect. Same time and date format as
described for the start keyword. The end time and date must be after the start time
and date. The maximum end time is 23:59 31 December 2035. If no end time and
date are specified, the associated permit or deny statement is in effect indefinitely.
Defaults
Command Modes
Time-range configuration
Command History
Release
Modification
12.0(1)T
Usage Guidelines
Time ranges are used by IP and IPX extended access lists. For more information on using these functions,
see the Release 12.2 Cisco IOS IP Configuration Guide and the Release 12.2 Cisco IOS AppleTalk and
Novell IPX Configuration Guide. Time ranges are applied to the permit or deny statements found in
these access lists.
The absolute command is one way to specify when a time range is in effect. Another way is to specify
a periodic length of time with the periodic command. Use either of these commands after the
time-range command, which enables time-range configuration mode and specifies a name for the time
range. Only one absolute entry is allowed per time-range command.
If a time-range command has both absolute and periodic values specified, then the periodic items are
evaluated only after the absolute start time is reached, and are not further evaluated after the absolute
end time is reached.
Note
All time specifications are interpreted as local time. To ensure that the time range entries take effect at
the desired times, the software clock should be synchronized using the Network Time Protocol (NTP),
or some other authoritative time source. For more information, refer to the Performing Basic System
FR-376
78-11740-02
Management chapter of the Release 12.2 Cisco IOS Configuration Fundamentals Configuration Guide.
Examples
The following example configures an access list named northeast, which references a time range named
xyz. The access list and time range together permit traffic on Ethernet interface 0 starting at noon on
January 1, 2001 and going forever.
time-range xyz
absolute start 12:00 1 January 2001
!
ip access-list extended northeast
permit ip any any time-range xyz
!
interface ethernet 0
ip access-group northeast in
The following example permits UDP traffic until noon on December 31, 2000. After that time, UDP
traffic is no longer allowed out Ethernet interface 0.
time-range abc
absolute end 12:00 31 December 2000
!
ip access-list extended northeast
permit udp any any time-range abc
!
interface ethernet 0
ip access-group northeast out
The following example permits UDP traffic out Ethernet interface 0 on weekends only, from 8:00 a.m.
on January 1, 1999 to 6:00 p.m. on December 31, 2001:
time-range test
absolute start 8:00 1 January 1999 end 18:00 31 December 2001
periodic weekends 00:00 to 23:59
!
ip access-list extended northeast
permit udp any any time-range test
!
interface ethernet 0
ip access-group northeast out
Related Commands
Command
Description
deny
Sets conditions under which a packet does not pass a named access list.
periodic
Specifies a recurring (weekly) start and end time for a time range.
permit
time-range
FR-377
alias
To create a command alias, use the alias global configuration command. To delete all aliases in a
command mode or to delete a specific alias, and to revert to the original command syntax, use the no
form of this command.
alias mode command-alias original-command
no alias mode [command-alias]
Syntax Description
mode
command-alias
Command alias.
original-command
Defaults
A set of six basic EXEC mode aliases are enabled by default. See the Usage Guidelines section of this
command for a list of default aliases.
Command Modes
Global configuration
Command History
Release
Modification
10.3
Usage Guidelines
Command Alias
Original Command
help
lo
logout
ping
resume
show
where
The default aliases in Table 44 are predefined. These default aliases can be disabled with the
no alias exec command.
Common keyword aliases (which can not be disabled) include running-config (keyword alias for
system:running-config) and startup-config (keyword alias for nvram:startup-config). See the
description of the copy command for more information about these keyword aliases.
FR-378
78-11740-02
Note that aliases can be configured for keywords instead of entire commands. You can create, for
example, an alias for the first part of any command and still enter the additional keywords and arguments
as normal.
To determine the value for the mode argument, enter the command mode in which you would issue the
original command (and in which you will issue the alias) and enter the ? command. The name of the
command mode should appear at the top of the list of commands. For example, the second line in the
following sample output shows the name of the command mode as Interface configuration:
Router#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)#interface e0
Router(config-if)#?
Interface configuration commands:
access-expression
Build a bridge boolean access expression
.
.
.
To match the name of the command mode to the acceptable mode keyword for the alias command, issue
the alias ? command. As shown in the following sample output, the keyword needed to create a
command alias for the access-expression command is interface:
Router(config)# alias ?
accept-dialin
VPDN group accept dialin configuration mode
accept-dialout
VPDN group accept dialout configuration mode
address-family
Address Family configuration mode
call-discriminator
Call Discriminator Configuration
cascustom
Cas custom configuration mode
clid-group
CLID group configuration mode
configure
Global configuration mode
congestion
Frame Relay congestion configuration mode
controller
Controller configuration mode
cptone-set
custom call progress tone configuration mode
customer-profile
customer profile configuration mode
dhcp
DHCP pool configuration mode
dnis-group
DNIS group configuration mode
exec
Exec mode
flow-cache
Flow aggregation cache config mode
fr-fr
FR/FR connection configuration mode
interface
Interface configuration mode
.
.
.
Router(config)# alias interface express access-expression
For a list of command modes with descriptions and references to related documentation, refer to the
Cisco IOS Command Modes appendix of the Release 12.2 Cisco IOS Configuration Fundamentals
Configuration Guide.
When you use online help, command aliases are indicated by an asterisk (*), and displayed in the
following format:
*command-alias=original-command
For example, the lo command alias is shown here along with other EXEC mode commands that start with
lo:
Router#lo?
*lo=logout
lock
login
logout
FR-379
When you use online help, aliases that contain multiple keyword elements separated by spaces are
displayed in quotes, as shown here:
Router(config)#alias exec device-mail telnet device.cisco.com 25
Router(config)#end
Router#device-mail?
*device-mail=telnet device.cisco.com 25"
To list only commands and omit aliases, begin your input line with a space. In the following example,
the alias td is not shown, because there is a space before the t? command line.
Router(config)#alias exec td telnet device
Router(config)#end
Router# t?
telnet terminal test tn3270 trace
To circumvent command aliases, use a space before entering the command. In the following example,
the command alias express is not recognized because a space is used before the command.
Router(config-if)#exp?
*express=access-expression
Router(config-if)# express ?
% Unrecognized command
As with commands, you can use online help to display the arguments and keywords that can follow a
command alias. In the following example, the alias td is created to represent the command telnet device.
The /debug and /line switches can be added to telnet device to modify the command:
Router(config)#alias exec td telnet device
Router(config)#end
Router#td ?
/debug
Enable telnet debugging mode
/line
Enable telnet line mode
...
whois
Whois port
<cr>
Router# telnet device
You must enter the complete syntax for the command alias. Partial syntax for aliases is not accepted. In
the following example, the parser does not recognize the command t as indicating the alias td:
Router#t
% Ambiguous command: t
Examples
In the following example, the alias fixmyrt is configured for the clear iproute 209.165.201.16 EXEC
mode command:
Router(config)# alias exec fixmyrt clear ip route 209.165.201.16
In the following example, the alias express is configured for the first part of the access-expression
interface configuration command:
Router#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)#interface e0
Router(config-if)#?
Interface configuration commands:
access-expression
Build a bridge boolean access expression
.
.
.
FR-380
78-11740-02
Router(config-if)#exit
Router(config)#alias ?
accept-dialin
accept-dialout
address-family
call-discriminator
cascustom
clid-group
configure
congestion
controller
cptone-set
customer-profile
dhcp
dnis-group
exec
flow-cache
fr-fr
interface
.
.
.
Related Commands
Command
Description
show aliases
FR-381
buffers
To make adjustments to initial buffer pool settings and to the limits at which temporary buffers are
created and destroyed, use the buffers global configuration command. To return the buffers to their
default size, use the no form of this command.
buffers {small | middle | big | verybig | large | huge | type number} {permanent | max-free |
min-free | initial} number-of-buffers
no buffers {small | middle | big | verybig | large | huge | type number} {permanent | max-free |
min-free | initial} number-of-buffers
Syntax Description
small
middle
big
verybig
large
huge
Default buffer size of this public buffer pool is 18024 bytes. This value can be
configured with the buffers huge size command.
type number
Interface type and interface number of the interface buffer pool. The type value
cannot be fddi.
permanent
Number of permanent buffers that the system tries to create and keep. Permanent
buffers are normally not trimmed by the system.
max-free
min-free
initial
Number of additional temporary buffers that are to be allocated when the system
is reloaded. This keyword can be used to ensure that the system has necessary
buffers immediately after reloading in a high-traffic environment.
number-of-buffers
Defaults
The default number of buffers in a pool is determined by the hardware configuration and can be
displayed with the show buffers EXEC command.
Command Modes
Global configuration
Command History
Release
Modification
10.0
FR-382
78-11740-02
Usage Guidelines
Note
Normally you need not adjust these parameters; do so only after consulting with technical support
personnel.
Examples
The following example keeps at least 50 small buffers free in the system:
Router(config)# buffers small min-free 50
The following example increases the permanent buffer pool allocation for big buffers to 200:
Router(config)# buffers big permanent 200
A general guideline is to display buffers with the show buffers command, observe which buffer pool is
depleted, and increase that one.
The following example increases the permanent Ethernet interface 0 buffer pool on a Cisco 4000 router
to 96 when the Ethernet 0 buffer pool is depleted:
Router(config)# buffers ethernet 0 permanent 96
Related Commands
Command
Description
load-interval
Changes the length of time for which data is used to compute load statistics.
show buffers
FR-383
Syntax Description
number-of-bytes
Defaults
18,024 bytes
Command Modes
Global configuration
Command History
Release
Modification
10.0
Usage Guidelines
Note
Examples
Use this command only after consulting with technical support personnel. The buffer size cannot be
lowered below the default.
Related Commands
Command
Description
buffers
Adjusts the initial buffer pool settings and the limits at which temporary
buffers are created and destroyed.
show buffers
FR-384
78-11740-02
calendar set
To manually set the hardware clock (calendar), use one of the formats of the calendar set EXEC
command.
calendar set hh:mm:ss day month year
calendar set hh:mm:ss month day year
Syntax Description
hh:mm:ss
day
month
year
Command Modes
EXEC
Command History
Release
Modification
10.0
Usage Guidelines
Some platforms have a hardware clock that is separate from the software clock. In Cisco IOS software
syntax, the hardware clock is called the calendar. The hardware clock is a battery-powered chip that
runs continuously, even if the router is powered off or rebooted. After you set the hardware clock, the
software clock will be automatically set from the hardware clock when the system is restarted or when
the clock read-calendar EXEC command is issued. The time specified in this command is relative to
the configured time zone.
Examples
The following example manually sets the hardware clock to 1:32 p.m. on July 23, 1997:
Router# calendar set 13:32:00 23 July 1997
Related Commands
Command
Description
clock read-calendar
Performs a one-time update of the software clock from the hardware clock
(calendar).
clock set
clock summer-time
clock timezone
clock update-calendar
Performs a one-time update of the hardware clock from the software clock.
FR-385
clock calendar-valid
To configure a system as an authoritative time source for a network based on its hardware clock
(calendar), use the clock calendar-valid global configuration command. To specify that the hardware
clock is not an authoritative time source, use the no form of this command.
clock calendar-valid
no clock calendar-valid
Syntax Description
Defaults
Command Modes
Global configuration
Command History
Release
Modification
10.0
Usage Guidelines
Some platforms have a hardware clock that is separate from the software clock. The hardware clock runs
continuously, even if the router is powered off or rebooted. If no outside time source is available on your
network, use this command to make the hardware clock an authoritative time source.
Because the hardware clock is not as accurate as other time sources, you should configure this command
only when a more accurate time source (such as NTP) is not available.
Examples
The following example configures a router as the time source for a network based on its hardware clock:
Router(config)# clock calendar-valid
Related Commands
Command
Description
ntp master
Configures the Cisco IOS software as an NTP master clock to which peers
synchronize themselves when an external NTP source is not available.
vines time use-system Sets VINES network time based on the system time.
FR-386
78-11740-02
clock read-calendar
To manually read the hardware clock (calendar) settings into the software clock, use the clock
read-calendar EXEC command.
clock read-calendar
Syntax Description
Command Modes
EXEC
Command History
Release
Modification
10.0
Usage Guidelines
Some platforms have a hardware clock that is separate from the software clock. The hardware clock runs
continuously, even if the router is powered off or rebooted. When the router is rebooted, the hardware
clock is automatically read into the software clock. However, you may use this command to manually
read the hardware clock setting into the software clock. This command is useful if the calendar set
command has been used to change the setting of the hardware clock.
Examples
The following example configures the software clock to set its date and time by the hardware clock
setting:
Router> clock read-calendar
Related Commands
Command
Description
calendar set
clock set
clock update-calendar
Performs a one-time update of the hardware clock from the software clock.
ntp update-calendar
FR-387
clock set
To manually set the system software clock, use one of the formats of the clock set command in privileged
EXEC mode.
clock set hh:mm:ss day month year
clock set hh:mm:ss month day year
Syntax Description
hh:mm:ss
day
month
year
Command Modes
Command History
Release
Modification
10.0
Usage Guidelines
Generally, if the system is synchronized by a valid outside timing mechanism, such as a Network Time
Protocol (NTP) or VINES clock source, or if you have a router with hardware clock, you need not set
the software clock. Use this command if no other time sources are available. The time specified in this
command is relative to the configured time zone.
Examples
The following example manually sets the software clock to 1:32 p.m. on July 23, 1997:
Router# clock set 13:32:00 23 July 1997
Related Commands
Command
Description
calendar set
clock read-calendar
Performs a one-time update of the software clock from the hardware clock
(calendar).
clock summer-time
clock timezone
FR-388
78-11740-02
clock summer-time
To configure the system to automatically switch to summer time (daylight saving time), use one of the
formats of the clock summer-time global configuration command. To configure the Cisco IOS software
not to automatically switch to summer time, use the no form of this command.
clock summer-time zone recurring [week day month hh:mm week day month hh:mm [offset]]
clock summer-time zone date date month year hh:mm date month year hh:mm [offset]
clock summer-time zone date month date year hh:mm month date year hh:mm [offset]
no clock summer-time
Syntax Description
zone
Name of the time zone (for example, PDT for Pacific Daylight Time) to be displayed
when summer time is in effect.
recurring
Indicates that summer time should start and end on the corresponding specified days
every year.
date
Indicates that summer time should start on the first specific date listed in the command
and end on the second specific date in the command.
week
day
date
month
year
hh:mm
offset
Defaults
Summer time is disabled. If the clock summer-time zone recurring command is specified without
parameters, the summer time rules default to United States rules. Default of the offset argument is 60.
Command Modes
Global configuration
Command History
Release
Modification
10.0
Usage Guidelines
Use this command if you want to automatically switch to summer time (for display purposes only). Use
the recurring form of the command if the local summer time rules are of this form. Use the date form
to specify a start and end date for summer time if you cannot use the recurring form.
FR-389
In both the date and recurring forms of the command, the first part of the command specifies when
summer time begins, and the second part specifies when it ends. All times are relative to the local time
zone. The start time is relative to standard time. The end time is relative to summer time. If the starting
month is chronologically after the ending month, the system assumes that you are in the southern
hemisphere.
Examples
The following example specifies that summer time starts on the first Sunday in April at 2 a.m. and ends
on the last Sunday in October at 2 a.m.:
Router(config)# clock summer-time PDT recurring 1 Sunday April 2:00 last Sunday October
2:00
If you live in a place where summer time does not follow the pattern in the first example, you can specify
the exact date and times. In the following example, daylight saving time (summer time) is configured to
start on October 12, 1997 at 2 a.m., and end on April 26, 1998 at 2 a.m.:
Router(config)# clock summer-time date 12 October 1997 2:00 26 April 1998 2:00
Related Commands
Command
Description
calendar set
clock timezone
FR-390
78-11740-02
clock timezone
To set the time zone for display purposes, use the clock timezone global configuration command. To set
the time to Coordinated Universal Time (UTC), use the no form of this command.
clock timezone zone hours-offset [minutes-offset]
no clock timezone
Syntax Description
zone
hours-offset
minutes-offset
Defaults
UTC
Command Modes
Global configuration
Command History
Release
Modification
10.0
Usage Guidelines
The system internally keeps time in UTC, so this command is used only for display purposes and when
the time is manually set.
Table 45 lists common time zone acronyms used for the zone argument.
Table 45
Acronym
Europe
GMT
BST
IST
WET
WEST
CET
CEST
EET
EEST
MSK
MSD
FR-391
Table 45
Acronym
AST
ADT
ET
EST
EDT
CT
CST
CDT
MT
MST
MDT
PT
PST
PDT
AKST
AKDT
HST
Australia
WST
CST
EST
Table 46 lists an alternative method for referring to time zones, in which single letters are used to refer
to the time zone difference from UTC. Using this method, the letter Z is used to indicate the zero
meridian, equivalent to UTC, and the letter J (Juliet) is used to refer to the local time zone. Using this
method, the International Date Line is between time zones M and Y.
Table 46
Letter Designator
Word Designator
Yankee
UTC 12 hours
Xray
UTC 11 hours
Whiskey
UTC 10 hours
FR-392
78-11740-02
Table 46
Letter Designator
Word Designator
Yankee
UTC 12 hours
Victor
UTC 9 hours
Uniform
UTC 8 hours
Tango
UTC 7 hours
Sierra
UTC 6 hours
Romeo
UTC 5 hours
Quebec
UTC 4 hours
Papa
UTC 3 hours
Oscar
UTC 2 hours
November
UTC 1 hour
Zulu
Same as UTC
Alpha
UTC +1 hour
Bravo
UTC +2 hours
Charlie
UTC +3 hours
Delta
UTC +4 hours
Echo
UTC +5 hours
Foxtrot
UTC +6 hours
Golf
UTC +7 hours
Hotel
UTC +8 hours
India
UTC +9 hours
Kilo
Lima
Mike
The following example sets the time zone to Pacific Standard Time (PST), which is 8 hours behind UTC:
Router(config)# clock timezone PST -8
The following example sets the time zone to Atlantic Time (AT) for Newfoundland, Canada, which is
3.5 hours behind UTC:
Router(config)# clock timezone AT -3 30
FR-393
Related Commands
Command
Description
calendar set
clock set
clock summer-time
show clock
FR-394
78-11740-02
clock update-calendar
To perform a one-time update of the hardware clock (calendar) from the software clock, use the clock
update-calendar in user or privileged EXEC mode.
clock update-calendar
Syntax Description
Command Modes
EXEC
Command History
Release
Modification
10.0
Usage Guidelines
Some platforms have a hardware clock (calendar) in addition to a software clock. The hardware clock is
battery operated, and runs continuously, even if the router is powered off or rebooted.
If the software clock and hardware clock are not synchronized, and the software clock is more accurate,
use this command to update the hardware clock to the correct date and time.
Examples
The following example copies the current date and time from the software clock to the hardware clock:
Router> clock update-calendar
Related Commands
Command
Description
clock read-calendar
Performs a one-time update of the software clock from the hardware clock
(calendar).
ntp update-calendar
FR-395
downward-compatible-config
To generate a configuration that is compatible with an earlier Cisco IOS release, use the
downward-compatible-config global configuration command. To remove this feature, use the no form
of this command.
downward-compatible-config version
no downward-compatible-config
Syntax Description
version
Defaults
Disabled
Command Modes
Global configuration
Command History
Release
Modification
11.1
Usage Guidelines
In Cisco IOS Release 10.3, IP access lists changed format. Use the downward-compatible-config
command to regenerate a configuration in a format prior to Release 10.3 if you are going to downgrade
from your software version to version 10.2 or 10.3. The earliest version value this command accepts
is 10.2.
When this command is configured, the router attempts to generate a configuration that is compatible with
the specified version. Note that this command affects only IP access lists.
Under some circumstances, the software might not be able to generate a fully backward-compatible
configuration. In such a case, the software issues a warning message.
Examples
The following example generates a configuration file compatible with Cisco IOS Release 10.2 access
lists:
Router(config)# downward-compatible-config 10.2
Related Commands
Command
Description
access-list (extended)
Provides extended access lists that allow more detailed access lists.
access-list (standard)
FR-396
78-11740-02
hostname
To specify or modify the host name for the network server, use the hostname global configuration
command.
hostname name
Syntax Description
name
Defaults
Command Modes
Global configuration
Command History
Release
Modification
10.0
Usage Guidelines
Examples
Related Commands
Command
Description
setup
FR-397
ip bootp server
To enable the BOOTP service on your routing device, use the ip bootp server global configuration
command. To disable BOOTP services, use the no form of the command.
ip bootp server
no ip bootp server
Syntax Description
Defaults
Enabled
Command Modes
Global configuration
Command History
Release
Modification
11.2
Usage Guidelines
By default, the BOOTP service is enabled. When disabled, the no ip bootp server command will appear
in the configuration file.
The integrated Dynamic Host Configuration Protocol (DHCP) server was introduced in Cisco IOS
Release 12.0(1)T. Because DHCP is based on BOOTP, both of these services share the well-known
UDP server port of 67 (per RFC 951, RFC 1534, and RFC 2131). If both the BOOTP server and DHCP
server are disabled, and a helper address is not configured, "ICMP port unreachable" messages will be
sent in response to incoming requests on port 67, and the original incoming packet will be discarded.
Note
As with all minor services, the async line BOOTP service should be disabled on your system if you do
not have a need for it in your network.
Any network device that has UDP, TCP, BOOTP, DHCP or Finger services should be protected by a
firewall or have the services disabled to protect against Denial of Service attacks.
Examples
In the following example, BOOTP and DHCP services are disabled on the router:
Router(config)# no ip bootp server
Router(config)# no service dhcp
Related Commands
Command
Description
service dhcp
FR-398
78-11740-02
ip finger
To configure a system to accept Finger protocol requests (defined in RFC 742), use the ip finger global
configuration command. To disable this service, use the no form of this command.
ip finger [rfc-compliant]
no ip finger
Syntax Description
rfc-compliant
Defaults
Disabled
Command Modes
Global configuration
Command History
Release
Usage Guidelines
Modification
11.3
12.1(5), 12.1(5)T
This command was changed from being enabled by default to being disabled
by default.
The Finger service allows remote users to view the output equivalent to the show users [wide]
command.
When ip finger is configured, the router will respond to a telnet a.b.c.d finger command from a remote
host by immediately displaying the output of the show users command and then closing the connection.
When the ip finger rfc-compliant command is configured, the router will wait for input before
displaying anything (as required by RFC 1288). The remote user can then enter the Return key to display
the output of the show users EXEC command, or enter /W to display the output of the show users wide
EXEC command. After this information is displayed, the connection is closed.
Note
As with all minor services, the Finger service should be disabled on your system if you do not have a
need for it in your network.
Any network device that has UDP, TCP, BOOTP, or Finger services should be protected by a firewall or
have the services disabled to protect against Denial of Service attacks.
Because of the potential for hung lines, the rfc-compliant form of this command should not be
configured for devices with more than 20 simultaneous users.
FR-399
Examples
FR-400
78-11740-02
ip telnet source-interface
To specify the IP address of an interface as the source address for Telnet connections, use the ip telnet
source-interface global configuration command. To reset the source address to the default for each
connection, use the no form of this command.
ip telnet source-interface interface
no ip telnet source-interface
Syntax Description
interface
Defaults
The address of the closest interface to the destination as the source address.
Command Modes
Global configuration
Command History
Release
Modification
11.1
Usage Guidelines
The interface whose address is to be used as the source for Telnet connections.
Use this command to set the IP address of an interface as the source for all Telnet connections.
If the specified interface is not up, the Cisco IOS software selects the address of the interface closest to
the destination as the source address.
Examples
The following example forces the IP address for Ethernet interface 1 as the source address for Telnet
connections:
Router(config)# ip telnet source-interface Ethernet1
Related Commands
Command
Description
ip radius
source-interface
FR-401
ip tftp source-interface
To specify the IP address of an interface as the source address for TFTP connections, use the ip tftp
source-interface global configuration command. To return to the default, use the no form of this
command.
ip tftp source-interface interface
no ip tftp source-interface
Syntax Description
interface
Defaults
The address of the closest interface to the destination as the source address.
Command Modes
Global configuration
Command History
Release
Modification
11.1
Usage Guidelines
The interface whose address is to be used as the source for TFTP connections.
Use this command to set the IP address of an interface as the source for all TFTP connections.
If the specified interface is not up, the Cisco IOS software selects the address of the interface closest to
the destination as the source address.
Examples
In the following example, the IP address assigned to the Loopback0 interface will be used as the source
address for TFTP connections:
Router(config)# ip tftp source-interface Loopback0
Related Commands
Command
Description
ip ftp source-interface
ip radius source-interface
FR-402
78-11740-02
load-interval
To change the length of time for which data is used to compute load statistics, use the load-interval
interface configuration command. To revert to the default setting, use the no form of this command.
load-interval seconds
no load-interval seconds
Syntax Description
seconds
Defaults
Command Modes
Interface configuration
Command History
Release
Modification
10.3
Usage Guidelines
Length of time for which data is used to compute load statistics. A value that is
a multiple of 30, from 30 to 600 (30, 60, 90, 120, and so on).
If you want load computations to be more reactive to short bursts of traffic, rather than averaged over
5-minute periods, you can shorten the length of time over which load averages are computed.
If the load interval is set to 30 seconds, new data is used for load calculations over a 30-second period.
This data is used to compute load statistics, including input rate in bits and packets per second, output
rate in bits and packets per second, load, and reliability.
Load data is gathered every 5 seconds. This data is used for a weighted average calculation in which
more-recent load data has more weight in the computation than older load data. If the load interval is set
to 30 seconds, the average is computed for the last 30 seconds of load data.
The load-interval command allows you to change the default interval of 5 minutes to a shorter or longer
period of time. If you change it to a shorter period of time, the input and output statistics that are
displayed when you use the show interface command will be more current, and based on more
instantaneous data, rather than reflecting a more average load over a longer period of time.
This command is often used for dial backup purposes, to increase or decrease the likelihood of a backup
interface being implemented, but it can be used on any interface.
Examples
In the following example, the default 5-minute average is set to a 30-second average. A burst in traffic
that would not trigger a dial backup for an interface configured with the default 5-minute interval might
trigger a dial backup for this interface that is set for a shorter, 30-second interval.
Router(config)# interface serial 0
Router(config-if)# load-interval 30
FR-403
Related Commands
Command
Description
show interfaces
FR-404
78-11740-02
ntp access-group
To control access to the Network Time Protocol (NTP) services on the system, use the ntp access-group
command in global configuration mode. To remove access control to the NTP services, use the no form
of this command.
ntp access-group {query-only | serve-only | serve | peer} access-list-number
no ntp
Syntax Description
query-only
Allows only NTP control queries. See RFC 1305 (NTP version 3).
serve-only
serve
Allows time requests and NTP control queries, but does not allow the
system to synchronize to the remote system.
peer
Allows time requests and NTP control queries and allows the system to
synchronize to the remote system.
access-list-number
Defaults
Command Modes
Global configuration
Command History
Release
Modification
10.0
Usage Guidelines
The access group options are scanned in the following order from least restrictive to most restrictive:
1.
peer
2.
serve
3.
serve-only
4.
query-only
Access is granted for the first match that is found. If no access groups are specified, all access is granted
to all sources. If any access groups are specified, only the specified access is granted. This facility
provides minimal security for the time services of the system. However, it can be circumvented by a
determined programmer. If tighter security is desired, use the NTP authentication facility.
When you configure NTP, you must include at least one of the available keywords; the NTP service is
activated and the keyword takes effect.
In the no form of ntp commands, all the keywords are optional. When you enter the no ntp command
followed by one or more of its keywords, only the functions activated by those keywords are removed
from the NTP service. The NTP service itself remains active, along with all functions you have not
specified in the no ntp command.
FR-405
To terminate NTP service on a device, you must enter the no ntp command without keywords.
For example, if you previously issued the ntp access-group command and you now want to remove not
only the access group, but all NTP functions from the device, use the no ntp command without any
keywords. This ensures that all NTP functions are removed and that the NTP service is also terminated.
Examples
The following example shows how to configure a system to allow itself to be synchronized by a peer
from access list 99. However, the system restricts access to allow only time requests from access list 42.
Router(config)# ntp access-group peer 99
Router(config)# ntp access-group serve-only 42
The following example shows how to remove all the configured NTP options and disable the ntp server:
Router(config)# no ntp
Related Commands
Command
Description
access-list
Configures the access list mechanism for filtering frames by protocol type or
vendor code.
FR-406
78-11740-02
ntp authenticate
To enable Network Time Protocol (NTP) authentication, use the ntp authenticate command in global
configuration mode. To disable the function, use the no form of this command.
ntp authenticate
no ntp
Syntax Description
Defaults
No authentication
Command Modes
Global configuration
Command History
Release
Modification
10.0
Usage Guidelines
Use this command if you want authentication. If this command is specified, the system will not
synchronize to a system unless it carries one of the authentication keys specified in the ntp trusted-key
global configuration command.
When you configure NTP, you must include at least one of the available keywords; the NTP service is
activated and the keyword takes effect.
In the no form of ntp commands, all the keywords are optional. When you enter the no ntp command
followed by one or more of its keywords, only the functions activated by those keywords are removed
from the NTP service. The NTP service itself remains active, along with all functions you have not
specified in the no ntp command.
To terminate NTP service on a device, you must enter the no ntp command without keywords.
For example, if you previously issued the ntp authenticate command and you now want to disable not
only the authentication, but all NTP functions from the device, use the no ntp command without any
keywords. This ensures that all NTP functions are removed and that the NTP service is also terminated.
Examples
The following example shows how to configure the system to synchronize only to systems that provide
authentication key 42 in their NTP packets:
Router(config)# ntp authenticate
Router(config)# ntp authentication-key 42 md5 aNiceKey
Router(config)# ntp trusted-key 42
The following example shows how to remove all the configured NTP options and disable the ntp server:
Router(config)# no ntp
FR-407
Related Commands
Command
Description
ntp
authentication-key
ntp trusted-key
FR-408
78-11740-02
ntp authentication-key
To define an authentication key for Network Time Protocol (NTP), use the ntp authentication-key
command in global configuration mode. To remove the authentication key for NTP, use the no form of
this command.
ntp authentication-key number md5 value
no ntp
Syntax Description
number
md5
value
Defaults
Command Modes
Global configuration
Command History
Release
Modification
10.0
Usage Guidelines
Note
Use this command to define authentication keys for use with other NTP commands in order to provide
a higher degree of security.
When this command is written to NVRAM, the key is encrypted so that it is not displayed when the
configuration is viewed.
When you configure NTP, you must include at least one of the available keywords; the NTP service is
activated and the keyword takes effect.
In the no form of ntp commands, all the keywords are optional. When you enter the no ntp command
followed by one or more of its keywords, only the functions activated by those keywords are removed
from the NTP service. The NTP service itself remains active, along with all functions you have not
specified in the no ntp command.
To terminate NTP service on a device, you must enter the no ntp command without keywords.
For example, if you previously issued the ntp authentication-key command and you now want to
remove not only the authentication key, but all NTP functions from the device, use the no ntp command
without any keywords. This ensures that all NTP functions are removed and that the NTP service is also
terminated.
FR-409
Examples
The following example shows how to configure the system to synchronize only to systems providing
authentication key 42 in their NTP packets:
Router(config)# ntp authenticate
Router(config)# ntp authentication-key 42 md5 aNiceKey
Router(config)# ntp trusted-key 42
The following example shows how to remove all the configured NTP options and disable the ntp server:
Router(config)# no ntp
Related Commands
Command
Description
ntp authenticate
ntp peer
ntp server
ntp trusted-key
FR-410
78-11740-02
Syntax Description
Defaults
Disabled
Command Modes
Interface configuration
Command History
Release
Modification
10.0
Usage Guidelines
Use this command to allow the system to listen to broadcast packets on an interface-by-interface basis.
When you configure NTP, you must include at least one of the available keywords; the NTP service is
activated and the keyword takes effect.
In the no form of ntp commands, all the keywords are optional. When you enter the no ntp command
followed by one or more of its keywords, only the functions activated by those keywords are removed
from the NTP service. The NTP service itself remains active, along with all functions you have not
specified in the no ntp command.
To terminate NTP service on a device, you must enter the no ntp command without keywords.
For example, if you previously issued the ntp broadcast client command and you now want to remove
not only the broadcast client capability, but all NTP functions from the device, use the no ntp command
without any keywords. This ensures that all NTP functions are removed and that the NTP service is also
terminated.
Examples
In the following example, the system is configured to receive (listen to) NTP broadcasts on Ethernet
interface 1:
Router(config)# interface ethernet 1
Router(config-if)# ntp broadcast client
The following example shows how to remove all the configured NTP options and disable the ntp server:
Router(config)# no ntp
FR-411
Related Commands
Command
Description
ntp broadcast
ntp broadcastdelay
Sets the estimated round-trip delay between the system and an NTP
broadcast server.
FR-412
78-11740-02
ntp broadcast
To configure the system to send Network Time Protocol (NTP) broadcast packets on a specified
interface, use the ntp broadcast command in interface configuration mode. To disable this capability,
use the no form of this command.
ntp broadcast [version number]
no ntp
Syntax Description
version
number
Defaults
Disabled
Command Modes
Interface configuration
Command History
Release
Modification
10.0
Usage Guidelines
When you configure NTP, you must include at least one of the available keywords; the NTP service is
activated and the keyword takes effect.
In the no form of ntp commands, all the keywords are optional. When you enter the no ntp command
followed by one or more of its keywords, only the functions activated by those keywords are removed
from the NTP service. The NTP service itself remains active, along with all functions you have not
specified in the no ntp command.
To terminate NTP service on a device, you must enter the no ntp command without keywords.
For example, if you previously issued the ntp broadcast command and you now want to remove not only
the broadcast capability, but all NTP functions from the device, use the no ntp command without any
keywords. This ensures that all NTP functions are removed and that the NTP service is also terminated.
Examples
The following example shows how to configures Ethernet interface 0 to send NTP version 2 broadcasts:
Router(config)# interface ethernet 0
Router(config-if)# ntp broadcast version 2
The following example shows how to remove all the configured NTP options and disable the ntp server:
Router(config)# no ntp
FR-413
Related Commands
Command
Description
ntp broadcastdelay
Sets the estimated round-trip delay between the Cisco IOS software and an
NTP broadcast server.
FR-414
78-11740-02
ntp broadcastdelay
To set the estimated round-trip delay between the Cisco IOS software and a Network Time Protocol
(NTP) broadcast server, use the ntp broadcastdelay command in global configuration mode. To revert
to the default value, use the no form of this command.
ntp broadcastdelay microseconds
no ntp
Syntax Description
microseconds
Defaults
3000 microseconds
Command Modes
Global configuration
Command History
Release
Modification
10.0
Usage Guidelines
Estimated round-trip time (in microseconds) for NTP broadcasts. The range is
from 1 to 999999.
Use this command when the router is configured as a broadcast client and the round-trip delay on the
network is other than 3000 microseconds.
When you configure NTP, you must include at least one of the available keywords; the NTP service is
activated and the keyword takes effect.
In the no form of ntp commands, all the keywords are optional. When you enter the no ntp command
followed by one or more of its keywords, only the functions activated by those keywords are removed
from the NTP service. The NTP service itself remains active, along with all functions you have not
specified in the no ntp command.
To terminate NTP service on a device, you must enter the no ntp command without keywords.
For example, if you previously issued the ntp broadcastdelay command and you now want to remove
not only the delay setting, but all NTP functions from the device, use the no ntp command without any
keywords. This ensures that all NTP functions are removed and that the NTP service is also terminated.
Examples
The following example shows how to set the estimated round-trip delay between a router and the
broadcast client to 5000 microseconds:
Router(config)# ntp broadcastdelay 5000
The following example shows how to remove all the configured NTP options and disable the ntp server:
Router(config)# no ntp
FR-415
Related Commands
Command
Description
ntp broadcast
FR-416
78-11740-02
ntp clock-period
Caution
Do not enter this command; it is documented for informational purposes only. The system automatically
generates this command as Network Time Protocol (NTP) determines the clock error and compensates.
As NTP compensates for the error in the software clock, it keeps track of the correction factor for this
error. The system automatically saves this value into the system configuration when the
ntp clock-period command is issued in global configuration mode. To revert to the default, use the no
form of this command.
ntp clock-period value
no ntp
Syntax Description
value
Defaults
Command Modes
Global configuration
Command History
Release
Modification
10.0
Usage Guidelines
Amount of time to add to the software clock for each clock hardware tick (this
value is multiplied by 2-32).
FR-417
Examples
The following example shows a typical difference between the values of the NTP clock-period setting
in the running configuration and in the startup configuration:
Router# show startup-config | include clock-period
ntp clock-period 17180239
Router# show running-config | include clock-period
ntp clock-period 17180255
The following example shows how to remove all the configured NTP options and disable the ntp server:
Router(config)# no ntp
FR-418
78-11740-02
ntp disable
To prevent an interface from receiving Network Time Protocol (NTP) packets, use the ntp disable
command in interface configuration mode. To enable receipt of NTP packets on an interface, use the no
form of this command.
ntp disable
no ntp
Syntax Description
Defaults
Enabled
Command Modes
Interface configuration
Command History
Release
Modification
10.0
Usage Guidelines
Examples
The following example shows how to prevent Ethernet interface 0 from receiving NTP packets:
Router(config)# interface ethernet 0
Router(config-if)# ntp disable
The following example shows how to remove all the configured NTP options and disable the ntp server:
Router(config)# no ntp
FR-419
ntp master
To configure the Cisco IOS software as a Network Time Protocol (NTP) master clock to which peers
synchronize themselves when an external NTP source is not available, use the ntp master command in
global configuration mode. To disable the master clock function, use the no form of this command.
ntp master [stratum]
no ntp
Caution
Use this command with caution. It is very easy to override valid time sources using this command,
especially if a low stratum number is configured. Configuring multiple devices in the same network with
the ntp master command can cause instability in keeping time if the devices do not agree on the time.
Syntax Description
stratum
Defaults
By default, the master clock function is disabled. When enabled, the default stratum is 8.
Command Modes
Global configuration
Command History
Release
Modification
10.0
Usage Guidelines
(Optional) Number from 1 to 15. Indicates the NTP stratum number that the system will
claim.
Because the Cisco implementation of NTP does not support directly attached radio or atomic clocks, the
router is normally synchronized, directly or indirectly, to an external system that has such a clock. In a
network without Internet connectivity, such a time source may not be available. The ntp master
command is used in such cases.
If the system has ntp master configured, and it cannot reach any clock with a lower stratum number, the
system will claim to be synchronized at the configured stratum number, and other systems will be willing
to synchronize to it via NTP.
Note
The software clock must have been set from some source, including manually, before the ntp master
command will have any effect. This protects against distributing erroneous time after the system is
restarted.
When you configure NTP, you must include at least one of the available keywords; the NTP service is
activated and the keyword takes effect.
FR-420
78-11740-02
In the no form of ntp commands, all the keywords are optional. When you enter the no ntp command
followed by one or more of its keywords, only the functions activated by those keywords are removed
from the NTP service. The NTP service itself remains active, along with all functions you have not
specified in the no ntp command.
To terminate NTP service on a device, you must enter the no ntp command without keywords.
For example, if you previously issued the ntp master command and you now want to remove not only
the master clock function, but all NTP functions from the device, use the no ntp command without any
keywords. This ensures that all NTP functions are removed and that the NTP service is also terminated.
Examples
The following example shows how to configure a router as an NTP master clock to which peers may
synchronize:
Router(config)# ntp master 10
The following example shows how to remove all the configured NTP options and disable the ntp server:
Router(config)# no ntp
Related Commands
Command
Description
clock calendar-valid
Configures the system hardware clock an authoritative time source for the
network.
FR-421
ntp max-associations
To configure the maximum number of Network Time Protocol (NTP) peers and clients for the routing
device, use the ntp max-associations command in global configuration mode. To return the maximum
associations value to the default, use the no form of this command.
ntp max-associations number
no ntp
Syntax Description
number
Defaults
Command Modes
Global configuration
Command History
Release
Modification
12.0
Usage Guidelines
The router can be configured to define the maximum number of NTP peer and client associations that
the router will serve. The ntp max-associations command is used to set this limit.
This command is useful for ensuring that that the router is not overwhelmed by huge numbers of NTP
synchronization requests or, for an NTP master server, to allow large numbers of devices to sync to the
router.
When you configure NTP, you must include at least one of the available keywords; the NTP service is
activated and the keyword takes effect.
In the no form of ntp commands, all the keywords are optional. When you enter the no ntp command
followed by one or more of its keywords, only the functions activated by those keywords are removed
from the NTP service. The NTP service itself remains active, along with all functions you have not
specified in the no ntp command.
To terminate NTP service on a device, you must enter the no ntp command without keywords.
For example, if you previously issued the ntp max-associations command and you now want to remove
not only that maximum value, but all NTP functions from the device, use the no ntp command without
any keywords. This ensures that all NTP functions are removed and that the NTP service is also
terminated.
FR-422
78-11740-02
Examples
In the following example, the router is configured to act as an NTP server to 200 clients:
Router(config)# ntp max-associations 200
The following example shows how to remove all the configured NTP options and disable the ntp server:
Router(config)# no ntp
Related Commands
Command
Description
FR-423
Syntax Description
ip-address
Defaults
Disabled
Command Modes
Interface configuration
Command History
Release
Modification
12.1
Usage Guidelines
Use this command to allow the system to listen to multicast packets on an interface-by-interface basis.
When you configure NTP, you must include at least one of the available keywords; the NTP service is
activated and the keyword takes effect.
In the no form of ntp commands, all the keywords are optional. When you enter the no ntp command
followed by one or more of its keywords, only the functions activated by those keywords are removed
from the NTP service. The NTP service itself remains active, along with all functions you have not
specified in the no ntp command.
To terminate NTP service on a device, you must enter the no ntp command without keywords.
For example, if you previously issued the ntp multicast client command and you now want to remove
not only the multicast client capability, but all NTP functions from the device, use the no ntp command
without any keywords. This ensures that all NTP functions are removed and that the NTP service is also
terminated.
Examples
In the following example, the system is configured to receive (listen to) NTP multicast packets on
Ethernet interface 1:
Router(config)# interface ethernet 1
Router(config-if)# ntp multicast client
The following example shows how to remove all the configured NTP options and disable the ntp server:
Router(config)# no ntp
FR-424
78-11740-02
Related Commands
Command
Description
ntp multicast
FR-425
ntp multicast
To configure a system to send Network Time Protocol (NTP) multicast packets on a specified interface,
use the ntp multicast interface configuration command. To disable this capability, use the no form of
this command.
ntp multicast [ip-address] [key key-id] [ttl value] [version number]
no ntp
Syntax Description
ip-address
key
key-id
ttl
value
(Optional) TTL value in the range from 1 to 255. Default TTL value is 16.
version
number
Defaults
Disabled
Command Modes
Interface configuration
Command History
Release
Modification
12.1
Usage Guidelines
The TTL value is used to limit the scope of an audience for multicast routing.
When you configure NTP, you must include at least one of the available keywords; the NTP service is
activated and the keyword takes effect.
In the no form of ntp commands, all the keywords are optional. When you enter the no ntp command
followed by one or more of its keywords, only the functions activated by those keywords are removed
from the NTP service. The NTP service itself remains active, along with all functions you have not
specified in the no ntp command.
To terminate NTP service on a device, you must enter the no ntp command without keywords.
For example, if you previously issued the ntp multicast command and you now want to remove not only
the multicast capability, but all NTP functions from the device, use the no ntp command without any
keywords. This ensures that all NTP functions are removed and that the NTP service is also terminated.
FR-426
78-11740-02
Examples
The following example shows how to configure Ethernet interface 0 to send NTP version 2 broadcasts:
Router(config)# interface ethernet 0
Router(config-if)# ntp multicast version 2
The following example shows how to remove all the configured NTP options and disable the ntp server:
Router(config)# no ntp
Related Commands
Command
Description
ntp authentication-key
FR-427
ntp peer
To configure the software clock to synchronize a peer or to be synchronized by a peer, use the ntp peer
command in global configuration mode. To disable this capability, use the no form of this command.
ntp peer ip-address [normal-sync] [version number] [key key-id] [source interface] [prefer]
no ntp
Syntax Description
ip-address
normal-sync
version
number
key
keyid
source
interface
(Optional) Name of the interface from which to pick the IP source address.
prefer
(Optional) Makes this peer the preferred peer that provides synchronization.
Command Default
Command Modes
Global configuration
Command History
Release
Modification
10.0
12.3(14)T
Usage Guidelines
When a peer is configured, the default NTP version number is 3, no authentication key is used, and the
source IP address is taken from the outgoing interface.
Use this command to allow a device to synchronize with a peer, or vice versa. Using the prefer keyword
reduces switching between peers.
Tip
If you are using the default version of 3 and NTP synchronization does not occur, try using NTP
version 2 (NTPv2).
When you configure NTP, you must include at least one of the available keywords; the NTP service is
activated and the keyword takes effect.
FR-428
78-11740-02
In the no form of ntp commands, all the keywords are optional. When you enter the no ntp command
followed by one or more of its keywords, only the functions activated by those keywords are removed
from the NTP service. The NTP service itself remains active, along with all functions you have not
specified in the no ntp command.
To terminate NTP service on a device, you must enter the no ntp command without keywords.
For example, if you previously issued the ntp peer command and you now want to remove not only the
peer, but all NTP functions from the device, use the no ntp command without any keywords. This
ensures that all NTP functions are removed and that the NTP service is also terminated.
Examples
The following example shows how to configure a router to allow its software clock to be synchronized
with the clock of the peer (or vice versa) at IP address 192.168.22.33 using NTP version 2. The source
IP address is the address of Ethernet 0.
Router(config)# ntp peer 192.168.22.33 version 2 source ethernet 0
The following example shows how to remove all the configured NTP options and disable the ntp server:
Router(config)# no ntp
Related Commands
Command
Description
ntp authentication-key
ntp server
ntp source
FR-429
ntp refclock
To configure an external clock source for use with Network Time Protocol (NTP) services, use the ntp
refclock command in line configuration mode. To disable support of the external time source, use the
no form of this command.
ntp refclock {trimble | telecom-solutions} pps {cts | ri | none} [inverted] [pps-offset number]
[stratum number] [timestamp-offset number]
no ntp
Syntax Description
trimble
Enables the reference clock driver for the Trimble Palisade NTP
Synchronization Kit (Cisco 7200 series routers only).
telecom-solutions
Enables the reference clock driver for a Telecom Solutions GPS device.
pps
Pulse per second (PPS) signal line. Indicate PPS pulse reference clock
support. Choices are cts, ri, or none.
cts
ri
none
inverted
pps-offset number
(Optional) Offset of PPS pulse. The number is the offset (in milliseconds).
stratum number
(Optional) Number from 0 to 14. Indicates the NTP stratum number that the
system will claim.
timestamp-offset
number
(Optional) Offset of time stamp. The number is the offset (in milliseconds).
Defaults
Command Modes
Line configuration
Command History
Release
Modification
12.1
The trimble keyword was added to provide driver activation for a Trimble
GPS time source on the Cisco 7200 series router.
Usage Guidelines
To configure a PPS signal as the source for NTP synchronization, use the following form of the ntp
refclock command:
ntp refclock pps {cts | ri} [inverted] [pps-offset number] [stratum number] [timestamp-offset
number]
To configure a Trimble Palisade NTP Synchronization Kit as the GPS clock source connected to the
auxiliary port of a Cisco 7200 router, use the following form of the ntp refclock command:
ntp refclock trimble pps none [stratum number]
FR-430
78-11740-02
To configure a Telecom Solutions product as the GPS clock source, use the ntp refclock
telecom-solutions form of the command:
ntp refclock telecom-solutions pps cts [stratum number]
When you configure NTP, you must include at least one of the available keywords; the NTP service is
activated and the keyword takes effect.
In the no form of ntp commands, all the keywords are optional. When you enter the no ntp command
followed by one or more of its keywords, only the functions activated by those keywords are removed
from the NTP service. The NTP service itself remains active, along with all functions you have not
specified in the no ntp command.
To terminate NTP service on a device, you must enter the no ntp command without keywords.
For example, if you previously issued the ntp refclock command and you now want to remove not only
the external clock source, but all NTP functions from the device, use the no ntp command without any
keywords. This ensures that all NTP functions are removed and that the NTP service is also terminated.
Examples
The following example shows configuration of a Trimble Palisade GPS time source on a Cisco 7200
router:
Router(config)# ntp master
Router(config)# ntp update-calendar
Router(config)# line aux 0
Router(config-line)# ntp refclock trimble pps none
The following example shows configuration of a Telecom Solutions GPS time source on a Catalyst
switch platform:
Router(config)# ntp master
Router(config)# ntp update-calendar
Router(config)# line aux 0
Router(config-line)# ntp refclock telecom-solutions pps cts stratum 1
The following example shows how to remove all the configured NTP options and disable the ntp server:
Router(config)# no ntp
Related Commands
Command
Description
FR-431
ntp server
To allow the software clock to be synchronized by a Network Time Protocol (NTP) time server, use the
ntp server command in global configuration mode. To disable this capability, use the no form of this
command.
ntp server ip-address | hostname [version number] [key key-id] [source interface] [prefer]
no ntp
Syntax Description
ip-address
hostname
version
number
key
key-id
source
(Optional) Identifies the interface from which to pick the IP source address.
interface
(Optional) Name of the interface from which to pick the IP source address.
prefer
(Optional) Specifies that the server referenced in this command is preferred over other
configured NTP servers.
Defaults
No peers are configured by default. If a peer is configured, the default NTP version number is 3, no
authentication key is used, and the source IP address is taken from the outgoing interface.
Command Modes
Global configuration
Command History
Release
Modification
10.0
Usage Guidelines
Use this command if you want to allow the system to synchronize with the specified server. The server
will not synchronize to this machine.
When you use the hostname option, the router does a domain name server (DNS) lookup on that name,
and stores the IP address in the configuration. For example, if you enter the command ntp server host1
and then check the running configuration, the output shows ntp server 172.16.0.4, assuming that the
router is correctly configured as a DNS client.
Use the prefer keyword if you use this command multiple times, and you want to set a preferred server.
Using the prefer keyword reduces switching between servers.
If you are using the default version of 3 and NTP synchronization does not occur, try NTP version 2.
Some NTP servers on the Internet run version 2.
When you configure NTP, you must include at least one of the available keywords; the NTP service is
activated and the keyword takes effect.
FR-432
78-11740-02
In the no form of ntp commands, all the keywords are optional. When you enter the no ntp command
followed by one or more of its keywords, only the functions activated by those keywords are removed
from the NTP service. The NTP service itself remains active, along with all functions you have not
specified in the no ntp command.
To terminate NTP service on a device, you must enter the no ntp command without keywords.
For example, if you previously issued the ntp server command and you now want to remove not only
the server synchronization capability, but all NTP functions from the device, use the no ntp command
without any keywords. This ensures that all NTP functions are removed and that the NTP service is also
terminated.
Examples
The following example shows how to configure a router to allow its software clock to be synchronized
with the clock by the device at IP address 172.16.22.44 using NTP version 2:
Router(config)# ntp server 172.16.22.44 version 2
The following example shows how to remove all the configured NTP options and disable the ntp server:
Router(config)# no ntp
Related Commands
Command
Description
ntp authentication-key
ntp peer
ntp source
FR-433
ntp source
To use a particular source address in Network Time Protocol (NTP) packets, use the ntp source
command in global configuration mode. To remove the specified source address, use the no form of this
command.
ntp source type number
no ntp
Syntax Description
type
Type of interface.
number
Defaults
Command Modes
Global configuration
Command History
Release
Modification
10.0
Usage Guidelines
Use this command when you want to use a particular source IP address for all NTP packets. The address
is taken from the named interface. This command is useful if the address on an interface cannot be used
as the destination for reply packets. If the source keyword is present on an ntp server or ntp peer global
configuration command, that value overrides the global value set by this command.
When you configure NTP, you must include at least one of the available keywords; the NTP service is
activated and the keyword takes effect.
In the no form of ntp commands, all the keywords are optional. When you enter the no ntp command
followed by one or more of its keywords, only the functions activated by those keywords are removed
from the NTP service. The NTP service itself remains active, along with all functions you have not
specified in the no ntp command.
To terminate NTP service on a device, you must enter the no ntp command without keywords.
For example, if you previously issued the ntp source command and you now want to remove not only
the configured source address, but all NTP functions from the device, use the no ntp command without
any keywords. This ensures that all NTP functions are removed and that the NTP service is also
terminated.
Examples
The following example shows how to configure a router to use the IP address of Ethernet 0 as the source
address of all outgoing NTP packets:
Router(config)# ntp source ethernet 0
FR-434
78-11740-02
The following example shows how to remove all the configured NTP options and disable the ntp server:
Router(config)# no ntp
Related Commands
Command
Description
ntp peer
ntp server
FR-435
ntp trusted-key
To authenticate the identity of a system to which Network Time Protocol (NTP) will synchronize, use
the ntp trusted-key command in global configuration mode. To disable authentication of the identity of
the system, use the no form of this command.
ntp trusted-key key-number
no ntp
Syntax Description
key-number
Defaults
Disabled
Command Modes
Global configuration
Command History
Release
Modification
10.0
Usage Guidelines
If authentication is enabled, use this command to define one or more key numbers (corresponding to the
keys defined with the ntp authentication-key command) that a peer NTP system must provide in its
NTP packets, in order for this system to synchronize to it. This function provides protection against
accidentally synchronizing the system to a system that is not trusted, because the other system must
know the correct authentication key.
When you configure NTP, you must include at least one of the available keywords; the NTP service is
activated and the keyword takes effect.
In the no form of ntp commands, all the keywords are optional. When you enter the no ntp command
followed by one or more of its keywords, only the functions activated by those keywords are removed
from the NTP service. The NTP service itself remains active, along with all functions you have not
specified in the no ntp command.
To terminate NTP service on a device, you must enter the no ntp command without keywords.
For example, if you previously issued the ntp trusted-key command and you now want to remove not
only the authentication, but all NTP functions from the device, use the no ntp command without any
keywords. This ensures that all NTP functions are removed and that the NTP service is also terminated.
Examples
The following example shows how to configure the system to synchronize only to systems providing
authentication key 42 in its NTP packets:
Router(config)# ntp authenticate
Router(config)# ntp authentication-key 42 md5 aNiceKey
Router(config)# ntp trusted-key 42
FR-436
78-11740-02
The following example shows how to remove all the configured NTP options and disable the ntp server:
Router(config)# no ntp
Related Commands
Command
Description
ntp authenticate
ntp authentication-key
FR-437
ntp update-calendar
To periodically update the hardware clock (calendar) from a Network Time Protocol (NTP) time source,
use the ntp update-calendar command in global configuration mode. To disable the periodic updates,
use the no form of this command.
ntp update-calendar
no ntp
Syntax Description
Defaults
Command Modes
Global configuration
Command History
Release
Modification
10.0
Usage Guidelines
Some platforms have a battery-powered hardware clock, referred to in the command-line interface (CLI)
as the calendar, in addition to the software based system clock. The hardware clock runs continuously,
even if the router is powered off or rebooted.
If the software clock is synchronized to an outside time source via NTP, it is a good practice to
periodically update the hardware clock with the time learned from NTP. Otherwise, the hardware clock
will tend to gradually lose or gain time (drift), and the software clock and hardware clock may become
out of synchronization with each other. The ntp update-calendar command will enable the hardware
clock to be periodically updated with the time specified by the NTP source. The hardware clock will be
updated only if NTP has synchronized to an authoritative time server.
Many lower-end routers (for example, the Cisco 2500 series or the Cisco 2600 series) do not have
hardware clocks, so this command is not available on those platforms.
To force a single update of the hardware clock from the software clock, use the clock update-calendar
EXEC command.
When you configure NTP, you must include at least one of the available keywords; the NTP service is
activated and the keyword takes effect.
In the no form of ntp commands, all the keywords are optional. When you enter the no ntp command
followed by one or more of its keywords, only the functions activated by those keywords are removed
from the NTP service. The NTP service itself remains active, along with all functions you have not
specified in the no ntp command.
To terminate NTP service on a device, you must enter the no ntp command without keywords.
FR-438
78-11740-02
For example, if you previously issued the ntp update-calendar command and you now want to disable
not only the periodic updates, but all NTP functions running on the device, use the no ntp command
without any keywords. This ensures that all NTP functions are removed and that the NTP service is also
terminated.
Examples
The following example shows how to configure the system to periodically update the hardware clock
from the NTP time source:
Router(config)# ntp update-calendar
The following example shows how to remove all the configured NTP options and disable the ntp server:
Router(config)# no ntp
Related Commands
Command
Description
clock read-calendar
Performs a one-time update of the software clock from the hardware clock
(calendar).
clock update-calendar
FR-439
periodic
To specify a recurring (weekly) time range for functions that support the time-range feature, use the
periodic time-range configuration command. To remove the time limitation, use the no form of this
command.
periodic days-of-the-week hh:mm to [days-of-the-week] hh:mm
no periodic days-of-the-week hh:mm to [days-of-the-week] hh:mm
Syntax Description
days-of-the-week The first occurrence of this argument is the starting day or day of the week that the
associated time range is in effect. The second occurrence is the ending day or day
of the week the associated statement is in effect.
This argument can be any single day or combinations of days: Monday, Tuesday,
Wednesday, Thursday, Friday, Saturday, and Sunday. Other possible values
are:
If the ending days of the week are the same as the starting days of the week, they
can be omitted.
hh:mm
The first occurrence of this argument is the starting hours:minutes that the
associated time range is in effect. The second occurrence is the ending
hours:minutes the associated statement is in effect.
The hours:minutes are expressed in a 24-hour clock. For example, 8:00 is
8:00 a.m. and 20:00 is 8:00 p.m.
to
Defaults
Command Modes
Time-range configuration
Command History
Release
Modification
12.0(1)T
Usage Guidelines
For Cisco IOS Release 12.2, IP and Internetwork Packet Exchange (IPX) extended access lists are the
only functions that can use time ranges. For further information on using these functions, refer to the
Release 12.2 Cisco IOS IP Configuration Guide and the Release 12.2 Cisco IOS AppleTalk and Novell
IPX Configuration Guide.
FR-440
78-11740-02
The periodic command is one way to specify when a time range is in effect. Another way is to specify
an absolute time period with the absolute command. Use either of these commands after the time-range
global configuration command, which specifies the name of the time range. Multiple periodic entries
are allowed per time-range command.
If the end days-of-the-week value is the same as the start value, they can be omitted.
If a time-range command has both absolute and periodic values specified, then the periodic items are
evaluated only after the absolute start time is reached, and are not further evaluated after the absolute
end time is reached.
Note
All time specifications are taken as local time. To ensure that the time range entries take effect at the
desired times, you should synchronize the system software clock using Network Time Protocol (NTP).
Table 47 lists some typical settings for your convenience:
Table 47
If you want:
Configure this:
Every day of the week, from 8:00 a.m. to 6:00 p.m. periodic daily 8:00 to 18:00
only
Examples
The following example denies HTTP traffic on Monday through Friday from 8:00 a.m. to 6:00 p.m.:
time-range no-http
periodic weekdays 8:00 to 18:00
!
ip access-list extended strict
deny tcp any any eq http time-range no-http
!
interface ethernet 0
ip access-group strict in
The following example permits Telnet traffic on Mondays, Tuesdays, and Fridays from 9:00 a.m. to
5:00 p.m.:
time-range testing
periodic Monday Tuesday Friday 9:00 to 17:00
!
ip access-list extended legal
permit tcp any any eq telnet time-range testing
!
interface ethernet 0
ip access-group legal in
FR-441
Related Commands
Command
Description
absolute
access-list (extended)
deny (IP)
Sets conditions under which a packet does not pass a named IP access list.
permit (IP)
time-range
FR-442
78-11740-02
process-max-time
To configure the amount of time after which a process should voluntarily yield to another process, use
the process-max-time command in global configuration mode. To reset this value to the system default,
use the no form of this command.
process-max-time milliseconds
no process-max-time [milliseconds]
Syntax Description
milliseconds
Defaults
Command Modes
Global configuration
Command History
Release
Modification
12.1
Usage Guidelines
Lowering the maximum time a process can run is useful in some circumstances to ensure equitable
division of CPU time among different tasks.
Only use this command if recommended to do so by the Cisco Technical Assistance Center (TAC).
Examples
The following example limits the time to 100 milliseconds that a process can run without suspending:
process-max-time 100
FR-443
prompt
To customize the CLI prompt, use the prompt global configuration command. To revert to the default
prompt, use the no form of this command.
prompt string
no prompt [string]
Syntax Description
string
Defaults
The default prompt is either Router or the name defined with the hostname global configuration
command, followed by an angle bracket (>) for user EXEC mode or a pound sign (#) for privileged
EXEC mode.
Command Modes
Global configuration
Command History
Release
Modification
10.3
Usage Guidelines
Text that will be diplayed on screen as the CLI prompt, including any
desired prompt variables.
You can include customized variables when specifying the prompt. All prompt variables are preceded by
a percent sign (%). Table 48 lists the availble prompt variables.
Table 48
Prompt Variable
Interpretation
%h
Host name. This is either Router or the name defined with the
hostname global configuration command.
%n
%p
%s
Space.
%t
Tab.
%%
Issuing the prompt %h command has the same effect as issuing the no prompt command.
FR-444
78-11740-02
Examples
The following example changes the EXEC prompt to include the tty number, followed by the name and
a space:
Router(config)# prompt TTY%n@%h%s%p
The following are examples of user and privileged EXEC prompts that result from the previous
command:
TTY17@Router1 > enable
TTY17@Router1 #
Related Commands
Command
Description
hostname
FR-445
scheduler allocate
To guarantee CPU time for processes, use the scheduler allocate global configuration command on the
Cisco 7200 series and Cisco 7500 series routers. To restore the default, use the no form of this command.
scheduler allocate interrupt-time process-time
no scheduler allocate
Syntax Description
interrupt-time Integer (in microseconds) that limits the maximum number of microseconds to spend
on fast switching within any one network interrupt context. The range is from 400 to
60000 microseconds. The default is 4000 microseconds.
process-time
Defaults
Command Modes
Global configuration
Command History
Release
Modification
11.2
Usage Guidelines
Note
Examples
This command applies to the Cisco 7200 series and Cisco 7500 series routers.
Changing settings associated with CPU processes can negatively impact system performance.
The following example makes 20 percent of the CPU available for process tasks:
Router(config)# scheduler allocate 2000 500
Related Commands
Command
Description
scheduler interval
Controls the maximum amount of time that can elapse without running
system processes.
FR-446
78-11740-02
scheduler interval
To control the maximum amount of time that can elapse without running system processes, use the
scheduler interval global configuration command. To restore the default, use the no form of this
command.
scheduler interval milliseconds
no scheduler interval
Syntax Description
milliseconds
Defaults
Command Modes
Global configuration
Command History
Release
Modification
10.0
Usage Guidelines
Note
Integer that specifies the interval (in milliseconds). The minimum interval that you
can specify is 500 milliseconds; there is no maximum value.
The normal operation of the network server allows the switching operations to use as much of the central
processor as is required. If the network is running unusually heavy loads that do not allow the processor
the time to handle the routing protocols, give priority to the system process scheduler. High-priority
operations are allowed to use as much of the CPU as needed.
Changing settings associated with CPU processes can negatively impact system performance.
On the Cisco 7200 series and Cisco 7500 series, use the scheduler allocate global configuration
command instead of the scheduler interval command.
Examples
The following example changes the low-priority process schedule to an interval of 750 milliseconds:
Router(config)# scheduler interval 750
Related Commands
Command
Description
scheduler allocate
FR-447
service decimal-tty
To specify that line numbers be displayed and interpreted as decimal numbers rather than octal numbers,
use the service decimal-tty global configuration command. To display octal numbers, use the no form
of this command.
service decimal-tty
no service decimal-tty
Syntax Description
Defaults
Command Modes
Global configuration
Command History
Release
Modification
10.0
Examples
The following example displays decimal rather than octal line numbers:
Router(config)# service decimal-tty
FR-448
78-11740-02
service exec-wait
To delay the startup of the EXEC on noisy lines, use the service exec-wait global configuration
command. To disable the delay function, use the no form of this command.
service exec-wait
no service exec-wait
Syntax Description
Defaults
Disabled
Command Modes
Global configuration
Command History
Release
Modification
10.0
Usage Guidelines
This command delays startup of the EXEC until the line has been idle (no traffic seen) for 3 seconds.
The default is to enable the line immediately on modem activation.
This command is useful on noisy modem lines or when a modem attached to the line is configured to
ignore MNP/V.42 negotiations, and MNP/V.42 modems may be dialing in. In these cases, noise or
MNP/V.42 packets may be interpreted as usernames and passwords, causing authentication failure
before the user has a chance to type a username or password. The command is not useful on nonmodem
lines or lines without some kind of login configured.
Examples
FR-449
service finger
The service finger command has been replaced by the ip finger command. However, the service finger
and no service finger commands continue to function to maintain backward compatibility with older
versions of Cisco IOS software. Support for this command may be removed in a future release. See the
description of the ip finger command in this chapter for more information.
FR-450
78-11740-02
service hide-telnet-address
To hide addresses while trying to establish a Telnet session, use the service hide-telnet-address global
configuration command. To remove this service, use the no form of this command.
service hide-telnet-address
no service hide-telnet-address
Syntax Description
Defaults
Command Modes
Global configuration
Command History
Release
Modification
11.2
Usage Guidelines
When you attempt to connect to a device, the router displays addresses and other messages (for example,
Trying router1 (171.69.1.154, 2008)...). With the hide feature, the router suppresses the display of the
address (for example, Trying router1 address #1...). The router continues to display all other messages
that would normally be displayed during a connection attempt, such as detailed error messages if the
connection was not successful.
The hide feature improves the functionality of the busy-message feature. When you configure only the
busy-message command, the normal messages generated during a connection attempt are not displayed;
only the busy-message is displayed. When you use the hide and busy features together you can customize
the information displayed during Telnet connection attempts. When you configure the
service hide-telnet-address command and the busy-message command, the router suppresses the
address and displays the message specified with the busy-message command if the connection attempt
is not successful.
Examples
Related Commands
Command
Description
busy-message
FR-451
service nagle
To enable the Nagle congestion control algorithm, use the service nagle global configuration command.
To to disable the algorithm, use the no form of this command.
service nagle
no service nagle
Syntax Description
Defaults
Disabled
Command Modes
Global configuration
Command History
Release
Modification
10.0
Usage Guidelines
When using a standard TCP implementation to send keystrokes between machines, TCP tends to send
one packet for each keystroke typed. On larger networks, many small packets use up bandwidth and
contribute to congestion.
The algorithm developed by John Nagle (RFC 896) helps alleviate the small-packet problem in TCP. In
general, it works this way: The first character typed after connection establishment is sent in a single
packet, but TCP holds any additional characters typed until the receiver acknowledges the previous
packet. Then the second, larger packet is sent, and additional typed characters are saved until the
acknowledgment comes back. The effect is to accumulate characters into larger chunks, and pace them
out to the network at a rate matching the round-trip time of the given connection. This method is usually
effective for all TCP-based traffic. However, do not use the service nagle command if you have
XRemote users on X Window system sessions.
Examples
FR-452
78-11740-02
Syntax Description
Defaults
Command Modes
Global configuration
Command History
Release
Modification
11.1
Examples
In the following example, the no service prompt config command prevents the configuration prompt
from being displayed. The prompt is still displayed in EXEC mode. When the service prompt config
command is entered, the configuration mode prompt reappears.
Router# configure terminal
Enter configuration commands, one per line.
Router(config)# no service prompt config
hostname newname
end
newname# configure terminal
Enter configuration commands, one per line.
service prompt config
newname(config)# hostname Router
Router(config)# end
Router#
Related Commands
Command
Description
hostname
prompt
FR-453
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
Defaults
Disabled
Command Modes
Global configuration
Command History
Release
Modification
11.1
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
FR-454
78-11740-02
service telnet-zero-idle
To set the TCP window to zero (0) when the Telnet connection is idle, use the service telnet-zero-idle
global configuration command. To disable this service, use the no form of this command.
service telnet-zero-idle
no service telnet-zero-idle
Syntax Description
Defaults
Disabled
Command Modes
Global configuration
Command History
Release
Modification
10.0
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
FR-455
service udp-small-servers
To access minor User Datagram Protocol (UDP) services available from hosts on the network, use the
service udp-small-servers global configuration command. To disable these services, use the no form of
this command.
service udp-small-servers
no service udp-small-servers
Syntax Description
Defaults
Disabled
Command Modes
Global configuration
Command History
Release
Modification
11.2
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 minor UDP services are enabled on the router:
Router(config)# service udp-small-servers
FR-456
78-11740-02
show aliases
To display all alias commands, or the alias commands in a specified mode, use the show aliases EXEC
command.
show aliases [mode]
Syntax Description
mode
Command Modes
EXEC
Command History
Release
Modification
10.3
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
Release 12.2 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
Exec mode aliases:
h
lo
p
r
s
w
Related Commands
help
logout
ping
resume
show
where
Command
Description
alias
FR-457
show buffers
To display statistics for the buffer pools on the network server, use the show buffers EXEC command.
show buffers [address hex-addr |[all | assigned | failures | free | old [dump | header | packet]]
| input-interface interface-type identifier | pool pool-name]
Syntax Description
address
hex-addr
all
assigned
failures
free
old
dump
(Optional) Displays the buffer header and all data in the display.
header
packet
(Optional) Displays the buffer header and packet data in the display.
input-interface
interface-type
identifier
pool
pool-name
Command Modes
EXEC
Command History
Release
Modification
10.0
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:
Router> show buffers
Buffer elements:
398 in free list (500 max allowed)
1266 hits, 0 misses, 0 created
FR-458
78-11740-02
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.
Router> show buffers
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)
FR-459
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.
Router> show buffers
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)
48 hits, 0 fallbacks
16 max cache size, 16 in cache
Field
Description
Buffer elements
free list
max allowed
hits
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.
Small buffers
Middle buffers
Big buffers
VeryBig buffers
Large buffers
Huge buffers
total
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
FR-460
78-11740-02
Table 49
Field
Description
min
max allowed
hits
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
total
permanent
free list
min
max allowed
hits
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.
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.
FR-461
show calendar
To display the current time and date setting for the hardware clock, use the show calendar EXEC
command:
show calendar
Syntax Description
Command Modes
EXEC
Command History
Release
Modification
10.0
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:
Router> show calendar
12:13:44 PST Fri Jul 19 1996
Related Commands
Command
Description
show clock
Displays the time and date from the system software clock.
FR-462
78-11740-02
show clock
To display the time and date from the system software clock, use the show clock EXEC command.
show clock [detail]
Syntax Description
detail
Command Modes
EXEC
Command History
Release
Modification
10.0
Usage Guidelines
(Optional) Indicates the clock source (NTP, VINES, hardware clock, and so on)
and the current summer-time setting (if any).
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:
Note
Examples
Symbol
Description
(blank)
Time is authoritative.
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 Mon Mar 3 1999
Time source is NTP
The following example shows the current clock is authoritative, but NTP is not yet synchronized:
Router> show clock
.16:42:35.597 UTC Wed Nov 1 1999
FR-463
Related Commands
Command
Description
clock set
show calendar
Displays the current time and date setting of the system hardware clock.
FR-464
78-11740-02
show idb
To display information about the status of interface descriptor blocks (IDBs), use the show idb command
in privileged EXEC mode.
show idb
Syntax Description
Defaults
Command Modes
Privileged EXEC
Command History
Release
Modification
12.1
12.2(15)T
Examples
Active
Inactive
Total IDBs
Size each (bytes)
Total bytes
HWIDB#1
HWIDB#2
HWIDB#3
HWIDB#4
HWIDB#5
1
2
3
4
13
2
3
4
5
1
In use 17.
SWIDBs
14
3
17
2576
43792
GigabitEthernet0/0 0 5, HW
GigabitEthernet9/0 0 5, HW
GigabitEthernet9/1 6 5, HW
GigabitEthernet9/2 6 5, HW
Ethernet0 4 5, HW IFINDEX,
IFINDEX,
IFINDEX,
IFINDEX,
IFINDEX,
Ether)
Ether)
Ether)
Ether)
Ether)
Field
Description
In use
Total number of software IDBs (SWIDBs) that have been allocated. This number never
decreases. SWIDBs are never deallocated.
Active
Total number of hardware IDBs (HWIDBs) and SWIDBs that are allocated and in use.
Inactive
Total number of HWIDBs and SWIDBs that are allocated but not in use.
Total
FR-465
Syntax Description
detail
Command Modes
EXEC
Command History
Release
Modification
10.0
Examples
Detailed descriptions of the information displayed by this command can be found in the NTP
specification (RFC 1305).
The following is sample output from the show ntp associations command:
Router> show ntp associations
address
~172.31.32.2
+~192.168.13.33
*~192.168.13.57
* master (synced),
ref clock
st when poll reach delay offset
disp
172.31.32.1
5
29 1024 377
4.2
-8.59
1.6
192.168.1.111
3
69
128 377
4.1
3.48
2.3
192.168.1.111
3
32
128 377
7.9
11.18
3.6
# master (unsynced), + selected, - candidate, ~ configured
Field
Description
address
Address of peer.
ref clock
st
Stratum of peer.
when
poll
FR-466
78-11740-02
Table 51
Field
Description
reach
delay
offset
disp
Dispersion
The following is sample output of the show ntp associations detail command:
Router> show ntp associations detail
172.31.32.2 configured, insane, invalid, stratum 5
ref ID 172.31.32.1, time AFE252C1.6DBDDFF2 (00:12:01.428 PDT Mon Jul 5 1993)
our mode active, peer mode active, our poll intvl 1024, peer poll intvl 64
root delay 137.77 msec, root disp 142.75, reach 376, sync dist 215.363
delay 4.23 msec, offset -8.587 msec, dispersion 1.62
precision 2**19, version 3
org time AFE252E2.3AC0E887 (00:12:34.229 PDT Mon Jul 5 1993)
rcv time AFE252E2.3D7E464D (00:12:34.240 PDT Mon Jul 5 1993)
xmt time AFE25301.6F83E753 (00:13:05.435 PDT Mon Jul 5 1993)
filtdelay =
4.23
4.14
2.41
5.95
2.37
2.33
4.26
4.33
filtoffset =
-8.59
-8.82
-9.91
-8.42 -10.51 -10.77 -10.13 -10.11
filterror =
0.50
1.48
2.46
3.43
4.41
5.39
6.36
7.34
192.168.13.33 configured, selected, sane, valid, stratum 3
ref ID 192.168.1.111, time AFE24F0E.14283000 (23:56:14.078 PDT Sun Jul 4 1993)
our mode client, peer mode server, our poll intvl 128, peer poll intvl 128
root delay 83.72 msec, root disp 217.77, reach 377, sync dist 264.633
delay 4.07 msec, offset 3.483 msec, dispersion 2.33
precision 2**6, version 3
org time AFE252B9.713E9000 (00:11:53.442 PDT Mon Jul 5 1993)
rcv time AFE252B9.7124E14A (00:11:53.441 PDT Mon Jul 5 1993)
xmt time AFE252B9.6F625195 (00:11:53.435 PDT Mon Jul 5 1993)
filtdelay =
6.47
4.07
3.94
3.86
7.31
7.20
9.52
8.71
filtoffset =
3.63
3.48
3.06
2.82
4.51
4.57
4.28
4.59
filterror =
0.00
1.95
3.91
4.88
5.84
6.82
7.80
8.77
192.168.13.57 configured, our_master, sane, valid, stratum 3
ref ID 192.168.1.111, time AFE252DC.1F2B3000 (00:12:28.121 PDT Mon Jul 5 1993)
our mode client, peer mode server, our poll intvl 128, peer poll intvl 128
root delay 125.50 msec, root disp 115.80, reach 377, sync dist 186.157
delay 7.86 msec, offset 11.176 msec, dispersion 3.62
precision 2**6, version 2
org time AFE252DE.77C29000 (00:12:30.467 PDT Mon Jul 5 1993)
rcv time AFE252DE.7B2AE40B (00:12:30.481 PDT Mon Jul 5 1993)
xmt time AFE252DE.6E6D12E4 (00:12:30.431 PDT Mon Jul 5 1993)
filtdelay =
49.21
7.86
8.18
8.80
4.30
4.24
7.58
6.42
filtoffset =
11.30
11.18
11.13
11.28
8.91
9.09
9.27
9.57
filterror =
0.00
1.95
3.91
4.88
5.78
6.76
7.74
8.71
Field
Descriptions
configured
dynamic
FR-467
Table 52
Related Commands
Field
Descriptions
our_master
selected
candidate
sane
insane
valid
invalid
leap_add
leap-sub
unsynced
ref ID
time
our mode
peer mode
root delay
root disp
reach
sync dist
delay
offset
dispersion
precision
version
org time
rcv time
xmt time
filtdelay
filtoffset
filterror
Command
Description
FR-468
78-11740-02
Syntax Description
Command Modes
EXEC
Command History
Release
Modification
10.0
Examples
The following is sample output from the show ntp status command:
Router> show ntp status
Clock is synchronized, stratum 4, reference is 192.168.13.57
nominal freq is 250.0000 Hz, actual freq is 249.9990 Hz, precision is 2**19
reference time is AFE2525E.70597B34 (00:10:22.438 PDT Mon Jul 5 1993)
clock offset is 7.33 msec, root delay is 133.36 msec
root dispersion is 126.28 msec, peer dispersion is 5.98 msec
Field
Description
synchronized
unsynchronized
stratum
reference
nominal freq
actual freq
precision
reference time
clock offset
root delay
root dispersion
peer dispersion
FR-469
Related Commands
Command
Description
FR-470
78-11740-02
show registry
To show the function registry information, use the show registry EXEC command.
show registry [registry-name [registry-num]] [brief | statistics]
Syntax Description
registry-name
registry-num
brief
statistics
Defaults
brief
Command Modes
EXEC
Command History
Release
Modification
11.1
Examples
The following example is sample output of the show registry command using the brief argument:
Switch> show registry atm 3/0/0 brief
Registry objects: 1799
bytes: 213412
FR-471
show sntp
To show information about the Simple Network Time Protocol (SNTP), use the show sntp EXEC
command on a Cisco 1003, Cisco 1004, Cisco 1005, Cisco 1600, Cisco 1720, or Cisco 1750 router.
show sntp
Syntax Description
Command Modes
EXEC
Command History
Release
Modification
11.2
Examples
Stratum
5
4
Version
3
3
Last Receive
00:01:02
00:00:36
Synced
Bcast
Field
Description
SNTP server
Stratum
NTP stratum of the server. The stratum indicates how far away
from an authoritative time source the server is.
Version
Last Receive
Time since the last NTP packet was received from the server.
Synced
Bcast
FR-472
78-11740-02
Related Commands
Command
Description
Configures a Cisco 1003, Cisco 1004, Cisco 1005, Cisco 1600, Cisco 1720,
or Cisco 1750 router to use SNTP to accept NTP traffic from any broadcast
server.
sntp server
Configures a Cisco 1003, Cisco 1004, Cisco 1005, Cisco 1600, Cisco 1720,
or Cisco 1750 router to use SNTP to request and accept NTP traffic from a
time server.
FR-473
Syntax Description
Defaults
The router does not accept SNTP traffic from broadcast servers.
Command Modes
Global configuration
Command History
Release
Modification
11.2
Usage Guidelines
SNTP is a compact, client-only version of the NTP. SNMP can only receive the time from NTP servers;
it cannot be used to provide time services to other systems.
SNTP typically provides time within 100 milliseconds of the accurate time, but it does not provide the
complex filtering and statistical mechanisms of NTP. In addition, SNTP does not authenticate traffic,
although you can configure extended access lists to provide some protection.
You must configure the router with either this command or the sntp server global configuration
command to enable SNTP.
Examples
The following example enables the router to accept broadcast NTP packets and shows sample show sntp
command output:
Router(config)# sntp broadcast client
Router(config)# end
Router#
%SYS-5-CONFIG: Configured from console by console
Router# show sntp
SNTP server
172.21.28.34
Stratum
4
Version
3
Last Receive
00:00:36
Synced
Bcast
FR-474
78-11740-02
Related Commands
Command
Description
show sntp
Displays information about SNTP on a Cisco 1003, Cisco 1004, Cisco 1005,
Cisco 1600, Cisco 1720, or Cisco 1750 router.
sntp server
Configures a Cisco 1003, Cisco 1004, Cisco 1005, Cisco 1600, Cisco 1720,
or Cisco 1750 router to use SNTP to request and accept NTP traffic from a
time server.
FR-475
sntp server
To configure a Cisco 1003, Cisco 1004, Cisco 1005, Cisco 1600, Cisco 1720, Cisco 1750, or Cisco 800
router to use the Simple Network Time Protocol (SNTP) to request and accept Network Time Protocol
(NTP) traffic from a stratum 1 time server, use the sntp server global configuration command. To
remove a server from the list of NTP servers, use the no form of this command.
sntp server {address | hostname} [version number]
no sntp server {address | hostname}
Syntax Description
address
hostname
version number
Defaults
The router does not accept SNTP traffic from a time server.
Command Modes
Global configuration
Command History
Release
Modification
11.2
Usage Guidelines
SNTP is a compact, client-only version of the NTP. SNMP can only receive the time from NTP servers;
it cannot be used to provide time services to other systems.
SNTP typically provides time within 100 milliseconds of the accurate time, but it does not provide the
complex filtering and statistical mechanisms of NTP. In addition, SNTP does not authenticate traffic,
although you can configure extended access lists to provide some protection.
Enter this command once for each NTP server.
You must configure the router with either this command or the sntp broadcast client global
configuration command in order to enable SNTP.
SNTP time servers should operate only at the root (stratum 1) of the subnet, and then only in configurations
where no other source of synchronization other than a reliable radio or modem time service is available. A
stratum 2 server cannot be used as an SNTP time server. The use of SNTP rather than NTP in primary servers
should be carefully considered.
Examples
The following example enables the router to request and accept NTP packets from the server at
172.21.118.9 and displays sample show sntp command output:
Router(config)# sntp server 172.21.118.9
Router(config)# end
Router#
%SYS-5-CONFIG: Configured from console by console
FR-476
78-11740-02
Related Commands
Stratum
5
Version
3
Last Receive
00:01:02
Synced
Command
Description
show sntp
Displays information about SNTP on a Cisco 1003, Cisco 1004, Cisco 1005,
Cisco 1600, Cisco 1720, or Cisco 1750 router.
Configures a Cisco 1003, Cisco 1004, Cisco 1005, Cisco 1600, Cisco 1720,
or Cisco 1750 router to use SNTP to accept NTP traffic from any broadcast
server.
FR-477
time-range
To enable time-range configuration mode and define time ranges for functions (such as extended access
lists), use the time-range global configuration command. To remove the time limitation, use the no form
of this command.
time-range time-range-name
no time-range time-range-name
Syntax Description
time-range-name Desired name for the time range. The name cannot contain a space or quotation
mark, and must begin with a letter.
Defaults
None
Command Modes
Global configuration
Command History
Release
Modification
12.0(1)T
Usage Guidelines
Note
The time-range entries are identified by a name, which is referred to by one or more other configuration
commands. Multiple time ranges can occur in a single access list or other feature.
For Cisco IOS Release 12.2, IP and Internetwork Packet Exchange (IPX) extended access lists are the
only functions that can use time-ranges. For further information on using these functions, see the Release
12.2 Cisco IOS IP Configuration Guide and the Release 12.2 Cisco IOS AppleTalk and Novell IPX
Configuration Guide.
After the time-range command, use the periodic time-range configuration command, the absolute
time-range configuration command, or some combination of them to define when the feature is in effect.
Multiple periodic commands are allowed in a time range; only one absolute command is allowed.
Tip
Examples
To avoid confusion, use different names for time ranges and named access lists.
The following example denies HTTP traffic on Monday through Friday from 8:00 a.m. to 6:00 p.m. The
example allows UDP traffic on Saturday and Sunday from noon to midnight only.
time-range no-http
periodic weekdays 8:00 to 18:00
!
time-range udp-yes
periodic weekend 12:00 to 24:00
FR-478
78-11740-02
!
ip access-list extended strict
deny tcp any any eq http time-range no-http
permit udp any any time-range udp-yes
!
interface ethernet 0
ip access-group strict in
Related Commands
Command
Description
absolute
ip access-list
periodic
Specifies a recurring (weekly) start and end time for a time range.
permit (IP)
FR-479
FR-480
78-11740-02
This chapter describes the commands used to troubleshoot a routing device. To troubleshoot, you need
to discover, isolate, and resolve the system problems. You can discover problems with the system
monitoring commands, isolate problems with the system test commands (including debug commands),
and resolve problems by reconfiguring your system with the suite of Cisco IOS software commands.
This chapter describes general fault management commands. For detailed troubleshooting procedures
and a variety of scenarios, see the Cisco IOS Internetwork Troubleshooting Guide publication. For
complete details on all debug commands, see the Cisco IOS Debug Command Reference.
For troubleshooting tasks and examples, refer to the Troubleshooting and Fault Management chapter
in the Release 12.2 Cisco IOS Configuration Fundamentals Configuration Guide.
For documentation of commands in Cisco IOS Release 12.2T or 12.3 mainline, see the Cisco IOS
Configuration Fundamentals and Network Management Command Reference, Release 12.3.
FR-481
attach
To connect to a specific line card for the purpose of executing monitoring and maintenance commands
on that line card only, use the attach privileged EXEC command. To exit from the Cisco IOS software
image on the line card and return to the Cisco IOS image on the GRP card, use the exit command.
attach slot-number
Syntax Description
slot-number
Defaults
None
Command Modes
Privileged EXEC
CommandHistory
Release
Modification
11.2 GS
This command was added to support the Cisco 12000 series Gigabit Switch
Routers.
Usage Guidelines
Slot number of the line card you want to connect to. Slot numbers range from
0 to 11 for the Cisco 12012 router and 0 to 7 for the Cisco 12008 router. If the
slot number is omitted, you are prompted for the slot number.
You must first use the attach privileged EXEC command to access the Cisco IOS software image on a
line card before using line card-specific show EXEC commands. Alternatively, you can use the
execute-on privileged EXEC command to execute a show command on a specific line card.
After you connect to the Cisco IOS image on the line card using the attach command, the prompt
changes to LC-Slotx#, where x is the slot number of the line card.
The commands executed on the line card use the Cisco IOS image on that line card.
You can also use the execute-on slot privileged EXEC command to execute commands on one or all line
cards.
Note
Examples
Do not execute the config EXEC command from the Cisco IOS software image on the line card.
In the following example, the user connects to the Cisco IOS image running on the line card in slot 9,
gets a list of valid show commands, and returns the Cisco IOS image running on the GRP:
Router# attach 9
Entering Console for 4 Port Packet Over SONET OC-3c/STM-1 in Slot: 9
Type exit to end this session
Press RETURN to get started!
LC-Slot9# show ?
FR-482
78-11740-02
cef
clock
context
history
hosts
ipc
location
sessions
terminal
users
version
LC-Slot9# exit
Disconnecting from slot 9.
Connection Duration: 00:01:04
Router#
Note
Related
Commands
Because not all statistics are maintained on the line cards, the output from some of the show commands
might not be consistent.
Command
Description
attach shelf
execute-on slot
FR-483
clear logging
To clear messages from the logging buffer, use the clear logging privileged EXEC command.
clear logging
Syntax Description
Command Modes
Privileged EXEC
CommandHistory
Release
Modification
11.2
Examples
Related Commands
Command
Description
logging buffered
show logging
FR-484
78-11740-02
diag
To perform field diagnostics on a line card, on the Gigabit Route Processor (GRP), on the Switch Fabric
Cards (SFCs), and on the Clock Scheduler Card (CSC) in Cisco 12000 series Gigabit Switch Routers
(GSRs), use the diag privileged EXEC command. To disable field diagnostics on a line card, use the no
form of this command.
diag slot-number [halt | previous | post | verbose [wait] | wait]
no diag slot-number
Syntax Description
slot-number
Slot number of the line card you want to test. Slot numbers range from 0 to 11
for the Cisco 12012 and 0 to 7 for the Cisco 12008 router. Slot numbers for
the CSC are 16 and 17, and for the FSC are 18, 19, and 20.
halt
previous
(Optional) Displays previous test results (if any) for the line card.
post
verbose [wait]
wait
(Optional) Stops the automatic reloading of the Cisco IOS software on the line
card after the completion of the field diagnostic testing. If you use this
keyword, you must use the microcode reload slot global configuration
command, or manually remove and insert the line card (to power it up) in the
slot so that the GRP will recognize the line card and download the Cisco IOS
software image to the line card.
Defaults
Command Modes
Privileged EXEC
Command History
Release
Modification
11.2 GS
This command was added to support the Cisco 12000 series GSR.
FR-485
Usage Guidelines
The diag command must be executed from the GRP main console port.
Perform diagnostics on the CSC only if a redundant CSC is in the router.
Diagnostics will stop and ask you for confirmation before altering the routers configuration. For
example, running diagnostics on a SFC or CSC will cause the fabric to go from full bandwidth to
one-fourth bandwidth. Bandwidth is not affected by GRP or line card diagnostics.
The field diagnostic software image is bundled with the Cisco IOS software and is downloaded
automatically from the GRP to the target line card prior to testing.
Caution
Performing field diagnostics on a line card stops all activity on the line card. Before the diag EXEC
command begins running diagnostics, you are prompted to confirm the request to perform field
diagnostics on the line card.
In normal mode, if a test fails, the title of the failed test is displayed on the console. However, not all
tests that are performed are displayed. To view all the tests that are performed, use the verbose keyword.
After all diagnostic tests are completed on the line card, a PASSED or TEST FAILURE message is
displayed. If the line card sends a PASSED message, the Cisco IOS software image on the line card is
automatically reloaded unless the wait keyword is specified. If the line card sends a TEST FAILURE
message, the Cisco IOS software image on the line card is not automatically reloaded.
If you want to reload the line card after it fails diagnostic testing, use the microcode reload slot global
configuration command.
Note
When you stop the field diagnostic test, the line card remains down (that is, in an unbooted state). In
most cases, you stopped the testing because you need to remove the line card or replace the line card. If
that is not the case, and you want to bring the line card back up (that is, online), you must use the
microcode reload global configuration command or power cycle the line card.
If the line card fails the test, the line card is defective and should be replaced. In future releases this might
not be the case because DRAM and SDRAM SIMM modules might be field replaceable units. For
example, if the DRAM test failed you might only need to replace the DRAM on the line card.
For more information, refer to the Cisco 12000 series installation and configuration guides.
Examples
In the following example, a user is shown the output when field diagnostics are performed on the line
card in slot 3. After the line card passes all field diagnostic tests, the Cisco IOS software is automatically
reloaded on the card. Before starting the diagnostic tests, you must confirm the request to perform these
tests on the line card because all activity on the line card is halted. The total/indiv. timeout set to 600/220
sec. message indicates that 600 seconds are allowed to perform all field diagnostics tests, and that no
single test should exceed 220 seconds to complete.
Router# diag 3
Running Diags will halt ALL activity on the requested slot. [confirm]
Router#
Launching a Field Diagnostic for slot 3
Running DIAG config check
RUNNING DIAG download to slot 3 (timeout set to 400 sec.)
sending cmd FDIAG-DO ALL to fdiag in slot 3
(total/indiv. timeout set to 600/220 sec.)
Field Diagnostic ****PASSED**** for slot 3
FR-486
78-11740-02
Field Diag eeprom values: run 159 fial mode 0 (PASS) slot 3
last test failed was 0, error code 0
sending SHUTDOWN FDIAG_QUIT to fdiag in slot 3
Board will reload
.
.
.
Router#
In the following example, a user is shown the output when field diagnostics are performed on the line
card in slot 3 in verbose mode:
Router# diag 3 verbose
Running Diags will halt ALL activity on the requested slot. [confirm]
Router#
Launching a Field Diagnostic for slot 3
Running DIAG config check
RUNNING DIAG download to slot 3 (timeout set to 400 sec.)
sending cmd FDIAG-DO ALL to fdiag in slot 3
(total/indiv. timeout set to 600/220 sec.)
FDIAG_STAT_IN_PROGRESS: test #1 R5K Internal Cache
FDIAG_STAT_PASS test_num 1
FDIAG_STAT_IN_PROGRESS: test #2 Sunblock Ordering
FDIAG_STAT_PASS test_num 2
FDIAG_STAT_IN_PROGRESS: test #3 Dram Datapins
FDIAG_STAT_PASS test_num 3
.
.
.
Field Diags: FDIAG_STAT_DONE
Field Diagnostic ****PASSED**** for slot 3
Field Diag eeprom values: run 159 fial mode 0 (PASS) slot 3
last test failed was 0, error code 0
sending SHUTDOWN FDIAG_QUIT to fdiag in slot 3
Board will reload
.
.
.
Router#
FR-487
Related Commands
Command
Description
microcode reload
Reloads the Cisco IOS image on a line card on the Cisco 7000 series with
RSP7000, Cisco 7500 series, or Cisco 12000 series routers after all
microcode configuration commands have been entered.
FR-488
78-11740-02
exception core-file
To specify the name of the core dump file, use the exception core-file global configuration command.
To return to the default core filename, use the no form of this command.
exception core-file file-name
no exception core-file
Syntax Description
file-name
Defaults
The core file is named hostname-core, where hostname is the name of the router.
Command Modes
CommandHistory
Release
Modification
10.2
Usage Guidelines
Caution
Use the exception commands only under the direction of a technical support representative. Creating a
core dump while the router is functioning in a network can disrupt network operation. The resulting
binary file, which is very large, must be transferred to a TFTP, File Transfer Protocol (FTP), or remote
copy protocol (rcp) server and subsequently interpreted by technical personnel that have access to source
code and detailed memory maps.
If you use TFTP to dump the core file to a server, the router will only dump the first 16 MB of the core
file. If the routers memory is larger than 16 MB, the whole core file will not be copied to the server.
Therefore, use rcp or FTP to dump the core file.
Examples
In the following example, a user configures a router to use FTP to dump a core file named dumpfile to
the FTP server at 172.17.92.2 when it crashes:
ip ftp username red
ip ftp password blue
exception protocol ftp
exception dump 172.17.92.2
exception core-file dumpfile
FR-489
Related
Commands
Command
Description
exception dump
Causes the router to dump a core file to a particular server when the router
crashes.
exception memory
Causes the router to create a core dump and reboot when certain memory size
parameters are violated.
exception
spurious-interrupt
Causes the router to create a core dump and reload after a specified number
of spurious interrupts.
exception protocol
ip ftp password
ip ftp username
FR-490
78-11740-02
exception dump
To configure the router to dump a core file to a particular server when the router crashes, use the
exception dump global configuration command. To disable core dumps, use the no form of this
command.
exception dump ip-address
no exception dump
Syntax Description
ip-address
Defaults
Disabled
Command Modes
Command History
Release
Modification
10.3
Usage Guidelines
Caution
Use the exception commands only under the direction of a technical support representative. Creating a
core dump while the router is functioning in a network can disrupt network operation. The resulting
binary file, which is very large, must be transferred to a TFTP, File Transfer Protocol (FTP), or remote
copy protocol (rcp) server and subsequently interpreted by technical personnel that have access to source
code and detailed memory maps.
If you use TFTP to dump the core file to a server, the router will only dump the first 16 MB of the core
file. If the routers memory is larger than 16 MB, the whole core file will not be copied to the server.
Therefore, use rcp or FTP to dump the core file.
The core dump is written to a file named hostname-core on your server, where hostname is the name of
the router. You can change the name of the core file by configuring the exception core-file command.
This procedure can fail for certain types of system crashes. However, if successful, the core dump file
will be the size of the memory available on the processor (for example, 16 MB for a CSC/4).
Examples
In the following example, a user configures a router to use FTP to dump a core file to the FTP server at
172.17.92.2 when it crashes:
ip ftp username red
ip ftp password blue
exception protocol ftp
exception dump 172.17.92.2
FR-491
Related Commands
Command
Description
exception core-file
exception memory
Causes the router to create a core dump and reboot when certain memory size
parameters are violated.
exception
spurious-interrupt
Causes the router to create a core dump and reload after a specified number
of spurious interrupts.
exception protocol
ip ftp password
ip ftp username
ip rcmd
remote-username
FR-492
78-11740-02
exception linecard
To enable storing of crash information for a line card and optionally specify the type and amount of
information stored, use the exception linecard global configuration command. To disable the storing of
crash information for the line card, use the no form of this command.
exception linecard {all | slot slot-number} [corefile filename | main-memory size [k | m] |
queue-ram size [k | m] | rx-buffer size [k | m] | sqe-register-rx | sqe-register-tx | tx-buffer
size [k | m]]
no exception linecard
Syntax Description
all
Stores crash information for the line card in the specified slot. Slot numbers
range from 0 to 11 for the Cisco 12012 and 0 to 7 for the Cisco 12008 router.
corefile filename
(Optional) Stores the crash information in the specified file in NVRAM. The
default filename is hostname-core-slot-number (for example, c12012-core-8).
main-memory size
(Optional) Stores the crash information for the main memory on the line card
and specifies the size of the crash information. Size of the memory to store is
0 to 268435456.
queue-ram size
(Optional) Stores the crash information for the queue RAM memory on the
line card and specifies the size of the crash information. Size of the memory
to store can be from 0 to 1048576.
rx-buffer size
(Optional) Stores the crash information for the receive and transmit buffer on
the line card and specifies the size of the crash information. Size of the
memory to store can be from 0 to 67108864.
tx-buffer size
sqe-register-rx
sqe-register-tx
k
m
Defaults
Command Modes
Command History
Release
Modification
11.2 GS
FR-493
Usage Guidelines
This command is currently supported only on Cisco 12000 series Gigabit Switch Routers (GSRs).
Use the exception linecard global configuration command only when directed by a technical support
representative. Only enable options that the technical support representative requests you to enable.
Technical support representatives need to be able to look at the crash information from the line card to
troubleshoot serious problems on the line card. The crash information contains all the line card memory
information including the main memory and transmit and receive buffer information.
Caution
Examples
Use caution when enabling the exception linecard global configuration command. Enabling all options
could cause a large amount (150 to 250 MB) of crash information to be sent to the server.
In the following example, the user enables the storing of crash information for line card 8. By default,
256 MB of main memory is stored.
12000(config)# exception linecard slot 8
FR-494
78-11740-02
exception memory
To cause the router to create a core dump and reboot when certain memory size parameters are violated,
use the exception memory global configuration command. To disable the rebooting and core dump, use
the no form of this command.
exception memory {fragment size | minimum size}
no exception memory {fragment | minimum}
Syntax Description
fragment size
minimum size
Defaults
Disabled
Command Modes
CommandHistory
Release
Modification
10.3
Usage Guidelines
Caution
Use the exception commands only under the direction of a technical support representative. Creating a
core dump while the router is functioning in a network can disrupt network operation. The resulting
binary file, which is very large, must be transferred to a TFTP, File Transfer Protocol (FTP), or remote
copy protocol (rcp) server and subsequently interpreted by technical personnel that have access to source
code and detailed memory maps.
This command is useful to troubleshoot memory leaks.
The size is checked every 60 seconds. If you enter a size that is greater than the free memory, a core
dump and router reload is generated after 60 seconds.
The exception dump command must be configured in order to generate a core dump file. If the
exception dump command is not configured, the router reloads without generating a core dump.
Examples
In the following example, the user configures the router to monitor the free memory. If the amount of
free memory falls below 250,000 bytes, the router will dump the core file and reload.
exception dump 131.108.92.2
exception core-file memory.overrun
exception memory minimum 250000
FR-495
Related Commands
Command
Description
exception core-file
exception dump
Configures the router to dump a core file to a particular server when the
router crashes.
exception protocol
exception region-size
Specifies the size of the region for the exception-time memory pool.
ip ftp password
ip ftp username
FR-496
78-11740-02
exception protocol
To configure the protocol used for core dumps, use the exception protocol global configuration
command. To configure the router to use the default protocol, use the no form of this command.
exception protocol {ftp | rcp | tftp}
no exception protocol
Syntax Description
ftp
rcp
tftp
Defaults
TFTP
Command Modes
CommandHistory
Release
Modification
10.3
Usage Guidelines
Caution
Use the exception commands only under the direction of a technical support representative. Creating a
core dump while the router is functioning in a network can disrupt network operation. The resulting
binary file, which is very large, must be transferred to a TFTP, File Transfer Protocol (FTP), or remote
copy protocol (rcp) server and subsequently interpreted by technical personnel that have access to source
code and detailed memory maps.
If you use TFTP to dump the core file to a server, the router will only dump the first 16 MB of the core
file. If the routers memory is larger than 16 MB, the whole core file will not be copied to the server.
Therefore, use rcp or FTP to dump the core file.
Examples
In the following example, the user configures a router to use FTP to dump a core file to the FTP server
at 172.17.92.2 when it crashes:
ip ftp username red
ip ftp password blue
exception protocol ftp
exception dump 172.17.92.2
FR-497
Related
Commands
Command
Description
exception core-file
exception dump
Causes the router to dump a core file to a particular server when the router
crashes.
exception memory
Causes the router to create a core dump and reboot when certain memory size
parameters are violated.
exception
spurious-interrupt
Causes the router to create a core dump and reload after a specified number
of spurious interrupts.
ip ftp password
ip ftp username
FR-498
78-11740-02
exception region-size
To specify the size of the region for the exception-time memory pool, use the exception region-size global
configuration command. To use the default region size, use the no form of this command.
exception region-size size
no exception region-size
Syntax Description
size
Defaults
16,384 bytes
Command Modes
CommandHistory
Release
Modification
10.3
Usage Guidelines
Caution
Use the exception commands only under the direction of a technical support representative. Creating a
core dump while the router is functioning in a network can disrupt network operation. The resulting
binary file, which is very large, must be transferred to a TFTP, File Transfer Protocol (FTP), or remote
copy protocol (rcp) server and subsequently interpreted by technical personnel that have access to source
code and detailed memory maps.
The exception region-size command is used to define a small amount of memory to serve as a fallback
pool when the processor memory pool is marked corrupt. The exception memory command must be
used to allocate memory to perform a core dump.
Examples
Related
Commands
Command
Description
exception core-file
exception dump
Configures the router to dump a core file to a particular server when the
router crashes.
FR-499
Command
Description
exception memory
Causes the router to create a core dump and reboot when certain memory size
parameters are violated.
exception protocol
ip ftp password
ip ftp username
FR-500
78-11740-02
exception spurious-interrupt
To configure the router to create a core dump and reload after a specified number of spurious interrupts,
use the exception spurious-interrupt command global configuration command. To disable the core
dump and reload, use the no form of this command.
exception spurious-interrupt [number]
no exception spurious-interrupt
Syntax Description
number
Defaults
Disabled
Command Modes
CommandHistory
Release
Modification
10.3
Usage Guidelines
Caution
Use the exception commands only under the direction of a technical support representative. Creating a
core dump while the router is functioning in a network can disrupt network operation. The resulting
binary file, which is very large, must be transferred to a TFTP, File Transfer Protocol (FTP), or remote
copy protocol (rcp) server and subsequently interpreted by technical personnel that have access to source
code and detailed memory maps.
If you use TFTP to dump the core dump file to a server, the router will only dump the first 16 MB of the
file. If the routers memory is larger than 16 MB, the whole core file will not be copied to the server.
Therefore, use rcp or FTP to dump the core file.
Examples
In the following example, the user configures a router to create a core dump with a limit of two spurious
interrupts:
Router# exception spurious-interrupt 2
FR-501
Related Commands
Command
Description
exception core-file
ip ftp password
ip ftp username
FR-502
78-11740-02
execute-on
To execute commands on a line card, use the execute-on privileged EXEC command.
execute-on {slot slot-number | all | master} command
Syntax Description
slot slot-number
Executes the command on the line card in the specified slot. Slot numbers can
be chosen from the following ranges:
all
master
command
Command Modes
Privileged EXEC
Command History
Release
Modification
11.2 GS
This command was introduced to support Cisco 12000 series Gigabit Switch
Routers.
11.3(2)AA
Support for this command was added to the Cisco AS5800 universal access
server.
Usage Guidelines
Use this command to execute a command on one or all line cards to monitor and maintain information
on one or more line cards (for example, a line card in a specified slot on a dial shelf). This allows you to
issue commands remotely; that is, to issue commands without needing to log in to the line card directly.
The all form of the command allows you to issue commands to all the line cards without having to log
in to each in turn.
Though this command does not have a no form, note that it is possible to use the no form of the remotely
executed commands used in this command.
Tip
This command is useful when used with show EXEC commands (such as show version), because you
can verify and troubleshoot the features found only on a specific line card. Please note, however, that
because not all statistics are maintained on the line cards, the output from some of the show commands
might not be consistent.
Cisco 12000 GSR Guidelines and Restrictions
You can use the execute-on privileged EXEC command only from Cisco IOS software running on the
GRP card.
FR-503
Timesaver
Though you can use the attach privileged EXEC command to execute commands on a specific line card,
using the execute-on slot command saves you some steps. For example, first you must use the attach
command to connect to the Cisco IOS software running on the line card. Next you must issue the
command. Finally you must disconnect from the line card to return to the Cisco IOS software running
on the GRP card. With the execute-on slot command, you can perform three steps with one command.
In addition, the execute-on all command allows you to perform the same command on all line cards
simultaneously.
Cisco AS5800 Guidelines and Restrictions
The purpose of the command is to conveniently enable certain commands to be remotely executed on the
dial shelf cards from the router without connecting to each line card. This is the recommended
procedure, because it avoids the possibility of adversely affecting a good configuration of a line card in
the process. The execute-on command does not give access to every Cisco IOS command available on
the Cisco AS5800 access server. In general, the purpose of the execute-on command is to provide access
to statistical reports from line cards without directly connecting to the dial shelf line cards.
Warning
Do not use this command to change configurations on dial shelf cards, because such changes will not
be reflected in the router shelf.
Using this command makes it possible to accumulate inputs for inclusion in the show tech-support
command.
The master form of the command can run a designated command remotely on the router from the DSC
card. However, using the console on the DSC is not recommended. It is used for technical support
troubleshooting only.
The show tech-support command for each dial shelf card is bundled into the router shelf's show
tech-support command via the execute-on facility.
The execute-on command also support interactive commands such as the following:
router: execute-on slave slot slot ping
The execute-on command has the same limitations and restrictions as a vty telnet client has; that is, it
cannot reload DSC using the following command:
router: execute-on slave slot slot reload
You can use the execute-on command to enable remote execution of the commands included in the
following partial list:
show context
show diag
show environment
show dsi
show dsip
show tech-support
FR-504
78-11740-02
Examples
In the following example, the user executes the show controllers command on the line card in slot 4 of
a Cisco 12000 series GSR:
Router# execute-on slot 4 show controllers
========= Line Card (Slot 4) =======
Interface POS0
Hardware is BFLC POS
lcpos_instance struct
6033A6E0
RX POS ASIC addr space 12000000
TX POS ASIC addr space 12000100
SUNI framer addr space 12000400
SUNI rsop intr status
00
CRC16 enabled, HDLC enc, int clock
no loop
Interface POS1
Hardware is BFLC POS
lcpos_instance struct
6033CEC0
RX POS ASIC addr space 12000000
TX POS ASIC addr space 12000100
SUNI framer addr space 12000600
SUNI rsop intr status
00
CRC32 enabled, HDLC enc, int clock
no loop
Interface POS2
Hardware is BFLC POS
lcpos_instance struct
6033F6A0
RX POS ASIC addr space 12000000
TX POS ASIC addr space 12000100
SUNI framer addr space 12000800
SUNI rsop intr status
00
CRC32 enabled, HDLC enc, int clock
no loop
Interface POS3
Hardware is BFLC POS
lcpos_instance struct
60341E80
RX POS ASIC addr space 12000000
TX POS ASIC addr space 12000100
SUNI framer addr space 12000A00
SUNI rsop intr status
00
CRC32 enabled, HDLC enc, ext clock
no loop
Router#
Related Commands
Command
Description
attach
Connects you to a specific line card for the purpose of executing commands
using the Cisco IOS software image on that line card.
FR-505
logging
To log messages to a syslog server host, use the logging global configuration command. To delete the
syslog server with the specified address from the list of syslogs, use the no form of this command.
logging host-name
no logging host-name
Syntax Description
host-name
Defaults
Command Modes
CommandHistory
Release
Modification
10.0
Usage Guidelines
This command identifies a syslog server host to receive logging messages. By issuing this command
more than once, you build a list of syslog servers that receive logging messages.
Examples
Related
Commands
Command
Description
logging trap
Limits messages logged to the syslog servers based on severity and limits the
logging of system messages sent to syslog servers to only those messages at
the specified level.
FR-506
78-11740-02
logging buffered
To limit messages logged to an internal buffer based on severity, use the logging buffered global
configuration command. To cancel the use of the buffer, use the no form of this command. The default
form of this command returns the buffer size to the default size.
logging buffered [buffer-size | level]
no logging buffered
default logging buffered
Syntax Description
buffer-size
(Optional) Size of the buffer from 4096 to 4,294,967,295 bytes. The default size
varies by platform.
level
(Optional) Limits the logging of messages to the buffer to a specified level. You can
enter the level name or level number. See Table 55 for a list of the accepatable level
name or level number keywords.
Defaults
For most platforms, the Cisco IOS software logs messages to the internal buffer.
Command Modes
Command History
Release
Modification
10.0
11.1(17)T
Usage Guidelines
This command copies logging messages to an internal buffer. The buffer is circular in nature, so newer
messages overwrite older messages after the buffer is filled.
Specifying a level causes messages at that level and numerically lower levels to be logged in an internal
buffer. See Table 55 for a list of level arguments.
Do not make the buffer size too large because the router could run out of memory for other tasks. You
can use the show memory EXEC command to view the free processor memory on the router; however,
this is the maximum available and should not be approached. The default logging buffered command
resets the buffer size to the default for the platform.
To display the messages that are logged in the buffer, use the show logging EXEC command. The first
message displayed is the oldest message in the buffer.
The show logging EXEC command displays the addresses and levels associated with the current logging
setup, and any other logging statistics.
FR-507
Table 55
Examples
Level Name
Level
Number Description
Syslog Definition
emergencies
System unusable
LOG_EMERG
alerts
LOG_ALERT
critical
Critical conditions
LOG_CRIT
errors
Error conditions
LOG_ERR
warnings
Warning conditions
LOG_WARNING
notifications
LOG_NOTICE
informational
LOG_INFO
debugging
Debugging messages
LOG_DEBUG
Related Commands
Command
Description
clear logging
show logging
FR-508
78-11740-02
logging console
To limit messages logged to the console based on severity, use the logging console global configuration
command. To disable logging to the console terminal, use the no form of this command.
logging console level
no logging console
Syntax Description
level
Defaults
debugging
Command Modes
Command History
Release
Modification
10.0
Usage Guidelines
Specifying a level causes messages at that level and numerically lower levels to be displayed at the
console terminal.
The show logging EXEC command displays the addresses and levels associated with the current logging
setup, and any other logging statistics. See Table 56.
Table 56
Level Arguments
Level
Description
Syslog Definition
emergencies
System unusable
LOG_EMERG
alerts
LOG_ALERT
critical
Critical conditions
LOG_CRIT
errors
Error conditions
LOG_ERR
warnings
Warning conditions
LOG_WARNING
notifications
LOG_NOTICE
informational
LOG_INFO
debugging
Debugging messages
LOG_DEBUG
The effect of the log keyword with the IP access list (extended) interface configuration command
depends on the setting of the logging console command. The log keyword takes effect only if the logging
console level is set to 6 or 7. If you change the default to a level lower than 6 and specify the log keyword
with the IP access list (extended) command, no information is logged or displayed.
FR-509
Examples
In the following example, the user changes the level of messages displayed to the console terminal to
alerts, which means alerts and emergencies are displayed:
logging console alerts
Related Commands
Command
Description
access-list (extended)
logging facility
FR-510
78-11740-02
logging facility
To configure the syslog facility in which system messages are sent, use the logging facility global
configuration command. To revert to the default of local7, use the no form of this command.
logging facility facility-type
no logging facility
Syntax Description
facility-type
Defaults
local7
Command Modes
Command History
Release
Modification
10.0
Usage Guidelines
Syslog facility. See the Usage Guidelines section of this command reference
entry for descriptions of acceptable keywords.
Facility-type keyword
Description
auth
Authorization system
cron
Cron facility
daemon
System daemon
kern
Kernel
local07
lpr
Mail system
news
USENET news
sys9
System use
sys10
System use
sys11
System use
sys12
System use
sys13
System use
sys14
System use
syslog
System log
FR-511
Table 57
Examples
Facility-type keyword
Description
user
User process
uucp
In the following example, the user configures the syslog facility to the kernel facility type:
logging facility kern
Related Commands
Command
Description
logging console
FR-512
78-11740-02
logging history
To limit syslog messages sent to the routers history table and the Simple Network Management Protocol
(SNMP) network management station based on severity, use the logging history global configuration
command. To return the logging of syslog messages to the default level, use the no form of this command
with the previously configured severity level argument.
logging history [severity-level-name | severity-level-number]
no logging history [severity-level-name | severity-level-number]
Syntax Description
severity-level-name
Name of the severity level. Specifies the lowest severity level for system
error messag logging. See the Usage Guidelines section of this command for
available keywords.
severity-level-number
Number of the severity level. Specifies the lowest severity level for system
error messag logging. See the Usage Guidelines section of this command for
available keywords.
Defaults
Logging of system messages of severity levels 0 through 4 (emergency, alert, critical, error, and warning
levels); in other words, saving level warnings or higher
Command Modes
Command History
Release
Modification
11.2
Usage Guidelines
Sending syslog messages to the SNMP network management station occurs when you enable syslog
traps with the snmp-server enable traps global configuration command. Because SNMP traps are
inherently unreliable and much too important to lose, at least one syslog message, the most recent
message, is stored in a history table on the router. The history table, which contains table size, message
status, and message text data, can be viewed using the show logging history command. The number of
messages stored in the table is governed by the logging history size EXEC command.
Severity levels are numbered 0 through 7, with 0 being the highest severity level and 7 being the lowest
severity level (that is, the lower the number, the more critical the message). Specifying a level causes
messages at that severity level and numerically lower levels to be stored in the routers history table and
sent to the SNMP network management station. For example, specifying the level critical causes
messages as the critical (3), alert (2), and emergency (1) levles to be saved to the logging history table.
Table 58 provides a description of logging severity levels, listed from higest severity to lowest severity,
and the arguments used inthe logging history command syntax. Note that you can use the level name or
the level number as the level argument in this command.
FR-513
Table 58
Examples
Severity Level
Name
Severity
Level
Number
Description
Syslog Definition
emergencies
System unusable
LOG_EMERG
alerts
LOG_ALERT
critical
Critical conditions
LOG_CRIT
errors
Error conditions
LOG_ERR
warnings
Warning conditions
LOG_WARNING
notifications
LOG_NOTICE
informational
LOG_INFO
debugging
Debugging messages
LOG_DEBUG
In the following example, the system is initially configured to the default of saving severity level 4 or
higher. The logging history1 command is used to configure the system to save only level 1 (alert) and
level 0 (emergency) messages to the logging history table. The configuration is then confirmed using the
show logging history command.
Router#show logging history
Syslog History Table:10 maximum table entries,
! The following line shows that system-error-message-logging is set to the
! default level of warnings (4).
saving level warnings or higher
23 messages ignored, 0 dropped, 0 recursion drops
1 table entries flushed
SNMP notifications not enabled
entry number 2 : LINK-3-UPDOWN
Interface FastEthernet0, changed state to up
timestamp: 2766
Router#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)#logging history 1
Router(config)#end
Router#
4w0d: %SYS-5-CONFIG_I: Configured from console by console
Router#show logging history
Syslog History Table:1 maximum table entries,
! The following line indicates that logging history level 1 is configured.
saving level alerts or higher
18 messages ignored, 0 dropped, 0 recursion drops
1 table entries flushed
SNMP notifications not enabled
entry number 2 : LINK-3-UPDOWN
Interface FastEthernet0, changed state to up
timestamp: 2766
Router#
FR-514
78-11740-02
Related Commands
Command
Description
logging on
Changes the number of syslog messages stored in the routers history table.
show logging
snmp-server host
FR-515
Syntax Description
number
Defaults
One message
Command Modes
Command History
Release
Modification
11.2
Number from 1 to 500 that indicates the maximum number of messages stored
in the history table.
Usage Guidelines
When the history table is full (that is, it contains the maximum number of message entries specified with
the logging history size command), the oldest message entry is deleted from the table to allow the new
message entry to be stored.
Examples
In the following example, the user sets the number of messages stored in the history table to 20:
logging history size 20
Related Commands
Command
Description
logging history
Limits syslog messages sent to the routers history table and the SNMP
network management station based on severity.
show logging
FR-516
78-11740-02
logging linecard
To log messages to an internal buffer on a line card, use the logging linecard global configuration
command. To cancel the use of the internal buffer on the line cards, use the no form of this command.
logging linecard [size | level]
no logging linecard
Syntax Description
size
(Optional) Size of the buffer used for each line card. The range is from 4096 to
65,536 bytes. The default is 8 KB.
level
criticalCritical conditions
debuggingDebugging messages
emergenciesSystem is unusable
errorsError conditions
informationalInformational messages
warningsWarning conditions
Defaults
The Cisco IOS software logs messages to the internal buffer on the GRP card.
Command Modes
Command History
Release
Modification
11.2 GS
This command was added to support the Cisco 12000 series Gigabit Switch
Routers.
Usage Guidelines
Specifying a message level causes messages at that level and numerically lower levels to be stored in the
internal buffer on the line cards.
Table 59 lists the message levels and associated numerical level. For example, if you specify a message
level of critical, all critical, alert, and emergency messages will be logged.
FR-517
Table 59
Message Levels
Level Keyword
Level
emergencies
alerts
critical
errors
warnings
notifications
informational
debugging
To display the messages that are logged in the buffer, use the show logging slot EXEC command. The
first message displayed is the oldest message in the buffer.
Do not make the buffer size too large because the router could run out of memory for other tasks. You
can use the show memory EXEC command to view the free processor memory on the router; however,
this is the maximum available and should not be approached.
Examples
The following example enables logging to an internal buffer on the line cards using the default buffer
size and logging warning, error, critical, alert, and emergency messages:
(config)# logging linecard warnings
Related Commands
Command
Description
clear logging
show logging
FR-518
78-11740-02
logging monitor
To limit messages logged to the terminal lines (monitors) based on severity, use the logging monitor
global configuration command. This command limits the logging messages displayed on terminal lines
other than the console line to messages with a level at or above the level argument. To disable logging
to terminal lines other than the console line, use the no form of this command.
logging monitor severity-level
no logging monitor
Syntax Description
severity-level
Defaults
debugging (severity-level 7)
Command Modes
Command History
Release
Modification
10.0
Usage Guidelines
Specifying a level causes messages at that level and numerically lower levels to be displayed to the
monitor.
Table 60
Examples
Level Name
Level
Number Description
Syslog Definition
emergencies
System unusable
LOG_EMERG
alerts
LOG_ALERT
critical
Critical conditions
LOG_CRIT
errors
Error conditions
LOG_ERR
warnings
Warning conditions
LOG_WARNING
notifications
LOG_NOTICE
informational
LOG_INFO
debugging
Debugging messages
LOG_DEBUG
In the following example, the user specifies that only messages of the levels errors, critical, alerts, and
emergencies be displayed on terminals:
FR-519
logging monitor 3
Related Commands
Command
Description
terminal monitor
FR-520
78-11740-02
logging on
To control logging of system messages (including error messages or debugging messages), use the
logging on global configuration command. This command sends system messages to a logging process,
which logs messages to designated locations asynchronously to the processes that generated the
messages. To disable the logging process, use the no form of this command.
logging on
no logging on
Syntax Description
Defaults
The Cisco IOS software sends messages to the asynchronous logging process.
Command Modes
Command History
Release
Modification
10.0
Usage Guidelines
The logging process controls the distribution of logging messages to the various destinations, such as
the logging buffer, terminal lines, or syslog server. You can turn logging on and off for these destinations
individually using the logging buffered, logging monitor, and logging global configuration commands.
However, if the logging on command is disabled, no messages will be sent to these destinations. Only
the console will receive messages.
Additionally, the logging process logs messages to the console and the various destinations after the
processes that generated them have completed. When the logging process is disabled, messages are
displayed on the console as soon as they are produced, often appearing in the middle of command output.
Caution
Disabling the logging on command will substantially slow down the router. Any process generating
system messages will wait until the messages have been displayed on the console before continuing.
The logging synchronous line configuration command also affects the displaying of messages to the
console. When the logging synchronous command is enabled, messages will appear only after the user
types a carriage return.
Examples
The following example shows command output and message output when logging is enabled. The ping
process finishes before any of the logging information is printed to the console (or any other destination).
Router(config)# logging on
Router(config)# end
Router#
%SYS-5-CONFIG_I: Configured from console by console
FR-521
In the following example, logging is disabled. The message output is displayed as messages are
generated, causing the debug messages to be interspersed with the message Type escape sequence to
abort.
Router(config)# no logging on
Router(config)# end
%SYS-5-CONFIG_I: Configured from console by console
Router#
Router# ping dirt
IP: s=172.21.96.41 (local), d=172.16.1.129 (Ethernet1/0), len 100, sendingTyp
IP: s=171.69.1.129 (Ethernet1/0), d=172.21.96.41, len 114, rcvd 1e
IP: s=172.21.96.41 (local), d=172.16.1.129 (Ethernet1/0), len 100, sending esc
IP: s=171.69.1.129 (Ethernet1/0), d=172.21.96.41, len 114, rcvd 1
IP: s=172.21.96.41 (local), d=172.16.1.129 (Ethernet1/0), len 100, sendingape
IP: s=171.69.1.129 (Ethernet1/0), d=172.21.96.41, len 114, rcvd 1
IP: s=172.21.96.41 (local), d=172.16.1.129 (Ethernet1/0), len 100, sendingse
IP: s=171.69.1.129 (Ethernet1/0), d=172.21.96.41, len 114, rcvd 1
IP: s=172.21.96.41 (local), d=172.16.1.129 (Ethernet1/0), len 100, sendingquen
IP: s=171.69.1.129 (Ethernet1/0), d=172.21.96.41, len 114, rcvd 1ce to abort.
Sending 5, 100-byte ICMP Echos to 172.16.1.129, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 152/152/156 ms
Router#
Related
Commands
Command
Description
logging
logging buffered
logging monitor
logging synchronous
FR-522
78-11740-02
logging rate-limit
To limit the rate of messages logged per second, use the logging rate-limit command in global
configuration mode. To disable the limit, use the no form of this command.
logging rate-limit {number | all number | console {number | all number}} [except severity]
no logging rate-limit
Syntax Description
number
Maximum number of messages logged per second. The valid values are
from 1 to 10000.
all
Sets the rate limit for all error and debug messages displayed at the console
and printer.
console
Sets the rate limit for error and debug messages displayed at the console.
except
severity
(Optional) Sets the logging severity level. The valid levels are from 0 to 7.
Command Default
The default for this command is 10 messages logged per second and exclusion of messages of the errors
level or lower.
Command Modes
Global configuration
Command History
Release
Modification
12.1(3)T
12.2
Usage Guidelines
12.3
12.3T
12.4
12.4T
The logging rate-limit command controls the output of messages from the system. Use this command
if you want to avoid a flood of output messages. You can select the severity of the output messages and
output rate by using the logging rate-limit command. You can use the logging rate-limit command
anytime; it will not negatively impact the performance of your system and may improve the system
performance by specifying the severities and rates of output messages.
FR-523
You can use this command with or without the logging synchronous line configuration command. For
example, if you want to see all severity 0, 1, and 2 messages, use the no logging synchronous command
and specify logging rate-limit 10 except 2. By using the two commands together, you cause all
messages of 0, 1, and 2 severity to print and limit the less severe ones (lower than 2) to only 10 per
second.
Table 61 compares the error message logging numeric severity level with its equivalent word
description.
Table 61
Examples
Equivalent Word
Description
emergencies
System unusable
alerts
critical
Critical conditions
errors
Error conditions
warnings
Warning conditions
notifications
informational
debugging
Debugging messages
In the following example, the logging rate-limit configuration mode command limits message output to
200 per second:
Router(config)# logging rate-limit 200
Related Commands
Command
Description
logging synchronous
FR-524
78-11740-02
logging source-interface
To specify the source IP address of syslog packets, use the logging source-interface global
configuration command. To remove the source designation, use the no form of this command.
logging source-interface interface-type interface-number
no logging source-interface
Syntax Description
interface-type
Interface type.
interface-number
Interface number.
Defaults
No interface is specified.
Command Modes
Command History
Release
Modification
11.2
Normally, a syslog message contains the IP address of the interface it uses to leave the router. The
logging source-interface command specifies that syslog packets contain the IP address of a particular
interface, regardless of which interface the packet uses to exit the router.
Examples
In the following example, the user specifies that the IP address for Ethernet interface 0 is the source IP
address for all syslog messages:
logging source-interface ethernet 0
The following example specifies that the IP address for Ethernet interface 2/1 on a Cisco 7000 series
router is the source IP address for all syslog messages:
logging source-interface ethernet 2/1
Related
Commands
Command
Description
logging
FR-525
logging synchronous
To synchronize unsolicited messages and debug output with solicited Cisco IOS software output and
prompts for a specific console port line, auxiliary port line, or vty, use the logging synchronous line
configuration command. To disable synchronization of unsolicited messages and debug output, use the
no form of this command.
logging synchronous [level severity-level | all] [limit number-of-buffers]
no logging synchronous [level severity-level | all] [limit number-of-buffers]
Syntax Description
Defaults
level severity-level
all
limit number-of-buffers
Command Modes
Line configuration
Command History
Release
Modification
10.0
Usage Guidelines
When synchronous logging of unsolicited messages and debug output is turned on, unsolicited
Cisco IOS software output is displayed on the console or printed after solicited Cisco IOS software
output is displayed or printed. Unsolicited messages and debug output is displayed on the console after
the prompt for user input is returned. To keep unsolicited messages and debug output from being
interspersed with solicited software output and prompts. After the unsolicited messages are displayed,
the console displays the user prompt again.
When specifying a severity level number, consider that for the logging system, low numbers indicate
greater severity and high numbers indicate lesser severity.
FR-526
78-11740-02
When a message queue limit of a terminal line is reached, new messages are dropped from the line,
although these messages might be displayed on other lines. If messages are dropped, the notice
%SYS-3-MSGLOST number-of-messages due to overflow follows any messages that are displayed.
This notice is displayed only on the terminal that lost the messages. It is not sent to any other lines, any
logging servers, or the logging buffer.
Caution
Examples
By configuring abnormally large message queue limits and setting the terminal to terminal monitor on
a terminal that is accessible to intruders, you expose yourself to denial of service attacks. An intruder
could carry out the attack by putting the terminal in synchronous output mode, making a Telnet
connection to a remote host, and leaving the connection idle. This could cause large numbers of
messages to be generated and queued, and these messages would unlikely consume all available RAM.
You should guard against this type of attack through proper configuration.
In the following example, line 4 is identified and synchronous logging for line 4 is enabled with a
severity level of 6. Then another line, line 2, is identified and the synchronous logging for line 2 is
enabled with a severity level of 7 and is specified with a maximum number of buffers to be 70,000.
line 4
logging synchronous level 6
line 2
logging synchronous level 7 limit 70000
Related
Commands
Command
Description
line
Identifies a specific line for configuration and starts the line configuration
command collection mode.
logging on
FR-527
logging trap
To limit messages logged to the syslog servers based on severity, use the logging trap global
configuration command. The command limits the logging of system messages sent to syslog servers to
only those messages at the specified level. To disable logging to syslog servers, use the no form of this
command.
logging trap level
no logging trap
Syntax Description
level
Defaults
informational (level 6)
Command Modes
Command History
Release
Modification
10.0
Usage Guidelines
Limits the logging of messages to the syslog servers to a specified level. You can
enter the level number or level name. See the Usage Guidelines section for a list
of acceptable level keywords.
The show logging EXEC command displays the addresses and levels associated with the current logging
setup. The command output also includes ancillary statistics.
Table 1 lists the syslog definitions that correspond to the debugging message levels. Additionally, four
categories of messages are generated by the software, as follows:
Use the logging and logging trap commands to send messages to a UNIX syslog server.
Table 62
Level Arguments
Level
Description
Syslog Definition
emergencies
System unusable
LOG_EMERG
alerts
LOG_ALERT
critical
Critical conditions
LOG_CRIT
errors
Error conditions
LOG_ERR
warnings
Warning conditions
LOG_WARNING
FR-528
78-11740-02
Table 62
Examples
Level Arguments
Level
Description
Syslog Definition
notifications
LOG_NOTICE
informational
LOG_INFO
debugging
Debugging messages
LOG_DEBUG
Related
Commands
Command
Description
logging
FR-529
ping (privileged)
To diagnose basic network connectivity on Apollo, AppleTalk, Connectionless Network Service
(CLNS), DECnet, IP, Novell IPX, VINES, or XNS networks, use the ping privileged EXEC command.
ping [protocol | tag] {host-name | system-address} [data [hex-data-pattern] | df-bit | repeat
[repeat-count] | size [datagram-size] | source [source-address | async | bvi | ctunnel | dialer |
ethernet | fastEthernet | lex | loopback | multilink | null | port-channel | tunnel | vif |
virtual-template | virtual-tokenring | xtagatm] | timeout [seconds] | validate]
Syntax Description
protocol
(Optional) Protocol keyword, one of apollo, appletalk, clns, decnet, ip, ipx, srb,
vines, or xns.
tag
host-name
system-address
data
hex-data-pattern
df-bit
repeat
repeat-count
size
(Optional) Specifies the datagram size. Datagram size is the number of bytes in
each ping.
datagram-size
source
source-address
async
bvi
ctunnel
dialer
ethernet
fastEthernet
lex
loopback
multilink
null
port-channel
tunnel
vif
virtual-template
timeout
FR-530
78-11740-02
seconds
validate
Command Modes
Privileged EXEC
Command History
Release
Modification
10.0
12.0
The data, df-bit, repeat, size, source, timeout, and validate keywords were
added.
Usage Guidelines
The ping (packet internet groper) command sends ISO CLNS echo packets to test the reachability of a
remote router over a connectionless Open System Interconnection (OSI) network.
The ping command sends an echo request packet to an address, then awaits a reply. Ping output can help
you evaluate path-to-host reliability, delays over the path, and whether the host can be reached or is
functioning.
To abnormally terminate a ping session, type the escape sequenceby default, Ctrl-^ X. You type the
default by simultaneously pressing and releasing the Ctrl, Shift, and 6 keys, and then pressing the X key.
Table 63 describes the test characters that the ping facility sends.
Table 63
Character Description
Note
Examples
Each period indicates that the network server timed out while waiting for a reply.
&
Not all protocols require hosts to support pings. For some protocols, the pings are Cisco-defined and are
only answered by another Cisco router.
After you enter the ping command in privileged mode, the system prompts for one of the following
keywords: apollo, appletalk, clns, decnet, ip, novell, vines, or xns. The default protocol is IP.
If you enter a host name or address on the same line as the ping command, the default action is taken as
appropriate for the protocol type of that name or address.
FR-531
The optional data, df-bit, repeat, size, source, timeout, and validate keywords can be used to avoid
extended ping command output. You can use as many of these keywords as you need, and you can use
them in any order after the host-name or system-address arguments.
Although the precise dialog varies somewhat from protocol to protocol, all are similar to the ping session
using default values shown in the following output:
Router# ping
Protocol [ip]:
Target IP address: 192.168.7.27
Repeat count [5]:
Datagram size [100]:
Timeout in seconds [2]:
Extended commands [n]:
Sweep range of sizes [n]:
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.7.27, timeout is 2 seconds:
!!!!!
Success rate is 100 percent, round-trip min/avg/max = 1/2/4 ms
Field
Description
Protocol [ip]:
Target IP address:
Prompts for the IP address or host name of the destination node you
plan to ping. If you have specified a supported protocol other than IP,
enter an appropriate address for that protocol here. The default is none.
Prompts for the number of ping packets that will be sent to the
destination address. The default is 5 packets.
Prompts for the size of the ping packet (in bytes). The default is 100
bytes.
Allows you to vary the sizes of the echo packets being sent. This
capability is useful for determining the minimum sizes of the MTUs
configured on the nodes along the path to the destination address.
Packet fragmentation contributing to performance problems can then
be reduced.
!!!!!
round-trip min/avg/max =
1/2/4 ms
Indicates the round-trip travel time intervals for the protocol echo
packets, including minimum/average/maximum (in milliseconds).
FR-532
78-11740-02
Related Commands
Command
Description
ping (user)
ping vrf
FR-533
ping (user)
To diagnose basic network connectivity on AppleTalk, Connection Network Service (CLNS), IP, Novell,
Apollo, VINES, DECnet, or XNS networks, use the ping (packet internet groper) user EXEC command.
ping [protocol] {host-name | system-address}
Syntax Description
protocol
(Optional) Protocol keyword, one of apollo, appletalk, clns, decnet, ip, ipx,
vines, or xns.
host-name
system-address
Command Modes
EXEC
Command History
Release
Modification
10.0
Usage Guidelines
The user-level ping feature provides a basic ping facility for users that do not have system privileges.
This feature allows the Cisco IOS software to perform the simple default ping functionality for a number
of protocols. Only the terse form of the ping command is supported for user-level pings.
If the system cannot map an address for a host name, it returns an %Unrecognized host or address error
message.
To abnormally terminate a ping session, type the escape sequenceby default, Ctrl-^ X. You type the
default by simultaneously pressing and releasing the Ctrl, Shift, and 6 keys, and then pressing the X key.
Table 65 describes the test characters that the ping facility sends.
Table 65
Character Description
Examples
Each period indicates that the network server timed out while waiting for a reply.
&
The following display shows sample ping output when you ping the IP host named donald:
Router> ping donald
Type escape sequence to abort.
FR-534
78-11740-02
Related
Commands
Command
Description
ping (privileged)
FR-535
service slave-log
To allow slave Versatile Interface Processor (VIP) cards to log important system messages to the console,
use the service slave-log global configuration command. To disable slave logging, use the no form of
this command.
service slave-log
no service slave-log
Syntax Description
Defaults
Command Modes
CommandHistory
Release
Modification
11.1
Usage Guidelines
This command allows slave slots to log system messages of level 2 or higher (critical, alerts, and
emergencies).
Examples
In the following example, important messages from the slave cards to the console are logged:
service slave-log
In the following example sample output is illustrated 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 system message.
FR-536
78-11740-02
service tcp-keepalives-in
To generate keepalive packets on idle incoming network connections (initiated by the remote host), use
the service tcp-keepalives-in global configuration command. To disable the keepalives, use the no form
of this command.
service tcp-keepalives-in
no service tcp-keepalives-in
Syntax Description
Defaults
Disabled
Command Modes
CommandHistory
Release
Modification
10.0
Examples
Related
Commands
Command
Description
service
tcp-keepalives-out
FR-537
service tcp-keepalives-out
To generate keepalive packets on idle outgoing network connections (initiated by a user), use the
service tcp-keepalives-out global configuration command. To disable the keepalives, use the no form
of this command.
service tcp-keepalives-out
no service tcp-keepalives-out
Syntax Description
Defaults
Disabled
Command Modes
CommandHistory
Release
Modification
10.0
Examples
Related
Commands
Command
Description
service
tcp-keepalives-in
FR-538
78-11740-02
service timestamps
To configure the system to time-stamp debugging or logging messages, use one of the service
timestamps global configuration commands. To disable this service, use the no form of this command.
service timestamps [debug | log] [ uptime | datetime [msec] [localtime] [show-timezone] ]
no service timestamps [debug | log]
Syntax Description
debug
log
uptime
(Optional) Specifies that the time stamp should consist of the time since the
system was last rebooted. For example 4w6d (time since last reboot is 4 weeks
and 6 days).
This is the default timestamp format for both debugging messages and logging
messages.
The format for uptime varies depending on how much time has elapsed:
HHHH:MM:SS (HHHH hours: MM minutes: SS seconds) for the first 24
hours
DdHHh (D days HH hours) after the first day
WwDd (W weeks D days) after the first week
datetime
(Optional) Specifies that the time stamp should consist of the date and time.
The time stamp format for datetime is MMM DD HH:MM:SS, where MMM
is the month, DD is the date, HH is the hour (in 24-hour notation), MM is the
minute, and SS is the second.
If the datetime keyword is specified, you can optionally add the msec
localtime, or show-timezone keywords.
msec
localtime
show-timezone
Defaults
If the localtime keyword option is not used (or if the local time zone has
not been configured using the clock timezone command), time will be
displayed in Universal Coordinated Time (UTC).
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.
FR-539
The no service timestamps command by itself disables time stamps for both debug and log messages.
Command Modes
Command History
Release
Modification
10.0
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. If the system clock has not been set, the date
and time are preceded by an asterisk (*) to indicate that the date and time are probably not correct.
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:
service timestamps log datetime localtime show-timezone
Related Commands
Command
Description
clock set
ntp
FR-540
78-11740-02
Syntax Description
Command Modes
EXEC
CommandHistory
Release
Modification
11.3 XA
Usage Guidelines
The show c2600 command provides complex troubleshooting information that pertains to the platforms
shared references rather than to a specific interface.
Examples
In the following example, sample output is shown for the show c2600 EXEC command. See Table 66
for a description of the output display fields.
router# show c2600
C2600 Platform Information:
Interrupts:
Assigned Handlers...
Vect Handler
# of Ints
00 801F224C
00000000
01 801DE768
0D3EE155
02 801E94E0
0000119E
04 801F0D94
00000000
05 801E6C34
00000000
06 801F0DE4
00002C1A
07 801F0EA0
0000015D
14 801F224C
00000000
IOS Priority Masks...
Level 00 = [ EF020000
Level 01 = [ EC020000
Level 02 = [ E8020000
Level 03 = [ E0020000
Level 04 = [ E0020000
Level 05 = [ E0020000
Level 06 = [ C0020000
Level 07 = [ 00000000
Name
Xilinx bridge error interrupt
MPC860 TIMER INTERRUPT
16552 Con/Aux Interrupt
PA Network Management Int Handler
Timebase Reference Interrupt
PA Network IO Int Handler
MPC860 CPM INTERRUPT
Xilinx bridge error interrupt
]
]
]
]
]
]
]
]
SIU_IRQ_MASK = FFFFFFFF
Spurious IRQs = 00000000
SIEN
= EF02xxxx
SIPEND = 0000xxxx
Current Level = 00
Interrupt Throttling:
FR-541
Throttle Count
Netint usec
Active
Longest IRQ
= 00000000
= 00000000
=
0
= 00000000
Timer Count
= 00000000
Netint Mask usec = 000003E8
Configured
=
0
IDMA Status:
Requests = 00000349
Drops
= 00000000
Complete = 00000349
Post Coalesce Frames = 00000349
Giant
= 00000000
Available Blocks = 256/256
ISP Status:
Version string burned in chip: "A986122997"
New version after next program operation: "B018020998"
ISP family type: "2096"
ISP chip ID: 0x0013
Device is programmable
Table 66
Field
Description
Interrupts
Assigned Handlers
Vect
Handler
# of Ints
Name
SIU_IRQ_MASK
Spurious IRQs
Interrupt Throttling:
Throttle Count
Timer Count
Netint usec
Active
Configured
Longest IRQ
FR-542
78-11740-02
Table 66
Related Commands
Field
Description
IDMA Status
Requests
Drops
Complete
Giant
Available Blocks
ISP Status
ISP chip ID
Device is programmable
Command
Description
show context
FR-543
Syntax Description
Command Modes
EXEC
Command History
Release
Modification
11.2
Usage Guidelines
Examples
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.
A0
170-43690-170
170-170-170
60 3E 28
AA AA AA
Board revision A0
Part number
73-1536-02
RMA number
00-00-00
49 06 00 02 00 00 00 00
FF FF FF FF FF FF FF FF
FR-544
78-11740-02
show cls
To display the current status of all Cisco link services (CLS) sessions on the router, use the show cls
EXEC command.
show cls [brief]
Syntax Description
brief
Defaults
Command Modes
EXEC
Command History
Release
Modification
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.
Examples
The following is sample output from the show cls brief command:
IBD-4500B# show cls brief
DLU user:SNASW
SSap:0x04 VDLC VDLC650
DTE:1234.4000.0001 1234.4000.0002 04 04
FR-545
DLU user:DLSWDLUPEER
DLU user:DLSWDLU
Bridging VDLC VDLC1000
Bridging VDLC VDLC650
The examples show two DLUsSNASw and DLSwactive 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.
FR-546
78-11740-02
Syntax Description
Command Modes
EXEC
Command History
Release
Modification
10.3
Usage Guidelines
Context information is specific to processors and architectures, whereas software version and uptime
information is not specific to architectures. Context information for the Cisco 2600 series router differs
from that for other router types because the Cisco 2600 runs with an M860 processor. The display from
the show context command includes the following information:
Stack trace
Software version
This information is useful only to your technical support representative for analyzing crashes in the field.
Use this information when you read the displayed statistics to an engineer over the phone.
Examples
The following is sample output from the show context command following a system failure on a
Cisco 2600 series router. See Table 67 for a description of the fields in this output.
router# show context
S/W Version: Cisco Internetwork Operating System Software
IOS (tm) c2600 Software (c2600-JS-M), Released Version 11.3(19980115:184921]
Copyright (c) 1986-1998 by cisco Systems, Inc.
Compiled Thu 15-Jan-98 13:49 by mmagno
Exception occurred at: 00:02:26 UTC Mon Mar 1 1993
Exception type: Data TLB Miss (0x1200)
CPU Register Context:
PC = 0x80109964 MSR = 0x00009030 CR = 0x55FFFD35 LR
= 0x80109958
CTR = 0x800154E4 XER = 0xC000BB6F DAR = 0x00000088 DSISR = 0x00000249
DEC = 0x7FFFDFCA TBU = 0x00000000 TBL = 0x15433FCF IMMR = 0x68010020
R0 = 0x80000000 R1 = 0x80E80BD0 R2 = 0x80000000 R3
= 0x00000000
R4 = 0x80E80BC0 R5 = 0x40800000 R6 = 0x00000001 R7
= 0x68010000
R8 = 0x00000000 R9 = 0x00000060 R10 = 0x00001030 R11
= 0xFFFFFFFF
R12 = 0x00007CE6 R13 = 0xFFF379E8 R14 = 0x80D50000 R15
= 0x00000000
FR-547
R16 =
R20 =
R24 =
R28 =
Stack
Frame
Frame
Frame
Frame
Frame
Frame
Table 67
Related Commands
R19
R23
R27
R31
=
=
=
=
0x00000000
0x00000000
0x80E92A80
0x00000018
Field
Description
S/W Version
Exception occurred at
Router real time when exception occurred. The router must have
the clock time properly configured for this to be accurate.
Exception type
Stack trace
Command
Description
show processes
show stacks
FR-548
78-11740-02
show context
To display information stored in NVRAM when the router crashes, use the show context EXEC
command.
show context summary
show context {all | slot slot-number [crash-index] [all] [debug]}
Syntax Description
summary
all
Displays all crashes for all the slots. When optionally used with the slot
keyword, displays crash information for the specified slot.
slot slot-number
[crash-index]
debug
Command Modes
EXEC
Command History
Release
Modification
11.2 GS
This command was modified to add the all, debug, slot, and summary
keywords.
Usage Guidelines
Note
Examples
The display from the show context command includes the following information:
Stack trace
Software version
This information is of use only to technical support representatives in analyzing crashes in the field. It
is included here in case you need to read the displayed statistics to an engineer over the phone.
The following is sample output from the show context command following a system failure:
FR-549
The following is sample output from the show context summary command on a Cisco 12012 router.
The show context summary command displays a summary of all the crashes recorded.
Router# show context summary
CRASH INFO SUMMARY
Slot 0 : 0 crashes
Slot 1 : 0 crashes
Slot 2 : 0 crashes
Slot 3 : 0 crashes
Slot 4 : 0 crashes
Slot 5 : 0 crashes
Slot 6 : 0 crashes
Slot 7 : 2 crashes
1 - crash at 18:06:41 UTC Tue Nov 5 1996
2 - crash at 12:14:55 UTC Mon Nov 4 1996
Slot 8 : 0 crashes
Slot 9 : 0 crashes
Slot 10: 0 crashes
Slot 11: 0 crashes
Router#
Related
Commands
Command
Description
show processes
show stacks
FR-550
78-11740-02
Syntax Description
Command Modes
atm slot-number
clock
csar [register]
csc-fpga
dp83800
fab-clk
fia [register]
pos [slot-number]
[details]
(Optional) Displays the POS framer state and optionally displays all the
details for the interface. Number is slot-number/port-number (for
example, 4/0). Slot numbers range from 0 to 11 for the Cisco 12012
router and from 0 to 7 for the Cisco 12008 router.
queues [slot-number]
sca
xbar
Privileged EXEC
FR-551
Command History
Release
Modification
11.2 GS
This command was added to support the Cisco 12000 series Internet Routers.
Usage Guidelines
This information provided by this command is intended for use only by technical support representatives
in analyzing system failures in the field.
Examples
The following is sample output from the show controllers pos command for a Cisco 12012:
Router# show controllers pos 7/0
POS7/0
SECTION
LOF = 2
LOS = 0
Active Alarms: None
LINE
AIS = 2
RDI = 2
FEBE = 146
Active Alarms: None
PATH
AIS = 2
RDI = 4
FEBE = 63
LOP = 0
PSE = 8
NSE = 3
Active Alarms: None
APS
COAPS = 3
PSBF = 2
State: PSBF_state = False
Rx(K1/K2): F0/15 Tx(K1/K2): 00/00
S1S0 = 00, C2 = 64
PATH TRACE BUFFER : STABLE
Remote hostname : GSR-C
Remote interface: POS10/0
Remote IP addr : 10.201.101.2
Remote Rx(K1/K2): F0/15 Tx(K1/K2): 00/00
Router#
Related Commands
Command
Description
clear controllers
BIP(B1) = 5889
BIP(B2) = 2106453
BIP(B3) = 3216
NEWPTR = 2
show controllers (line Displays information that is specific to the hardware on a line card.
card image)
FR-552
78-11740-02
Syntax Description
atm
port-number
all
sar
summary
fia
register
frfab
tofab
bma
microcode
mis-inst
register
qelem
start-queue-element
end-queue-element
qnum
FR-553
start-queue-number
end-queue-number
queues
statistics
io
l3
pos
framers
queues
registers
rxsram
port-number
queue-start-address
queue-length
txsram
Command Modes
Privileged EXEC
Command History
Release
Modification
11.2 GS
This command was added to support the Cisco 12000 series Gigabit Switch
Routers.
Usage Guidelines
Note
Examples
This information provided by this command is of use only to technical support representatives in
analyzing crashes in the field.
Because you are executing this command on the line card, you must use the execute-on command to use
the show command, or you must connect to the card using the attach command. All examples in this
section use the execute-on command
The following is partial sample output from the show controllers atm command:
Router# execute-on slot 4 show controllers atm 0
TX SAR (Beta 1.0.0) is Operational;
RX SAR (Beta 1.0.0) is Operational;
Interface Configuration Mode:
FR-554
78-11740-02
STS-12c
Active Maker Channels: total # 6
VCID ChnnlID Type OutputInfo
1
0888
UBR
0C010010
2
0988
VBR
04010020
3
8BC8
UBR
0C010030
4
0E08
UBR
0C010040
10
1288
VBR
040100A0
11
8BE8
VBR
0C0100B0
InPkts
0
0
0
0
0
0
InOAMs
0
0
0
0
0
0
MacString
08882000AAAA030000000800
09882000
8BC82000AAAA030000000800
0E082000AAAA030000000800
12882000
8BE82000AAAA030000000800
The following is partial sample output from the show controllers command:
Router# execute-on slot 6 show controllers
Interface POS0
Hardware is BFLC POS
lcpos_instance struct
60311B40
RX POS ASIC addr space 12000000
TX POS ASIC addr space 12000100
SUNI framer addr space 12000400
SUNI rsop intr status
00
CRC32 enabled, HDLC enc, int clock
no loop
Interface POS1
Hardware is BFLC POS
lcpos_instance struct
RX POS ASIC addr space
603142E0
12000000
FR-555
The following is partial sample output from the show controllers pos framers command:
Router# execute-on slot 6 show controllers pos framers
Framer 0, addr=0x12000400:
master reset
C0
master config
1F
master control
00
clock rcv cntrl
D0
RACP control
84
RACP gfc control
0F
TACP control status
04
RACP intr enable
04
RSOP cntrl intr enable 00
RSOP intr status
00
TPOP path sig lbl (c2) 13
SPTB control
04
SPTB status
00
Framer 1, addr=0x12000600:
master reset
C0
master config
1F
master control
00
clock rcv cntrl
D0
RACP control
84
RACP gfc control
0F
TACP control status
04
RACP intr enable
04
RSOP cntrl intr enable 00
RSOP intr status
00
TPOP path sig lbl (c2) 13
SPTB control
04
SPTB status
00
Framer 2, addr=0x12000800:
master reset
C0
master config
1F
master control
00
clock rcv cntrl
D0
RACP control
84
RACP gfc control
0F
TACP control status
04
RACP intr enable
04
RSOP cntrl intr enable 00
RSOP intr status
00
TPOP path sig lbl (c2) 13
SPTB control
04
SPTB status
00
.
.
.
Router#
hcsadd
tnull
hcsadd
tnull
hcsadd
tnull
The following is partial sample output from the show controllers fia command:
FR-556
78-11740-02
Related Commands
redund overflow 0
cell parity
0
2
3
--------------0
0
0
0
req error
multi req
uni req
empty dst req
0
0
0
0
Command
Description
clear controllers
cell drops 0
crc32
0
4
-------0
0
0
0
0
0
FR-557
Syntax Description
vip slot-number
Command Modes
Privileged EXEC
Command History
Release
Modification
11.2
Usage Guidelines
This command displays the state of syslog error and event logging, including host addresses, and
whether console logging is enabled.
Examples
The following is sample output from the show controllers logging command:
Router# show controllers vip 4 logging
Syslog logging: enabled
Console logging: disabled
Monitor logging: level debugging, 266 messages logged.
Trap logging: level informational, 266 messages logged.
Logging to 192.180.2.238
Related Commands
Field
Description
Syslog logging
When enabled, system logging messages are sent to a UNIX host that acts as a
syslog server; that is, it captures and saves the messages.
Console logging
Monitor logging
Trap logging
Command
Description
show logging
FR-558
78-11740-02
Syntax Description
vip slot-number
Command Modes
Privileged EXEC
Command History
Release
Modification
11.2
Usage Guidelines
Use this command to help collect general information about a VIP card when you are reporting a
problem. This command displays the equivalent of the following show commands for the VIP card:
more system:running-config
show buffers
show controllers
show interfaces
show stacks
show version
For a sample display of the show controllers tech-support command output, refer to these show
commands.
Related Commands
Command
Description
more
system:running-config
show buffers
show controllers
show interfaces
show processes
show processes
memory
show stacks
FR-559
Command
Description
show tech-support
show version
FR-560
78-11740-02
show debugging
To display information about the types of debugging that are enabled for your router, use the show
debugging privileged EXEC command.
show debugging
Syntax Description
Command Modes
Privileged EXEC
Command History
Release
Modification
11.1
Examples
The following is sample output from the show debugging command. In this example, three types of CDP
debugging are enabled.
Router# show debugging
CDP:
CDP packet info debugging is on
CDP events debugging is on
CDP neighbor info debugging is on
Related Commands
Command
Description
debug <feature>
FR-561
show diag
To display hardware information including DRAM and static RAM (SRAM) on line cards, use the show
diag command in privileged EXEC mode.
show diag [slot-number] [details] [summary]
Syntax Description
slot-number
details
(Optional) Displays more details than the normal show diag output.
summary
Command Modes
Privileged EXEC
Command History
Release
Modification
11.1 CA
11.2
11.2 P
11.2 GS
This command was made available on Cisco 12000 series Gigabit Switch
Routers (GSRs).
11.3 XA
12.0(5)XQ
This command was enhanced and made available on Cisco 1750 routers.
12.0(7)T
Usage Guidelines
Note
Use this command to determine the type of hardware installed in your router. This command applies line
cards in Cisco Universal Access Servers; Cisco 1750, 7200, and 7500 series routers; and Cisco 12000
series GSRs.
The enhancement to display the field replaceable unit (FRU) number in show diag command output is
not available in all Cisco IOS releases and not all Cisco devices and Cisco network modules will display
their FRU numbers.
Examples of output showing the FRU number are included in the Examples section.
Cisco 7304 Router Usage Guidelines
For the Cisco 7304 router, this command applies to NSEs, line cards, MSCs, and SPAs.
To display hardware information for an NSE, line card, or MSC in the specified slot, use the
slot-number argument. For MSCs, information about the MSC and each of its installed SPAs is
displayed.
To display hardware information about the backplane, power supplies, and fan modules, use the
chassis keyword.
FR-562
78-11740-02
Examples
To display hardware information for an MSC or SIP only in a specified slot, use the slot-number
argument.
To display hardware information for a SPA only, use the show diag subslot slot/subslot version of
this command.
Example for a 1-Port T3 Serial Port Adapter on the Cisco 7200 Series Router
The following is sample output from the show diag command for a 1-port T3 serial port adapter in
chassis slot 1 on a Cisco 7200 series router:
Router# show diag 1
Slot 1:
Physical slot 1, ~physical slot 0xE, logical slot 1, CBus 0
Microcode Status 0x4
Master Enable, LED, WCS Loaded
Board is analyzed
Pending I/O Status: None
EEPROM format version 1
VIP2 controller, HW rev 2.4, board revision D0
Serial number: 04372053 Part number: 73-1684-03
Test history: 0x00
RMA number: 00-00-00
Flags: cisco 7000 board; 7500 compatible
EEPROM contents (hex):
0x20: 01 15 02 04 00 42 B6 55 49 06 94 03 00 00 00 00
0x30: 68 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Slot database information:
Flags: 0x4
Insertion time: 0x14A8 (5d02h ago)
Controller Memory Size: 16 MBytes DRAM, 1024 KBytes SRAM
PA Bay 0 Information:
T3 Serial PA, 1 ports
EEPROM format version 1
HW rev FF.FF, Board revision UNKNOWN
Serial number: 4294967295 Part number: 255-65535-255
The following is sample output from the show diag command on a Cisco 7200 series router showing the
FRU number:
Router# show diag
Slot 0:
Dual FastEthernet (RJ-45) I/O Card Port adapter, 2 ports
Port adapter is analyzed
Port adapter insertion time 6d02h ago
EEPROM contents at hardware discovery:
Hardware Revision
: 2.1
Top Assy. Part Number
: 800-07114-06
Part Number
: 73-5003-06
Board Revision
: B0
PCB Serial Number
: 31558694
RMA History
: 00
Fab Version
: 03
Fab Part Number
: 28-3455-03
Product (FRU) Number
: C7200-I/O-2FE/E
Deviation Number
: 0-0
FR-563
02
42
00
49
FF
FF
FF
FF
01
30
02
2F
FF
FF
FF
FF
C0
C1
03
4F
FF
FF
FF
FF
46
8B
85
2D
FF
FF
FF
FF
03
33
1C
32
FF
FF
FF
FF
20
31
0D
46
FF
FF
FF
FF
00
35
7F
45
FF
FF
FF
FF
1B
35
03
2F
FF
FF
FF
FF
CA
38
CB
45
FF
FF
FF
FF
06
36
8F
80
FF
FF
FF
FF
Router#
The following is sample output from the show diag command on a Cisco 12000 series Internet router:
Router# show diag 3
SLOT 3 (RP/LC 3 ): 4 Port Packet Over SONET OC-3c/STM-1 Multi Mode
MAIN: type 33, 00-0000-00 rev 70 dev 0
HW config: 0x01
SW key: 00-00-00
PCA: 73-2147-02 rev 94 ver 2
HW version 1.0 S/N 04499695
MBUS: MBUS Agent (1) 73-2146-05 rev 73 dev 0
HW version 1.1 S/N 04494882
Test hist: 0x00
RMA#: 00-00-00
RMA hist: 0x00
DIAG: Test count: 0x05000001
Test results: 0x00000000
MBUS Agent Software version 01.27 (RAM) using CAN Bus A
ROM Monitor version 00.0D
Fabric Downloader version used 00.0D (ROM version is 00.0D)
Board is analyzed
Board State is Line Card Enabled (IOS RUN )
Insertion time: 00:00:10 (00:04:51 ago)
DRAM size: 33554432 bytes
FrFab SDRAM size: 67108864 bytes
ToFab SDRAM size: 16777216 bytes
The following is sample output from the show diag command with the summary keyword:
Router# show diag summary
SLOT
SLOT
SLOT
SLOT
SLOT
SLOT
SLOT
SLOT
SLOT
SLOT
SLOT
SLOT
SLOT
SLOT
SLOT
0
2
4
7
9
11
16
17
18
19
20
24
26
28
29
(RP/LC 0 ):
(RP/LC 2 ):
(RP/LC 4 ):
(RP/LC 7 ):
(RP/LC 9 ):
(RP/LC 11):
(CSC 0
):
(CSC 1
):
(SFC 0
):
(SFC 1
):
(SFC 2
):
(PS A1
):
(PS B1
):
(TOP FAN ):
(BOT FAN ):
Route Processor
4 Port Packet Over SONET
4 Port Packet Over SONET
4 Port Packet Over SONET
4 Port Packet Over SONET
4 Port Packet Over SONET
Clock Scheduler Card
Clock Scheduler Card
Switch Fabric Card
Switch Fabric Card
Switch Fabric Card
AC Power Supply
AC Power Supply
Blower Module
Blower Module
OC-3c/STM-1
OC-3c/STM-1
OC-3c/STM-1
OC-3c/STM-1
OC-3c/STM-1
Single
Single
Single
Single
Single
Mode
Mode
Mode
Mode
Mode
The following is sample output from the show diag command with the details keyword:
Router# show diag 4 details
SLOT 4 (RP/LC 4): 4 Port Packet Over SONET OC-3c/STM-1 Single Mode
MAIN: type 33, 800-2389-01 rev 71 dev 16777215
HW config: 0x00
SW key: FF-FF-FF
PCA: 73-2275-03 rev 75 ver 3
FR-564
78-11740-02
The following is sample output from the show diag command for one ATM Segmentation and
Reassembly (SAR) AIM in a Cisco 3660 router:
Router# show diag 0
3660 Chassis type: ENTERPRISE
c3600 Backplane EEPROM:
Hardware Revision
: 1.0
Top Assy. Part Number
: 800-04740-02
.
.
.
ATM AIM: 1
ATM AIM module with SAR only (no DSPs)
Hardware Revision
: 1.0
Top Assy. Part Number
: 800-03700-01
Board Revision
: A0
Deviation Number
: 0-0
Fab Version
: 02
PCB Serial Number
: JAB9801ABCD
The following is sample output from the show diag command on a Cisco 3660 router that shows the FRU
numbers for slots 0 and 1:
Router# show diag
3660 Chassis type: ENTERPRISE
3660 Backplane EEPROM:
Hardware Revision
Top Assy. Part Number
Board Revision
Deviation Number
Fab Version
PCB Serial Number
RMA Test History
RMA Number
:
:
:
:
:
:
:
:
1.0
800-04740-02
C0
0-0
02
HAD04471U36
00
0-0-0-0
FR-565
RMA History
: 00
Chassis Serial Number
: JAB055180FF
Chassis MAC Address
: 0007.ebea.4460
MAC Address block size
: 112
Manufacturing Test Data : 00 00 00 00 00 00 00 00
Fab Part Number
: 28-2651-02
Number of Slots
: 6
EEPROM format version 4
EEPROM contents (hex):
0x00: 04 FF 40 00 C8 41 01 00 C0 46 03 20 00 12 84
0x10: 42 43 30 80 00 00 00 00 02 02 C1 8B 48 41 44
0x20: 34 34 37 31 55 33 36 03 00 81 00 00 00 00 04
0x30: C2 8B 4A 41 42 30 35 35 31 38 30 46 46 C3 06
0x40: 07 EB EA 44 60 43 00 70 C4 08 00 00 00 00 00
0x50: 00 00 85 1C 0A 5B 02 01 06 FF FF FF FF FF FF
0x60: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x70: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
02
30
00
00
00
FF
FF
FF
09
85
FF
FF
FF
FF
FF
00
Slot 0:
Slot 1:
Mueslix-4T Port adapter, 4 ports
Port adapter is analyzed
Port adapter insertion time unknown
EEPROM contents at hardware discovery:
Hardware revision 1.1
Board revision D0
Serial number
17202570
Part number
800-02314-02
FRU Part Number: NM-4T=
Test history
0x0
RMA number
00-00-00
EEPROM format version 1
EEPROM contents (hex):
0x00: 01 54 01 01 01 06 7D 8A 50 09 0A 02 00 00 00 00
0x10: 68 00 00 00 99 11 21 00 00 05 FF FF FF FF FF FF
Router#
FR-566
78-11740-02
The following is sample output from the show diag command for a Cisco 2611 router with the
NM-AIC-64 installed.
Router# show diag
Slot 0:
C2611 2E Mainboard Port adapter, 2 ports
Port adapter is analyzed
Port adapter insertion time unknown
EEPROM contents at hardware discovery:
Hardware Revision : 2.3
PCB Serial Number : JAD044808SG (1090473337)
Part Number : 73-2840-13
RMA History : 00
RMA Number : 0-0-0-0
Board Revision : C0
Deviation Number : 0-0
EEPROM format version 4
EEPROM contents (hex):
0x00: 04 FF 40 00 92 41 02 03 C1 18 4A 41 44
0x10: 38 30 38 53 47 20 28 31 30 39 30 34 37
0x20: 37 29 82 49 0B 18 0D 04 00 81 00 00 00
0x30: 30 80 00 00 00 00 FF FF FF FF FF FF FF
0x40: FF FF FF FF FF FF FF FF FF FF FF FF FF
0x50: FF FF FF FF FF FF FF FF FF FF FF FF FF
0x60: FF FF FF FF FF FF FF FF FF FF FF FF FF
0x70: FF FF FF FF FF FF FF FF FF FF FF FF FF
30
33
00
FF
FF
FF
FF
FF
34
33
42
FF
FF
FF
FF
FF
34
33
43
FF
FF
FF
FF
FF
Slot 1:
NM_AIC_64 Port adapter, 3 ports
Port adapter is analyzed
Port adapter insertion time unknown
EEPROM contents at hardware discovery:
Hardware Revision : 1.0
Part Number : 74-1923-01
Board Revision : 02
PCB Serial Number : DAN05060012
EEPROM format version 4
EEPROM contents (hex):
0x00: 04 FF 40 02 55 41 01 00 82 4A 07
0x10: C1 8B 44 41 4E 30 35 30 36 30 30
0x20: FF FF FF FF FF FF FF FF FF FF FF
0x30: FF FF FF FF FF FF FF FF FF FF FF
0x40: FF FF FF FF FF FF FF FF FF FF FF
0x50: FF FF FF FF FF FF FF FF FF FF FF
0x60: FF FF FF FF FF FF FF FF FF FF FF
0x70: FF FF FF FF FF FF FF FF FF FF FF
42
FF
FF
FF
FF
FF
FF
FF
30
FF
FF
FF
FF
FF
FF
FF
32
FF
FF
FF
FF
FF
FF
FF
83
31
FF
FF
FF
FF
FF
FF
01
32
FF
FF
FF
FF
FF
FF
Field
Description
Hardware Revision
FR-567
Table 69
Field
Description
Part Number
RMA History
Counter that indicates how many times the port adapter has been
returned and repaired.
RMA Number
Board Revision
Deviation Number
The following example shows how to obtain hardware information about an installed AIM-VPN on the
Cisco 2611XM router.
Router# show diag 0
Encryption AIM 1:
Hardware Revision
Top Assy. Part Number
Board Revision
Deviation Number
Fab Version
PCB Serial Number
RMA Test History
RMA Number
RMA History
EEPROM format version 4
EEPROM contents (hex):
0x00:04 FF 40 03 0B 41
0x10:42 41 30 80 00 00
0x20:38 30 31 41 42 43
0x30:FF FF FF FF FF FF
0x40:FF FF FF FF FF FF
0x50:FF FF FF FF FF FF
0x60:FF FF FF FF FF FF
0x70:FF FF FF FF FF FF
:1.0
:800-03700-01
:A0
:0-0
:02
:JAB9801ABCD
:00
:0-0-0-0
:00
01
00
44
FF
FF
FF
FF
FF
00
00
03
FF
FF
FF
FF
FF
C0
02
00
FF
FF
FF
FF
FF
46
02
81
FF
FF
FF
FF
FF
03
C1
00
FF
FF
FF
FF
FF
20
8B
00
FF
FF
FF
FF
FF
00
4A
00
FF
FF
FF
FF
FF
0E
41
00
FF
FF
FF
FF
FF
74
42
04
FF
FF
FF
FF
FF
01
39
00
FF
FF
FF
FF
FF
FR-568
78-11740-02
Field
Description
Hardware Revision
Board Revision
Deviation Number
RMA Number
RMA History
Counter that indicates how many times the port adapter has been
returned and repaired.
The following is sample output from the show diag slot-number version of the command for an
MSC-100 located in slot number 4 on a Cisco 7304 router. Information about the MSC is followed by
information for its associated SPAs:
Router# show diag 4
Slot 4:
7304-MSC-100 SPA Carrier Card Line Card
Line Card state: Active
Insertion time: 00:08:49 ago
Bandwidth points: 4000000
EEPROM contents at hardware discovery:
Hardware Revision
: 0.18
Boot Time out
: 0000
PCB Serial Number
: CSJ07288905
Part Number
: 73-8789-01
Board Revision
: A0
Fab Version
: 02
RMA Test History
: 00
RMA Number
: 0-0-0-0
RMA History
: 00
Deviation Number
: 0-0
Product Number
: 7304-MSC-100
Top Assy. Part Number
: 68-1163-04
Manufacturing Test Data : 00 00 00 00 00 00 00 00
Field Diagnostics Data
: 00 00 00 00 00 00 00 00
Calibration Data
: Minimum: 0 dBmV, Maximum:
Calibration values :
EEPROM format version 4
EEPROM contents (hex):
0x00: 04 FF 40 04 50 41 00 12 46 00 00 C1 8B 43 53
0x10: 30 37 32 38 38 39 30 35 82 49 22 55 01 42 41
0x20: 02 02 03 00 81 00 00 00 00 04 00 80 00 00 00
0x30: CB 94 37 33 30 34 2D 4D 53 43 2D 31 30 30 20
0x40: 20 20 20 20 20 20 87 44 04 8B 04 C4 08 00 00
0x50: 00 00 00 00 00 C5 08 00 00 00 00 00 00 00 00
0x60: 09 00 00 00 00 00 00 00 00 00 C7 7C F6 44 3F
0x70: 00 00 00 00 00 00 00 00 00 00 00 00 02 EE FF
0 dBmV
4A
30
00
20
00
C8
30
C8
FR-569
0x80: C8 37 26 05 DC 64 28 1E 37 26 09 C4 64 32 28 32
0x90: DD 0C E4 64 32 28 43 24 2E E0 AA 82 64 F4 24 00
0xA0: 00 00 00 00 00 00 F0 2E FF FF FF FF FF FF FF FF
0xB0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0xC0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0xD0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0xE0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0xF0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x100: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x110: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x120: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x130: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x140: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x150: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x160: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x170: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x180: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x190: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x1A0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x1B0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x1C0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x1D0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x1E0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x1F0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
FPGA information:
Current FPGA version
: 00.23
IOS bundled FPGA version : 00.23
CPLD version
: 01.02
Subslot 4/1:
Shared port adapter: SPA-4FE-7304, 4 ports
State: ok
Insertion time: 00:15:13 ago
Bandwidth: 400000 kbps
EEPROM contents:
The following is sample output from the show diag subslot command for a 4-Port 10/100 Fast Ethernet
SPA located in the bottom subslot (1) of the MSC that is installed in slot 4 on a Cisco 7304 router:
Router# show diag subslot 4/1
Subslot 4/1:
Shared port adapter: SPA-4FE-7304, 4 ports
Info: hw-ver=0x100, sw-ver=0x0 fpga-ver=0x0
State: ok
Insertion time: 23:20:42 ago
Bandwidth: 400000 kbps
EEPROM contents:
Hardware Revision
: 1.0
Boot Time out
: 0190
PCB Serial Number
: JAB073204G5
Part Number
: 73-8717-03
73/68 Level Revision
: 01
Fab Version
: 02
RMA Test History
: 00
RMA Number
: 0-0-0-0
RMA History
: 00
Deviation Number
: 0
Product Number
: SPA-4FE-7304
Product Version Id
: V01
Top Assy. Part Number
: 68-2181-01
73/68 Level Revision
: A0
CLEI Code
: CNS9420AAA
FR-570
78-11740-02
:
:
:
:
:
0000.0000.0000
1024
00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00
00 00 00 00
: Minimum: 0 dBmV, Maximum: 0 dBmV
:
: 160000mW max
: 0mW
: 0mW
: 0mW
Calibration Data
Calibration values
Power Consumption
Mode 1
Mode 2
Mode 3
EEPROM format version 4
EEPROM contents (hex):
0x00: 04 FF 40 04 35 41 01 00 46 01 90 C1 8B 4A 41 42
0x10: 30 37 33 32 30 34 47 35 82 49 22 0D 03 8A 30 31
0x20: 20 20 02 02 03 00 81 00 00 00 00 04 00 88 00 00
0x30: 00 00 CB 94 53 50 41 2D 34 46 45 2D 37 33 30 34
0x40: 20 20 20 20 20 20 20 20 89 56 30 31 20 87 44 08
0x50: 85 01 8A 41 30 20 20 C6 8A 43 4E 53 39 34 32 30
0x60: 41 41 41 CF 06 00 00 00 00 00 00 43 04 00 C4 08
0x70: 00 00 00 00 00 00 00 00 C5 08 00 00 00 00 00 00
0x80: 00 00 F4 00 64 00 00 00 00 00 00 00 00 00 00 00
0x90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xA0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xB0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xC0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xD0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xE0: 00 00 00 00 00 00 00 00 00 C8 09 00 00 00 00 00
0xF0: 00 00 00 00 D7 08 3E 80 00 00 00 00 00 00 F3 00
0x100: 41 01 08 F6 48 43 34 F6 49 44 35 02 31 04 B0 B4
0x110: A0 8C 00 00 05 DC 64 46 32 00 00 07 08 64 46 32
0x120: 00 00 09 C4 64 46 32 00 00 0C E4 64 46 32 00 00
0x130: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 FE 02
0x140: F2 A6 FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x150: CC A0 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x160: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x170: 00 00 D4 A0 00 00 00 00 00 00 00 00 00 00 00 00
0x180: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x190: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x1A0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x1B0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x1C0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x1D0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x1E0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x1F0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
FPGA version:
Software version : 04.17
Hardware version : 04.17
FR-571
The following is sample output from the show diag subslot command for a 2-Port 10/100/1000 Gigabit
Ethernet SPA located in the top subslot (0) of the MSC that is installed in slot 4 on a Cisco 7304 router:
Router# show diag subslot 4/0
Subslot 4/0:
Shared port adapter: SPA-2GE-7304, 2 ports
Info: hw-ver=0x17, sw-ver=0x0 fpga-ver=0x0
State: ok
Insertion time: 00:08:47 ago
Bandwidth: 2000000 kbps
EEPROM contents:
Hardware Revision
: 0.23
Boot Time out
: 0190
PCB Serial Number
: JAB073406YH
Part Number
: 73-8792-02
73/68 Level Revision
: 01
Fab Version
: 02
RMA Test History
: 00
RMA Number
: 0-0-0-0
RMA History
: 00
Deviation Number
: 0
Product Number
: SPA-2GE-7304
Product Version Id
: V01
Top Assy. Part Number
: 68-2181-01
73/68 Level Revision
: A0
CLEI Code
: CNS9420AAA
Base MAC Address
: 0000.0000.0000
MAC Address block size
: 1024
Manufacturing Test Data : 00 00 00 00 00 00 00 00
Field Diagnostics Data
: 00 00 00 00 00 00 00 00
Field Diagnostics Data
: 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00
00 00 00 00
Calibration Data
: Minimum: 0 dBmV, Maximum:
Calibration values :
Power Consumption
: 160000mW max
Mode 1 : 0mW
Mode 2 : 0mW
Mode 3 : 0mW
EEPROM format version 4
EEPROM contents (hex):
0x00: 04 FF 40 04 36 41 00 17 46 01 90 C1 8B 4A 41
0x10: 30 37 33 34 30 36 59 48 82 49 22 58 02 8A 30
0x20: 20 20 02 02 03 00 81 00 00 00 00 04 00 88 00
0x30: 00 00 CB 94 53 50 41 2D 32 47 45 2D 37 33 30
0x40: 20 20 20 20 20 20 20 20 89 56 30 31 20 87 44
0x50: 85 01 8A 41 30 20 20 C6 8A 43 4E 53 39 34 32
0x60: 41 41 41 CF 06 00 00 00 00 00 00 43 04 00 C4
0x70: 00 00 00 00 00 00 00 00 C5 08 00 00 00 00 00
0x80: 00 00 F4 00 64 00 00 00 00 00 00 00 00 00 00
0x90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xA0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xB0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xC0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0 dBmV
42
31
00
34
08
30
08
00
00
00
00
00
00
FR-572
78-11740-02
0xD0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0xE0: 00 00 00 00 00 00 00 00 00 C8 09 00 00 00 00 00
0xF0: 00 00 00 00 D7 08 3E 80 00 00 00 00 00 00 F3 00
0x100: 41 01 08 F6 48 43 34 F6 49 44 35 02 31 03 E8 B4
0x110: A0 8C 37 26 05 DC 64 46 32 37 26 07 08 64 46 32
0x120: 37 26 09 C4 64 46 32 32 DD 0C E4 64 46 32 43 24
0x130: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 FE 02
0x140: EF E2 FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x150: CC A0 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x160: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x170: 00 00 D4 A0 00 00 00 00 00 00 00 00 00 00 00 00
0x180: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x190: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x1A0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x1B0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x1C0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x1D0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x1E0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x1F0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
FPGA version:
Software version : 04.17
Hardware version : 04.17
The following is sample output from the show diag subslot command for the 1-Port OC-192c/STM-64c
POS/RPR XFP SPA in subslot 1 of the SIP located in chassis slot 1 on a Cisco 12000 series router:
Router# show diag subslot 1/1
SUBSLOT 1/1 (SPA-OC192POS-XFP): 1-port OC192/STM64 POS/RPR XFP Optics Shared Port Adapter
Product Identifier (PID) : SPA-OC192POS-XFP
Version Identifier (VID) : V01
PCB Serial Number
: PRTA1304061
Top Assy. Part Number
: 68-2190-01
Top Assy. Revision
: A0
Hardware Revision
: 2.0
CLEI Code
: UNASSIGNED
Insertion Time
: 00:00:10 (13:14:17 ago)
Operational Status
: ok
Field
Description
Hardware Revision
CLEI Code
FR-573
Table 71
Field
Description
Insertion Time
Time when the SPA was installed, and elapsed time between that
insertion time and the current time.
Operational Status
Current status of the SPA. For more information about the status
field descriptions, refer to the show hw-module subslot oir
command.
The following is sample output from the show diag subslot details command for the 1-Port
OC-192c/STM-64c POS/RPR XFP SPA in subslot 1 of the SIP located in chassis slot 1 on a Cisco 12000
series router:
Router# show diag subslot 1/1 details
SUBSLOT 1/1 (SPA-OC192POS-XFP): 1-port OC192/STM64 POS/RPR XFP Optics Shared Port Adapter
EEPROM version
: 4
Compatible Type
: 0xFF
Controller Type
: 1100
Hardware Revision
: 2.0
Boot Timeout
: 400 msecs
PCB Serial Number
: PRTA1304061
PCB Part Number
: 73-8546-01
PCB Revision
: A0
Fab Version
: 01
RMA Test History
: 00
RMA Number
: 0-0-0-0
RMA History
: 00
Deviation Number
: 0
Product Identifier (PID) : SPA-OC192POS-XFP
Version Identifier (VID) : V01
Top Assy. Part Number
: 68-2190-01
Top Assy. Revision
: A0
IDPROM Format Revision
: 36
System Clock Frequency
: 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00
00 00 00 00 00 00
CLEI Code
: UNASSIGNED
Base MAC Address
: 00 00 00 00 00 00
MAC Address block size
: 0
Manufacturing Test Data : 00 00 00 00 00 00 00 00
Field Diagnostics Data
: 00 00 00 00 00 00 00 00
Calibration Data
: Minimum: 0 dBmV, Maximum: 0 dBmV
Calibration values :
Power Consumption
: 11000 mWatts (Maximum)
Environment Monitor Data : 03 30 04 B0 46 32 07 08
46 32 09 C4 46 32 0C E4
46 32 13 88 46 32 07 08
46 32 EB B0 50 3C 00 00
00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00
00 00 FE 02 F6 AC
Processor Label
: 00 00 00 00 00 00 00
Platform features
: 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00
00 00 00 00 00 00 00
Asset ID
:
Asset Alias
:
Insertion Time
: 00:00:10 (13:14:24 ago)
Operational Status
: ok
FR-574
78-11740-02
The following is sample output from the show diag command for a SIP located in chassis slot 2 on a
Cisco 12000 series router:
Router# show diag 2
SLOT 2 (RP/LC 2 ): Modular 10G SPA Interface Card
MAIN: type 149, 800-26270-01 rev 84
Deviation: 0
HW config: 0x00
SW key: 00-00-00
PCA: 73-9607-01 rev 91 ver 1
Design Release 1.0 S/N SAD08460678
MBUS: Embedded Agent
Test hist: 0x00
RMA#: 00-00-00
RMA hist: 0x00
DIAG: Test count: 0x00000000
Test results: 0x00000000
FRU: Linecard/Module: 12000-SIP-650
FRU: Linecard/Module: 12000-SIP-650
Processor Memory: MEM-LC5-1024=(Non-Replaceable)
Packet Memory: MEM-LC5-PKT-256=(Non-Replaceable)
L3 Engine: 5 - ISE OC192 (10 Gbps)
MBUS Agent Software version 1.114 (RAM) (ROM version is 3.4)
ROM Monitor version 255.255
Fabric Downloader version used 3.7 (ROM version is 255.255)
Primary clock is CSC 1
Board is analyzed
Board State is Line Card Enabled (IOS RUN )
Insertion time: 1d00h (2d08h ago)
Processor Memory size: 1073741824 bytes
TX Packet Memory size: 268435456 bytes, Packet Memory pagesize: 32768 bytes
RX Packet Memory size: 268435456 bytes, Packet Memory pagesize: 32768 bytes
0 crashes since restart
SPA Information:
subslot 2/0:
subslot 2/1:
subslot 2/2:
subslot 2/3:
The following is sample output from the show diag command for a Cisco 2811 router with
HWIC-1ADSL installed in slot 1 and HWIC-1ADSLI installed in slot 2. Each HWIC has a daughtercard
as part of its assembly. The command results below give the output from the HWIC followed by the
output from its daughtercard.
Router# show diag 0
Slot 0:
C2811 Motherboard with 2FE and integrated VPN Port adapter, 2 ports
Port adapter is analyzed
Port adapter insertion time unknown
Onboard VPN
: v2.2.0
EEPROM contents at hardware discovery:
PCB Serial Number
: FOC09052HHA
Hardware Revision
: 2.0
Top Assy. Part Number
: 800-21849-02
Board Revision
: B0
Deviation Number
: 0
Fab Version
: 06
RMA Test History
: 00
RMA Number
: 0-0-0-0
RMA History
: 00
Processor type
: 87
FR-575
20
8B
00
4C
D9
FF
FF
FF
48
02
00
30
43
8F
82
FF
48
42
00
39
00
43
49
FF
41
42
04
30
18
49
1C
FF
40
30
00
38
C6
53
2E
FF
00
46
00
20
02
FF
FF
FF
66
48
00
20
40
FF
FF
FF
87
48
04
20
C1
FF
FF
FF
01
30
00
20
C6
FF
FF
FF
EM Slot 0:
ADSL over POTS non-removable daughtercard
Hardware Revision
: 5.0
Part Number
: 73-9307-05
Board Revision
: 03
Deviation Number
: 0
Fab Version
: 05
PCB Serial Number
: FHH0936006E
RMA Test History
: 00
RMA Number
: 0-0-0-0
RMA History
: 00
Fab Part Number
: 28-6607-05
Manufacturing Test Data : 00 00 00 00 00 00 00 00
Field Diagnostics Data
: 00 00 00 00 00 00 00 00
Connector Type
: 01
Version Identifier
: V01
Product (FRU) Number
:
EEPROM format version 4
EEPROM contents (hex):
0x00: 04 FF 40 04 7A 41 05 00 82 49 24 5B 05 42 30 33
FR-576
78-11740-02
0x10:
0x20:
0x30:
0x40:
0x50:
0x60:
0x70:
88
30
CF
00
FF
FF
FF
00
30
05
00
FF
FF
FF
00
36
C4
00
FF
FF
FF
00
45
08
00
FF
FF
FF
00
03
00
00
FF
FF
FF
02
00
00
00
FF
FF
FF
05
81
00
05
FF
FF
FF
C1
00
00
01
FF
FF
FF
8B
00
00
89
FF
FF
FF
46
00
00
56
FF
FF
FF
48
00
00
30
FF
FF
FF
48
04
00
31
FF
FF
FF
30
00
C5
20
FF
FF
FF
39
85
08
FF
FF
FF
FF
33
1C
00
FF
FF
FF
FF
36
19
00
FF
FF
FF
FF
WIC Slot 2:
ADSL over ISDN
Hardware Revision
: 7.0
Top Assy. Part Number
: 800-26248-01
Board Revision
: 01
Deviation Number
: 0
Fab Version
: 07
PCB Serial Number
: FHH093600DA
RMA Test History
: 00
RMA Number
: 0-0-0-0
RMA History
: 00
Product (FRU) Number
: HWIC-1ADSLI
Version Identifier
: V01
CLEI Code
:
EEPROM format version 4
EEPROM contents (hex):
0x00: 04 FF 40 04 C9 41 07 00 C0 46 03
0x10: 42 30 31 88 00 00 00 00 02 07 C1
0x20: 39 33 36 30 30 44 41 03 00 81 00
0x30: CB 94 48 57 49 43 2D 31 41 44 53
0x40: 20 20 20 20 20 20 89 56 30 31 20
0x50: 8A FF FF FF FF FF FF FF FF FF FF
0x60: FF FF FF FF FF FF FF FF FF FF FF
0x70: FF FF FF FF FF FF FF FF FF FF FF
20
8B
00
4C
D9
FF
FF
FF
00
46
00
49
02
FF
FF
FF
66
48
00
20
40
FF
FF
FF
88
48
04
20
C1
FF
FF
FF
01
30
00
20
C6
FF
FF
FF
EM Slot 0:
ADSL over ISDN non-removable daughtercard
Hardware Revision
: 5.0
Part Number
: 73-9308-05
Board Revision
: 03
Deviation Number
: 0
Fab Version
: 05
PCB Serial Number
: FHH0936008M
RMA Test History
: 00
RMA Number
: 0-0-0-0
RMA History
: 00
Fab Part Number
: 28-6607-05
Manufacturing Test Data : 00 00 00 00 00 00 00 00
Field Diagnostics Data
: 00 00 00 00 00 00 00 00
Connector Type
: 01
Version Identifier
: V01
Product (FRU) Number
:
EEPROM format version 4
EEPROM contents (hex):
0x00: 04 FF 40 04 7B 41 05 00 82 49 24 5C 05 42 30
0x10: 88 00 00 00 00 02 05 C1 8B 46 48 48 30 39 33
0x20: 30 30 38 4D 03 00 81 00 00 00 00 04 00 85 1C
0x30: CF 05 C4 08 00 00 00 00 00 00 00 00 C5 08 00
0x40: 00 00 00 00 00 00 05 01 89 56 30 31 20 FF FF
0x50: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x60: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x70: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
33
36
19
00
FF
FF
FF
FF
The following sample output from a Cisco 6500 series switch shows the FRU number:
FR-577
The following sample output from a Cisco 7600 series router shows the FRU number:
Router#show diag
Slot 2: Logical_index 4
2 port adapter Enhanced FlexWAN controller
Board is analyzed ipc ready
HW rev 2.1, board revision A0
Serial Number: JAE0940MH7Z Part number: 73-9539-04
Slot database information:
Flags: 0x2004
Insertion time: 0x256BC (1d01h ago)
Controller Memory Size:
384 MBytes CPU Memory
127 MBytes Packet Memory
511 MBytes Total on Board SDRAM
IOS (tm) cwlc Software (cwpa2-DW-M), Version 12.2(18)SXF2, RELEASE SOFT)
PA Bay 0 Information:
FR-578
78-11740-02
Related Commands
Command
Description
show controllers
gigabitethernet
FR-579
show disk0:
To display flash or file system information for a disk located in slot 0, use the show disk command in
user EXEC or privileged EXEC mode.
show disk0: [all | filesys]
Syntax Description
all
filesys
Command Modes
User EXEC
Privileged EXEC
Command History
Release
Modification
11.3AA
12.2
12.3(7)T
This command was enhanced to display information about the ATA ROM
monitor library (monlib) file.
12.2(25)S
Usage Guidelines
The show disk0: command is supported only on platforms that have a disk file system located in slot 0.
Use the show disk0: command to display details about the files in a particular ATA PCMCIA flash disk
memory card.
For more information regarding file systems and flash cards, access the PCMCIA Filesystem
Compatibility Matrix and Filesystem Information document at the following URL:
http://www.cisco.com/en/US/partner/products/hw/routers/ps341/products_tech_note09186a00800a751
5.shtml
Note
The name of the ATA monlib file may contain a platform name that does not match the platform that you
are using. Different platforms may have a similar name or the same name for their ATA monlib file.
FR-580
78-11740-02
Examples
The following examples show displays of information about the flash disks or file system information
for a disk. The output is self-explanatory.
c7200# show disk0:
-#- --length-- -----date/time------ path
1
29505176 Feb 27 2006 17:56:52 +00:00 c7200-jk9o3s-mz.124-6.T
2
32768 Feb 24 2006 13:30:30 +00:00 file1.log
34738176 bytes available (29540352 bytes used)
c7200# show disk0: all
-#- --length-- -----date/time------ path
1
29505176 Feb 27 2006 17:56:52 +00:00 c7200-jk9o3s-mz.124-6.T
2
32768 Feb 24 2006 13:30:30 +00:00 file1.log
34738176 bytes available (29540352 bytes used)
******** ATA Flash Card Geometry/Format Info ********
ATA CARD GEOMETRY
Number of Heads:
Number of Cylinders
Sectors per Cylinder
Sector Size
Total Sectors
4
984
32
512
125952
62
8
15693
125812
232
108
264
4
984
32
512
125952
62
8
15693
125812
232
FR-581
108
264
Related Commands
Command
Description
dir disk0:
dir disk1:
show disk1:
FR-582
78-11740-02
show disk1:
To display flash or file system information for a disk located in slot 1, use the show disk1: command in
user EXEC or privileged EXEC mode.
show disk1: [all | filesys]
Syntax Description
all
filesys
Command Modes
User EXEC
Privileged EXEC
Command History
Release
Modification
11.3AA
12.2
12.3(7)T
This command was enhanced to display information about the ATA ROM
monitor library (monlib) file.
12.2(25)S
Usage Guidelines
The show disk1: command is supported only on platforms that have a disk file system. Use the show
disk01: command to display details about the files in a particular ATA PCMCIA flash disk memory card
located in slot 1.
For more information regarding file systems and flash cards, access the PCMCIA Filesystem
Compatibility Matrix and Filesystem Information document at the following URL:
http://www.cisco.com/en/US/partner/products/hw/routers/ps341/products_tech_note09186a00800a751
5.shtml
Note
The name of the ATA monlib file may contain a platform name that does not match the platform that you
are using. Different platforms may have a similar name or the same name for their ATA monlib file.
FR-583
Examples
The following examples show displays of information about the flash disks or file system information
for a disk. The output is self-explanatory.
c7200# show disk1:
-#- --length-- -----date/time------ path
1
29505176 Feb 27 2006 17:56:52 +00:00 c7200-jk9o3s-mz.124-6.T
2
32768 Feb 24 2006 13:30:30 +00:00 file1.log
34738176 bytes available (29540352 bytes used)
c7200# show disk1: all
-#- --length-- -----date/time------ path
1
29505176 Feb 27 2006 17:56:52 +00:00 c7200-jk9o3s-mz.124-6.T
2
32768 Feb 24 2006 13:30:30 +00:00 file1.log
34738176 bytes available (29540352 bytes used)
******** ATA Flash Card Geometry/Format Info ********
ATA CARD GEOMETRY
Number of Heads:
Number of Cylinders
Sectors per Cylinder
Sector Size
Total Sectors
4
984
32
512
125952
62
8
15693
125812
232
108
264
4
984
32
512
125952
62
8
15693
125812
232
FR-584
78-11740-02
108
264
Related Commands
Command
Description
dir disk0:
dir disk1:
show disk0:
FR-585
show environment
To display temperature, voltage, and blower information on the Cisco 7000 series, Cisco 7200 series,
Cisco 7500 series routers, Cisco AS5300 series Access Servers, and Cisco 12000 series Gigabit Switch
Routers (GSRs), use the show environment privileged EXEC command.
show environment [alarms | all | fans | hardware | last | leds | power-supply | table |
temperatures | voltages]
Note
Syntax Description
alarms
all
fans
hardware
last
leds
(Optional) Displays the status of the MBus LEDs on the clock and scheduler
cards and switch fabric cards.
power-supply
table
temperature
voltages
Defaults
Command Modes
Privileged EXEC
CommandHistory
Release
Modification
10.0
11.2 GS
11.3(6)AA
This command was expanded to monitor the RPS and board temperature for
the Cisco AS5300 platform, Cisco 3600 Series routers, Cisco 7200 series
routers, and the Cisco 12000 series routers.
FR-586
78-11740-02
Usage Guidelines
Once a minute a routine is run that gets environmental measurements from sensors and stores the output
into a buffer. This buffer is displayed on the console when the show environment command is entered.
If a measurement exceeds desired margins, but has not exceeded fatal margins, a warning message is
printed to the system console. The system software queries the sensors for measurements once a minute,
but warnings for a given test point are printed at most once every hour for sensor readings in the warning
range and once every 5 minutes for sensor readings in the critical range. If a measurement is out of line
within these time segments, an automatic warning message appears on the console. As noted, you can
query the environmental status with the show environment command at any time to determine whether
a measurement is at the warning or critical tolerance.
If a shutdown occurs because of detection of fatal environmental margins, the last measured value from
each sensor is stored in internal nonvolatile memory.
For environmental specifications, refer to the hardware installation and configuration publication for
your individual chassis.
If the Cisco 12000 series exceeds environmental conditions, a message similar to the following is
displayed on the console:
%GSR_ENV-2-WARNING: Slot 3 Hot Sensor Temperature exceeds 40 deg C;
Check cooling systems
Note
Blower temperatures that exceed environmental conditions do not generate a warning message.
You can also enable Simple Network Management Protocol (SNMP) notifications (traps or informs) to
alert a network management system (NMS) when environmental thresholds are reached using the
snmp-server enable traps envmon and snmp-server host global configuration commands.
Whenever Cisco IOS software detects a failure or recovery event from the DRPS unit, it sends an SNMP
trap to the configured SNMP server. Unlike console messages, only one SNMP trap is sent when the
failure event is first detected. Another trap is sent when the recovery is detected.
Cisco AS5300 DRPS software reuses the MIB attributes and traps defined in CISCO-ENVMON-MIB
and CISCO-ACCESS-ENVMON-MIB. CISCO-ENVMON-MIB is supported by all Cisco routers with
RPS units, and CISCO-ACCESS-ENVMON-MIB is supported by the Cisco 3600 series routers.
A power supply trap defined in CISCO-ENVMON-MIB is sent when a failure is detected and when a
failure recovery occurs for the following events: input voltage fail, DC output voltage fail, thermal fail,
and multiple failure events.
A fan failure trap defined in CISCO-ENVMON-MIB is sent when a fan failure or recovery event is
detected by Cisco IOS software.
A temperature trap defined in CISCO-ACCESS-ENVMON-MIB is sent when a board overtemperature
condition is detected by Cisco IOS software.
CISCO-ACCESS-ENVMON-MIB also defines an overvoltage trap. A similar trap is defined in
CISCO-ENVMON-MIB, but it requires the ciscoEnvMonVoltageStatusValue in varbinds. This value
indicates the current value of the voltage in the RPS. With Cisco AS5300 RPS units, the current voltage
value is not sent to the motherboard.
CISCO-ENVMON-MIB is extended to add a new enumerated value, internalRedundant(5), for MIB
attribute ciscoEnvMonSupplySource. This is used to identify a RPS unit.
FR-587
Examples
In the following example, the typical show environment display is shown when no warning conditions
are in the system for the Cisco 7000 series and Cisco 7200 series routers. This information may vary
slightly depending on the platform you are using. The date and time of the query are displayed, along
with the data refresh information and a message indicating that there are no warning conditions.
Router> show environment
Environmental Statistics
Environmental status as of 13:17:39 UTC Thu Jun 6 1996
Data is 7 second(s) old, refresh in 53 second(s)
All Environmental Measurements are within specifications
Field
Description
Status message
The following are examples of messages that display on the system console when a measurement has
exceeded an acceptable margin:
ENVIRONMENTAL WARNING: Air flow appears marginal.
ENVIRONMENTAL WARNING: Internal temperature measured 41.3(C)
ENVIRONMENTAL WARNING: +5 volt testpoint measured 5.310(V)
The system displays the following message if voltage or temperature exceed maximum margins:
SHUTDOWN: air flow problem
In the following example, there have been two intermittent power failures since a router was turned on,
and the lower power supply is not functioning. The last intermittent power failure occurred on Monday,
June 10, 1996, at 11:07 p.m.
7000# show environment all
Environmental Statistics
Environmental status as of 23:19:47 UTC Wed Jun 12 1996
Data is 6 second(s) old, refresh in 54 second(s)
WARNING: Lower Power Supply is NON-OPERATIONAL
Lower Power Supply:700W, OFF
Intermittent Powerfail(s): 2
+12
+5
-12
+24
volts
volts
volts
volts
measured
measured
measured
measured
at 12.05(V)
at
4.96(V)
at -12.05(V)
at 23.80(V)
FR-588
78-11740-02
Field
Description
WARNING:
Intermittent Powerfail(s)
voltage specifications
The following example is for the Cisco 7000 series router. The router retrieves the environmental
statistics at the time of the last shutdown. In this example, the last shutdown was Friday, May 19, 1995,
at 12:40 p.m., so the environmental statistics at that time are displayed.
Router# show environment last
Environmental Statistics
Environmental status as of 14:47:00 UTC Sun May 21 1995
Data is 6 second(s) old, refresh in 54 second(s)
WARNING: Upper Power Supply is NON-OPERATIONAL
LAST Environmental Statistics
Environmental status as of 12:40:00 UTC Fri May 19 1995
Lower Power Supply: 700W, ON
Upper Power Supply: 700W, OFF
No Intermittent Powerfails
+12
+5
-12
+24
volts
volts
volts
volts
measured
measured
measured
measured
at 12.05(V)
at
4.98(V)
at -12.00(V)
at 23.80(V)
Field
Description
FR-589
Table 74
show environment last Field Descriptions for the Cisco 7000 (continued)
Field
Description
WARNING:
10.20
4.74
-10.20
20.00
12.05(V)
4.98(V)
-12.05(V)
24.00(V)
13.80
5.26
-13.80
28.00
Temperature Parameters:
SENSE
WARNING
NORMAL
WARNING
CRITICAL
SHUTDOWN
-------|-------------|------------|-------------|--------------|----------Airflow
Inlet
10
10
60
39
41(C)
70
46
73(C)
88
64
show environment Field Descriptions for the Cisco 7000 Series Router
Field
Description
SENSE (Temperature
Parameters)
Air being measured. Inlet measures the air coming in, and Airflow
measures the temperature of the air inside the chassis.
WARNING
FR-590
78-11740-02
Table 75
show environment Field Descriptions for the Cisco 7000 (continued)Series Router
Field
Description
NORMAL
CRITICAL
SHUTDOWN
The system displays the following message if the voltage or temperature enters the Warning range:
%ENVM-4-ENVWARN: Chassis outlet 3 measured at 55C/131F
The system displays the following message if the voltage or temperature enters the Critical range:
%ENVM-2-ENVCRIT: +3.45 V measured at +3.65 V
The system displays the following message if the voltage or temperature exceeds the maximum margins:
%ENVM-0-SHUTDOWN: Environmental Monitor initiated shutdown
The following message is sent to the console if a power supply has been inserted or removed from the
system. This message relates only to systems that have two power supplies.
%ENVM-6-PSCHANGE: Power Supply 1 changed from Zytek AC Power Supply to removed
The following message is sent to the console if a power supply has been powered on or off. In the case
of the power supply being shut off, this message can be due to the user shutting off the power supply or
to a failed power supply. This message relates only to systems that have two power supplies.
%ENVM-6-PSLEV: Power Supply 1 state changed from normal to shutdown
The following is sample output from the show environment all command on the Cisco 7200 series
router when there is a voltage warning condition in the system:
7200# show environment all
Power Supplies:
Power supply 1 is unknown. Unit is off.
Power supply 2 is Zytek AC Power Supply. Unit is on.
Temperature readings:
chassis inlet
chassis outlet 1
chassis outlet 2
chassis outlet 3
Voltage readings:
+3.45 V measured
+5.15 V measured
+12.15 measured
-11.95 measured
measured
measured
measured
measured
at
at
at
at
at
at
at
at
25C/77F
29C/84F
36C/96F
44C/111F
FR-591
Table 76
show environment all Field Descriptions for the Cisco 7200 Series Router
Field
Description
Power Supplies:
Temperature readings:
Voltage readings:
The following example is for the Cisco 7200 series router. This example shows the measurements
immediately before the last shutdown and the reason for the last shutdown (if appropriate).
7200# show environment last
chassis
chassis
chassis
chassis
+3.3 V
+5.0 V
+12.0 V
-12.0 V
inlet
outlet 1
outlet 2
outlet 3
previously
previously
previously
previously
previously
previously
previously
previously
measured
measured
measured
measured
measured
measured
measured
measured
at
at
at
at
at
at
at
at
27C/80F
31C/87F
37C/98F
45C/113F
4.02
4.92
12.65
11.71
show environment last Field Descriptions for the Cisco 7200 Series Router
Field
Description
chassis inlet
chassis outlet
voltages
The following example is for the Cisco 7200 series router. This information lists the temperature and
voltage shutdown thresholds for each sensor.
7200# show environment table
Sample Point
LowCritical
chassis inlet
chassis outlet 1
chassis outlet 2
chassis outlet 3
+3.45 V
+2.76
+5.15 V
+4.10
+12.15 V
+9.72
-11.95 V
-8.37
Shutdown system at 70C/158F
LowWarning
+3.10
+4.61
+10.91
-9.57
HighWarning
40C/104F
43C/109F
75C/167F
55C/131F
+3.80
+5.67
+13.37
-14.34
HighCritical
50C/122F
53C/127F
75C/167F
65C/149F
+4.14
+6.17
+14.60
-15.53
FR-592
78-11740-02
Table 78
show environment table Field Descriptions for the Cisco 7200 Series Router
Field
Description
Sample Point
LowCritical
LowWarning
HighWarning
HighCritical
Shutdown system at
The sample output for the Cisco 7500 series routers may vary depending on the specific model (for
example, the Cisco 7513 router). The following is sample output from the show environment all
command on the Cisco 7500 series router:
7500# show environment all
Arbiter type 1, backplane type 7513 (id 2)
Power supply #1 is 1200W AC (id 1), power supply #2 is removed (id 7)
Active fault conditions: none
Fan transfer point: 100%
Active trip points: Restart_Inhibit
15 of 15 soft shutdowns remaining before hard shutdown
Dbus slots:
card
RSP(6)
RSP(7)
1
0123456789012
X
XX
X
inlet
35C/95F
35C/95F
hotpoint
47C/116F
43C/109F
exhaust
40C/104F
39C/102F
+5V Current
+12V Current
-12V Current
output is 378 W
FR-593
Table 79
Field
Description
Arbiter type 1
Power supply
15 of 15 soft shutdowns remaining When the temperature increases above the board shutdown
level, a soft shutdown occurs (that is, the cards are shut down,
and the power supplies, fans, and CI continue to operate). When
the system cools to the restart level, the system restarts. The
system counts the number of times this occurs and keeps the
up/down cycle from continuing forever. When the counter
reaches zero, the system performs a hard shutdown, which
requires a power cycle to recover. The soft shutdown counter is
reset to its maximum value after the system has been up for
6 hours.
Dbus slots:
PS1
The following example is for the Cisco 7500 series router. This example shows the measurements
immediately before the last shutdown.
7500# show environment last
RSP(4) Inlet
RSP(4) Hotpoint
RSP(4) Exhaust
+12 Voltage
+5 Voltage
-12 Voltage
+24 Voltage
previously
previously
previously
previously
previously
previously
previously
measured
measured
measured
measured
measured
measured
measured
at
at
at
at
at
at
at
37C/98F
46C/114F
52C/125F
12.26
5.17
-12.03
23.78
FR-594
78-11740-02
Table 80
show environment last Field Descriptions for the Cisco 7500 Series Router
Field
Description
Voltages
The following example is for the Cisco 7500 series router. This information lists the temperature and
voltage thresholds for each sensor. These thresholds indicate when system messages occur. There are
two level of messages: warning and critical.
7500# show environment table
Sample Point
LowCritical
LowWarning
RSP(4) Inlet
RSP(4) Hotpoint
RSP(4) Exhaust
+12 Voltage
10.90
11.61
+5 Voltage
4.61
4.94
-12 Voltage
-10.15
-10.76
+24 Voltage
20.38
21.51
2.5 Reference
2.43
Shutdown boards at
70C/158F
Shutdown power supplies at
76C/168F
Restart after shutdown below 40C/104F
HighWarning
44C/111F
54C/129F
HighCritical
50C/122F
60C/140F
12.82
5.46
-13.25
26.42
2.51
13.38
5.70
-13.86
27.65
show environment table Field Descriptions for the Cisco 7500 Series Router
Field
Description
Sample Point
LowCritical
LowWarning
HighWarning
HighCritical
Shutdown boards at
FR-595
In the following example, how keywords and options are limited according to the physical
characteristics of the system is shown:
as5300# show environment ?
all
last
table
|
<cr>
The following examples are for the Cisco 12000 series GSRs.
The following is sample output from the show environment command for a Cisco 12012 router. Slots
0 through 11 are the line cards, slots 16 and 17 are the clock and scheduler cards, slots 18 through 20 are
the switch fabric cards, slots 24 through 26 are the power supplies, and slots 28 and 29 are the blowers.
An NA in the table means that no values were returned. In some cases it is because the equipment is
not supported for that environmental parameter (for example, the power supply and blowers in slots 24,
26, 28, and 29 do not have a 3V power supply, so an NA is displayed).
Router# show environment
Slot #
0
2
4
7
9
11
16
17
18
19
20
24
26
28
29
Slot #
24
26
Slot #
28
29
Router#
3V
(mv)
3300
3296
3280
3280
3292
3288
3308
3292
3304
3300
3304
NA
NA
NA
NA
5V
(mv)
4992
4976
4992
4984
4968
4992
NA
NA
NA
NA
NA
5536
5544
NA
NA
48V
(Volt)
46
46
AMP_48
(Amp)
12
19
Fan 0
(RPM)
2160
2130
Fan 1
(RPM)
2190
2190
Inlet Sensor
(deg C)
37.0
33.0
31.5
32.0
31.5
30.5
38.0
36.5
35.0
33.5
34.0
31.5
31.5
NA
NA
Fan 2
(RPM)
2160
2070
Table 82 describes the significant fields shown and lists the equipment supported by each environmental
parameter. NA indicates that the reading could not be obtained, so the command should be again.
FR-596
78-11740-02
Table 82
show environment Field Descriptions for the Cisco 12000 Series Routers
Field
Description
Slot #
Slot number of the equipment. On the Cisco 12012 router, slots 0 through 11
are the line cards, slots 16 and 17 are the clock and scheduler cards, slots 18
through 20 are the switch fabric cards, slots 24 through 27 are the power
supplies, and slots 28 and 29 are the blowers.
3V (mv)
Measures the 3v power supply on the card. The 3v power supply is on the line
cards, GRP card, clock and scheduler cards, and switch fabric cards.
5V (mv)
Measures the 5v power supply on the card. The 5v power supply is on the line
cards, GRP card, and power supplies.
MBUS 5V (mv)
Measures the temperature at the hot sensor on the card. The hot sensor is on the
line cards, GRP card, clock and scheduler cards, switch fabric cards, and
blowers.
Inlet Sensor (deg C) Measures the current inlet temperature on the card. The inlet sensor is on the
line cards, GRP card, clock and scheduler cards, switch fabric cards, and power
supplies.
48V (Volt)
AMP_48 (Amp)
The following is sample output from the show environment all command for the Cisco 12008 router.
Slots 0 through 7 are the line cards, slots 16 and 17 are the clock scheduler cards (the clock scheduler
cards control the fans), slots 18 through 20 are the switch fabric cards, and slots 24 and 26 are the power
supplies. The Cisco 12008 router does not support slots 25, 27, 28, and 29. An NA in the table means
that no values were returned. In some cases it is because the equipment is not supported for that
environmental parameter (for example, the power supplies in slots 24 and 26 do not have a hot sensor,
so an NA is displayed).
Router# show environment all
Slot #
2
5
16
18
19
24
26
Slot #
2
5
16
18
19
Slot #
Hot Sensor
(deg C)
31.0
33.5
25.5
22.0
22.5
NA
NA
Inlet Sensor
(deg C)
22.0
26.5
21.5
21.0
21.0
29.5
24.5
3V
(mv)
3292
3292
3272
3300
3316
5V
(mv)
5008
5000
NA
NA
NA
MBUS 5V
(mv)
5136
5128
5128
5128
5128
5V
(mv)
MBUS 5V 48V
(mv)
(Volt)
AMP_48
(Amp)
FR-597
24
26
0
5544
5096
5144
3
47
0
3
Slot #
16
Fan Information
Voltage 16V Speed slow: Main Fans Ok Power Supply fans Ok
Alarm Indicators
No alarms
Slot #
16
18
19
24
26
The following is sample output from the show environment table command for a Cisco 12012 router.
The show environment table command lists the warning, critical, and shutdown limits on your system
and includes the GRP card and line cards (slots 0 to 15), clock and scheduler cards (slots 16 and 17),
switch fabric cards (slots 18 to 20), and blowers.
Router# show environment table
Hot Sensor Temperature Limits (deg C):
Warning Critical Shutdown
GRP/GLC (Slots 0-15)
40
46
57
CSC
(Slots 16-17)
46
51
65
SFC
(Slots 18-20)
41
46
60
Inlet Sensor Temperature Limits (deg C):
Warning Critical Shutdown
GRP/GLC (Slots 0-15)
35
40
52
CSC
(Slots 16-17)
40
45
59
SFC
(Slots 18-20)
37
42
54
3V Ranges (mv):
Warning
Below
Above
3200
3400
3200
3400
3200
3400
Critical
Below Above
3100
3500
3100
3500
3100
3500
Shutdown
Below Above
3050
3550
3050
3550
3050
3550
Warning
Below
Above
4850
5150
Critical
Below Above
4750
5250
Shutdown
Below Above
4680
5320
Warning
Below
Above
5000
5250
4820
5150
5000
5250
Critical
Below Above
4900
5350
4720
5250
4900
5350
Shutdown
Below Above
4750
5450
4750
5450
4750
5450
5V Ranges (mv):
Fan 0
Fan 1
Fan 2
Warning
Below
1000
1000
1000
Critical
Below
750
750
750
FR-598
78-11740-02
Bottom Blower:
Warning
Below
1000
1000
1000
Fan 0
Fan 1
Fan 2
Critical
Below
750
750
750
The following is sample output from the show environment leds command for a Cisco 12012 router.
The show environment leds command lists the status of the MBus LEDs on the clock, scheduler, and
the switch fabric cards.
Router# show environment leds
16
18
19
20
Related Commands
leds
leds
leds
leds
Mbus
Mbus
Mbus
Mbus
OK
OK
OK
OK
Command
Description
FR-599
show gsr
To display hardware information on the Cisco 12000 series Gigabit Switch Routers (GSRs), use the
show gsr EXEC command.
show gsr [chassis-info [details]]
Syntax Description
chassis-info
details
Command Modes
EXEC
CommandHistory
Release
Modification
11.2 GS
This command was added to support the Cisco 12000 series GSRs.
Usage Guidelines
Use this command to determine the type of hardware installed in your Cisco 12000 series GSR router.
Examples
The following is sample output from the show gsr command for a Cisco 12012 router. This command
shows the type and state of the card installed in the slot.
Router# show gsr
Slot 0
type
state
Slot 7 type
state
Slot 16 type
state
=
=
=
=
=
=
Route Processor
IOS Running MASTER
1 Port Packet Over SONET OC-12c/STM-4c
Card Powered
Clock Scheduler Card
Card Powered PRIMARY CLOCK
The following is sample output from the show gsr chassis-info command for a Cisco 12012 router:
Router# show gsr chassis-info
Backplane NVRAM [version 0x20] Contents Chassis: type 12012 Fab Ver: 1
Chassis S/N: ZQ24CS3WT86MGVHL
PCA: 800-3015-1 rev: A0 dev: 257 HW ver: 1.0
Backplane S/N: A109EXPR75FUNYJK
MAC Addr: base 0000.EAB2.34FF block size: 1024
RMA Number: 0x5F-0x2D-0x44 code: 0x01 hist: 0x1A
FR-600
78-11740-02
Syntax Description
Command Modes
EXEC
CommandHistory
Release
Modification
11.2
Usage Guidelines
This command displays information about the CPU interface, DRAM/device address space, device
parameters, direct memory access (DMA) channels, timers and counters, and protocol control
information (PCI) internal registers. The information is generally useful for diagnostic tasks performed
by technical support only.
Examples
The following is a partial sample output for the show gt64010 command:
Router# show gt64010
GT64010 Channel 0 DMA:
dma_list=0x6088C3EC, dma_ring=0x4B018480, dma_entries=256
dma_free=0x6088CECC, dma_reqt=0x6088CECC, dma_done=0x6088CECC
thread=0x6088CEAC, thread_end=0x6088CEAC
backup_thread=0x0, backup_thread_end=0x0
dma_working=0, dma_complete=6231, post_coalesce_frames=6231
exhausted_dma_entries=0, post_coalesce_callback=6231
GT64010 Register Dump: Registers at 0xB4000000
CPU Interface:
cpu_interface_conf
:
addr_decode_err
:
Processor Address Space
ras10_low
:
ras10_high
:
ras32_low
:
ras32_high
:
cs20_low
:
cs20_high
:
cs3_boot_low
:
cs3_boot_high
:
pci_io_low
:
pci_io_high
:
pci_mem_low
:
pci_mem_high
:
0x80030000
0xFFFFFFFF
:
0x00000000
0x07000000
0x08000000
0x0F000000
0xD0000000
0x74000000
0xF8000000
0x7E000000
0x00080000
0x00000000
0x00020000
0x7F000000
(b/s 0x00000380)
(b/s 0xFFFFFFFF)
(b/s
(b/s
(b/s
(b/s
(b/s
(b/s
(b/s
(b/s
(b/s
(b/s
(b/s
(b/s
0x00000000)
0x00000007)
0x00000008)
0x0000000F)
0x000000D0)
0x00000074)
0x000000F8)
0x0000007E)
0x00000800)
0x00000000)
0x00000200)
0x0000007F)
FR-601
internal_spc_decode
bus_err_low
bus_err_high
.
.
.
FR-602
78-11740-02
show logging
To display the state of system logging (syslog) and the contents of the standard system logging message
buffer,, use the show logging privileged EXEC command.
show logging [slot slot-number | summary]
Syntax Description
slot slot-number
(Optional) Displays information in the syslog history table for a specific line
card. Slot numbers range from 0 to 11 for the Cisco 12012 router and 0 to 7
for the Cisco 12008 router.
summary
Command Modes
Privileged EXEC
Command History
Release
Modification
10.0
11.2 GS
The slot and summary keywords were added for the Cisco 12000 family.
Usage Guidelines
Note
Examples
This command displays the state of syslog error and event logging, including host addresses, and
whether console logging is enabled. This command also displays Simple Network Management Protocol
(SNMP) configuration parameters and protocol activity.
Within the context of the CLI, syslog is an abbreviation for the system message logging process in
Cisco IOS software. Syslog is alsp used to identify the messages generated, as in "syslog messages."
Technically, the term "syslog" refers only to the process of logging messages to a remote host or hosts,
but is commonly used to refer to all Cisco IOS system logging processes.
FR-603
Table 83
Field
Description
Syslog logging
When enabled, system logging messages are sent to a UNIX host that acts as a
syslog server; that is, syslog messages are saved to the specified server.
Console logging
Minimum level of severity required for a log message to be sent to the console.
If disabled, the word disabled is displayed.
Monitor logging
Trap logging
SNMP logging
The following is sample output from the show logging summary command for the Cisco 12012 router.
A number in the column indicates that the syslog contains that many messages for the line card. For
example, line card in slot 9 has 1 system message, 4 warning messages, and 47 notification messages.
Router# show logging summary
+-----+-------+-------+-------+-------+-------+-------+-------+-------+
SLOT | EMERG | ALERT | CRIT | ERROR |WARNING| NOTICE| INFO | DEBUG |
+-----+-------+-------+-------+-------+-------+-------+-------+-------+
|* 0* |
. |
. |
. |
. |
. |
. |
. |
. |
| 1 |
|
|
|
|
|
|
|
|
| 2 |
|
|
|
1 |
4 |
45 |
|
|
| 3 |
|
|
|
|
|
|
|
|
| 4 |
|
|
|
5 |
4 |
54 |
|
|
| 5 |
|
|
|
|
|
|
|
|
| 6 |
|
|
|
|
|
|
|
|
| 7 |
|
|
|
17 |
4 |
48 |
|
|
| 8 |
|
|
|
|
|
|
|
|
| 9 |
|
|
|
1 |
4 |
47 |
|
|
| 10 |
|
|
|
|
|
|
|
|
| 11 |
|
|
|
12 |
4 |
65 |
|
|
+-----+-------+-------+-------+-------+-------+-------+-------+-------+
Router#
Field
Description
SLOT
Indicates the slot number of the line card. An asterisk next to the slot number indicates
the GRP card whose error message counts are not displayed. For information on the
GRP card, use the show logging command.
EMERG
ALERT
CRIT
ERROR
WARNING
FR-604
78-11740-02
Table 84
Related Commands
Field
Description
NOTIFICE
INFO
DEBUG
Command
Description
clear logging
Changes the number of syslog messages stored in the history table of the
router.
logging linecard
Logs messages to an internal buffer on a line card and limits the logging
messages displayed on terminal lines other than the console line to messages
with a level at or above level.
FR-605
Syntax Description
Command Modes
Privileged EXEC
CommandHistory
Release
Modification
10.0
Usage Guidelines
This command displays information about the syslog history table, such as the table size, the status of
messages, and text of messages stored in the table. Messages stored in the table are governed by the
logging history global configuration command.
Examples
The following example shows sample output from the show logging history command. In this example,
notifications of severity level 5 (notifications) through severity level 0 (emergencies) are configured to
be written to the logging history table.
Router# show logging history
Syslog History Table: 1 maximum table entries,
saving level notifications or higher
0 messages ignored, 0 dropped, 15 table entries flushed,
SNMP notifications not enabled
entry number 16: SYS-5-CONFIG_I
Configured from console by console
timestamp: 1110
Router#
Field
Description
saving level notifications <x> or Level of messages that are stored in the history table and sent
higher
to the SNMP server (if SNMP notification is enabled). The
severity level can be configured with the logging history
command.
FR-606
78-11740-02
Table 85
Related
Commands
Field
Description
messages ignored
dropped
SNMP notifications
entry number:
timestamp
Time, based on the up time of the router, that the message was
generated.
Command
Description
clear logging
logging history
Changes the number of syslog messages that can be stored in the history
table.
logging linecard
snmp-server enable traps The [no] snmp-server enable traps syslog form of this command
controls (enables or disables) the sending of system-logging messages
to a network management station.
FR-607
show memory
To display memory utilization statistics, use the show memory command in User or Privileged EXEC
mode.
show memory [ start-address [end-address] | [ processor | io | multibus] [free] | summary ]
Syntax Description
Defaults
start-address
[end-address]
processor
io
multibus
free
(Optional) Displays only free memory statistics for the specified memory type.
summary
If a memory address is not specified, statistics for all memory addresses are displayed.
If a memory type (processor | io | multibus) is not specified, statistics for all memory types present are
displayed.
Command Modes
EXEC
Command History
Release
Modification
10.0
Usage Guidelines
Tip
This command prints detailed memory information to the screen. This information is intended for use
by Cisco technical support personnel.
This command can generate a large amount of output. Use the Break key sequence (often Crtl+z) at the
--More-- prompt to return to the CLI prompt.
This command first displays how much memory is being used on the router by memory pool (processor,
shared I/O memory, and, potentially, SRAM). Then this command displays, for each memory pool, a
complete list of all blocks.
Examples
FR-608
78-11740-02
Processor
Head
B0EE38
Total(b)
5181896
Processor memory
Bytes Prev.
Next
1056 0
B0F280
2656 B0EE38
B0FD08
2520 B0F280
B10708
2000 B0FD08
B10F00
512 B10708
B11128
2000 B10F00
B11920
44 B11128
B11974
1056 B11920
B11DBC
84 B11974
B11E38
84 B11DBC
B11EB4
84 B11E38
B11F30
84 B11EB4
B11FAC
Address
B0EE38
B0F280
B0FD08
B10708
B10F00
B11128
B11920
B11974
B11DBC
B11E38
B11EB4
B11F30
Router#
Used(b)
2210036
Ref
1
1
1
1
1
1
1
1
1
1
1
1
Free(b)
2971860
PrevF
NextF
Lowest(b) Largest(b)
2692456
2845368
Alloc PC
18F132
18F132
141384
14353C
14356C
1A110E
970DE8
18F132
19ABCE
19ABCE
19ABCE
19ABCE
What
List Elements
List Headers
TTY data
TTY Input Buf
TTY Output Buf
Interrupt Stack
*Init*
messages
Watched Boolean
Watched Boolean
Watched Boolean
Watched Boolean
The following is sample output from the show memory free command:
Router# show memory free
Processor
Address
CEB844
D35ED4
D27AE8
D0A8F4
B59EF0
Head
B0EE38
Total(b)
5181896
Processor memory
Bytes Prev.
Next
24
Free list 1
32 CEB7A4
CEB88C
52
Free list 2
72
Free list 3
76
Free list 4
80
Free list 5
80 D35E30
D35F4C
80 D27A48
D27B60
88
Free list 6
100
Free list 7
100 D0A8B0
D0A980
104
Free list 8
108 B59E8C
B59F84
Used(b)
2210076
Ref
Free(b)
2971820
PrevF
NextF
Lowest(b) Largest(b)
2692456
2845368
Alloc PC
What
96B894
SSE Manager
0
0
0
D35ED4
D27AE8
0
96B894
22585E
SSE Manager
SSE Manager
2258DA
SSE Manager
2258DA
(fragment)
The display of show memory free contains the same types of information as the show memory display,
except that only free memory is displayed, and the information is displayed in order for each free list.
The first section of the display includes summary statistics about the activities of the system memory
allocator. Table 86 describes the significant fields shown in the first section of the display.
Table 86
Field
Description
Head
Total(b)
Used(b)
Free(b)
FR-609
Table 86
Field
Description
Lowest(b)
Largest(b)
The second section of the display is a block-by-block listing of memory use. Table 87 describes the
significant fields shown in the second section of the display.
Table 87
Field
Description
Address
Bytes
Prev.
Next
Ref
Reference count for that memory block, indicating how many different processes are
using that block of memory.
PrevF
NextF
Alloc PC
Allocating Process Call Address of the system call that allocated the block.
What
Name of process that owns the block, or (fragment) if the block is a fragment, or
(coalesced) if the block was coalesced from adjacent free blocks.
The show memory io command displays the free I/O memory blocks.
The following is sample output from the show memory io command:
Router# show memory io
Address
Bytes
6132DA0
59264
600DDEC
500
600FE68
376
6011D54
652
614FCA0
832
6177640 2657056
Total: 2723244
Prev.
6132664
600DA4C
600FAC8
60119B4
614F564
6172E90
Next
6141520
600DFE0
600FFE0
6011FEO
614FFE0
0
Ref
0
0
0
0
0
0
PrevF
0
6132DA0
600DDEC
600FE68
601FD54
614FCA0
NextF
600DDEC
600FE68
6011D54
6013D54
6177640
0
Alloc PC
3FCF0
0
0
0
0
0
What
*Packet Buffer*
The show memory summary command displays a summary of all memory pools and memory usage per
Alloc PC (address of the system call that allocated the block).
The following is partial sample output from the show memory summary command.
Size is the number of bytes in each block. Bytes is the total size for all blocks (Bytes equals the
Size value multiplied by the Blocks value). For a description of the other fields, see Table 20 and
Table 21.
Router# show memory summary
Processor
I/O
Head
8404A580
7C53000
Total(b)
64102816
3854336
Used(b)
10509276
2138224
Free(b)
53593540
1716112
Lowest(b)
52101448
1708432
Largest(b)
51007568
1716064
FR-610
78-11740-02
Processor memory
Alloc PC
Size
Blocks
0x2AB2
192
1
0x70EC
92
2
0xC916
128
50
0x76ADE
4500
1
0x76E84
4464
1
0x76EAC
692
1
0x77764
408
1
0x77776
116
1
0x777A2
408
1
0x777B2
116
1
0xA4600
24
3
0xD9B5C
52
1
.......................
0x0
0
3413
0x0
0
28
0x0
40
3441
0x0
0
3413
0x0
0
28
Related Commands
Bytes
192
184
6400
4500
4464
692
408
116
408
116
72
52
2072576
2971680
137640
2072576
2971680
What
IDB: Serial Info
Init
RIF Cache
XDI data
XDI data
XDI data
Init
Init
Init
Init
List
SSE Manager
Pool Summary
Pool Summary (Free Blocks)
Pool Summary(All Block Headers)
Memory Summary
Memory Summary (Free Blocks)
Command
Description
FR-611
Syntax Description
Command Modes
Privileged EXEC
Command History
Release
Modification
11.1(30)CC
12.0(4)XE
12.0(6)S
12.1(13)
Usage Guidelines
Use this command to determine if the router has experienced single-bit parity errors.
Examples
The following is sample output from the show memory ecc command from a 12000-series router
running Cisco IOS Release 12.0(23)S:
Router# show memory ecc
ECC Single Bit error log
-----------------------Single Bit error detected and corrected at 0x574F3640
- Occured 1 time(s)
- Whether a scrub was attempted at this address: Yes
- Syndrome of the last error at this address: 0xE9
- Error detected on a read-modify-write cycle ? No
- Address region classification: Unknown
- Address media classification : Read/Write Single Bit error detected and corrected at
0x56AB3760
- Occured 1 time(s)
- Whether a scrub was attempted at this address: Yes
- Syndrome of the last error at this address: 0x68
- Error detected on a read-modify-write cycle ? No
- Address region classification: Unknown
- Address media classification : Read/Write
Total Single Bit error(s) thus far: 2
FR-612
78-11740-02
Table 86 describes the significant fields shown in the first section of the display.
Table 88
Field
Description
Occured n time(s)
Whether a scrub was attempted at this address: Indicates whether a scrub has been performed.
Related Commands
Command
Description
show memory
FR-613
Syntax Description
allocating-process
dead
free
totals
Command Modes
Exec
Command History
Release
Modification
12.1
Usage Guidelines
The show memory fast command displays the statistics for the fast memory. Fast memory is another
name for processor memory, and is also known as cache memory. Cache memory is called fast
memory because the processor can generally access the local cache (traditionally stored on SRAM
positioned close to the processor) much more quickly than main (primary) memory.
Cache = fast memory closest to processor = processor memory
Primary Memory = the main memory below cache.
Note
Examples
The show memory fast command is a command alias for the show memory processor command. These
commands will generate the same output on most platforms.
The following example shows sample output from the show memory fast and the show memory
processor commands:
Router>show memory fast
Processor memory
Address
8404A580
841B6ECC
Elements
841BBD18
841BC320
841BD6D4
841BD72C
841BDD34
841BE33C
Bytes
Prev
Next Ref
PrevF
NextF Alloc PC what
0001493284 00000000 841B6ECC 000 0
84BADF88 815219D8 (coalesced)
0000020004 8404A580 841BBD18 001 -------- -------- 815DB094 Managed Chunk Queue
0000001504
0000005004
0000000048
0000001504
0000001504
0000001504
841B6ECC
841BBD18
841BC320
841BD6D4
841BD72C
841BDD34
841BC320
841BD6D4
841BD72C
841BDD34
841BE33C
841BE944
001
001
001
001
001
001
-------------------------------------------
-------------------------------------------
8159EAC4
8159EB04
81F2A614
815A9514
815A9540
815A95E4
List Elements
List Headers
*Init*
messages
Watched messages
Watched Semaphore
FR-614
78-11740-02
Watched Message
Watcher Message
Process Array
Prev
Next Ref
PrevF
NextF Alloc PC what
00000000 841B6ECC 000 0
84BADF88 815219D8 (coalesced)
8404A580 841BBD18 001 -------- -------- 815DB094 Managed Chunk Queue
841B6ECC
841BBD18
841BC320
841BD6D4
841BD72C
841BDD34
841BE33C
841BC320
841BD6D4
841BD72C
841BDD34
841BE33C
841BE944
841BEB64
001
001
001
001
001
001
001
--------------------------------------------------
--------------------------------------------------
8159EAC4
8159EB04
81F2A614
815A9514
815A9540
815A95E4
815A9630
List Elements
List Headers
*Init*
messages
Watched messages
Watched Semaphore
Watched Message
Watcher Message
Process Array
Router>
The following example shows sample output from the show memory fast allocating-process command,
followed by sample output from the show memory fast allocating-process totals command:
Prev
Next Ref
00000000 841B6ECC 000
8404A580 841BBD18 001
841B6ECC
841BBD18
841BC320
841BD6D4
841BD72C
841BDD34
841BE33C
841BE944
841BEB64
841BC320
841BD6D4
841BD72C
841BDD34
841BE33C
841BE944
841BEB64
841BF16C
841BF5A0
001
001
001
001
001
001
001
001
001
Alloc Proc
*Init*
Alloc PC
815219D8
815DB094
What
(coalesced)
Managed Chunk Queue
*Init*
*Init*
*Init*
*Init*
*Init*
*Init*
*Init*
*Init*
*Init*
8159EAC4
8159EB04
81F2A614
815A9514
815A9540
815A95E4
815A9630
815A9658
815A2B24
List Elements
List Headers
*Init*
messages
Watched messages
Watched Semaphore
Watched Message Queue
Watcher Message Queue
Process Array
Total
1194600
948680
Count
150
5
Name
Process Stack
pak subblock chunk
FR-615
0x819F1DE4
0x815C4FD4
0x815B5FDC
0x819F14DC
0x81A1E838
0x8153DFB8
0x82142438
0x82151E0C
0x819F1C8C
0x815A4858
0x8083DA44
524640
393480
351528
327900
327900
248136
133192
131116
118480
100048
97248
8
6
30
5
5
294
4
1
4
148
17
--More-<Ctrl+z>
The following example shows sample output from the show memory fast dead command:
Router#show memory fast dead
Processor memory
Address
Bytes
Prev
Next Ref
8498FC20 0000000028 8498FB90 8498FC64 001
------68
Router#show memory fast dead totals
PrevF
NextF Alloc PC
-------- -------- 81472B24
what
AAA MI SG NAME
Total
68
Count
1
Name
AAA MI SG NAME
Router#
FR-616
78-11740-02
Syntax Description
Command Modes
EXEC
Command History
Release
Modification
12.0(4)XE
12.0(7)T
This command was implemented in Cisco IOS Release 12.0T for the
Cisco 7500 series.
12.0(6)S
This command was implemented in Cisco IOS Release 12.0S for the
Cisco 7500 series.
12.1(1)E
This command was implemented in Cisco IOS Release 12.1E for the
Cisco 7500 series.
Usage Guidelines
For the show memory scan command to function, the memory scan feature must be enabled on the RSP
using the memory scan global configuraiton mode command.
Examples
If errors are detected in the system, the show memory scan command generates an error report. In the
following example, memory scan detected a parity error:
Router# show memory scan
Memory scan is on.
Total Parity Errors 1.
Address
BlockPtr
BlckSize
6115ABCD 60D5D090
9517A4
Disposit
Scrubed
Region Timestamp
Local 16:57:09 UTC Thu
Mar 18
FR-617
Table 89
Field
Description
Address
BlockPtr
BlckSize
Disposit
Region
Timestamp
Related Commands
IBSSimage BSS
IDataimagedata
ITextimagetext
localheap
Command
Description
memory scan
FR-618
78-11740-02
show pci
To display information about the peripheral component interconnect (PCI) hardware registers or bridge
registers for the Cisco 7200 series routers, use the show pci EXEC command.
show pci {hardware | bridge [register]}
Syntax Description
hardware
bridge
register
Command Modes
EXEC
Command History
Release
Modification
11.2
Usage Guidelines
Note
Examples
The output of this command is generally useful for diagnostic tasks performed by technical support only.
The show pci hardware EXEC command displays a substantial amount of information.
The following is sample output for the PCI bridge register 1 on a Cisco 7200 series router:
Router# show pci bridge 1
Bridge 4, Port Adaptor 1, Handle=1
DEC21050 bridge chip, config=0x0
(0x00): cfid
= 0x00011011
(0x04): cfcs
= 0x02800147
(0x08): cfccid = 0x06040002
(0x0C): cfpmlt = 0x00010010
(0x18):
(0x1C):
(0x20):
(0x24):
cfsmlt
cfsis
cfmla
cfpmla
=
=
=
=
0x18050504
0x22805050
0x48F04880
0x00004880
(0x3C): cfbc
= 0x00000000
(0x40): cfseed = 0x00100000
(0x44): cfstwt = 0x00008020
The following is partial sample output for the PCI hardware register, which also includes information on
all the PCI bridge registers on a Cisco 7200 series router:
Router# show pci hardware
FR-619
cfsmlt
cfsis
cfmla
cfpmla
=
=
=
=
0x18000100
0x02809050
0x4AF04880
0x4BF04B00
(0x3C): cfbc
= 0x00000000
(0x40): cfseed = 0x00100000
(0x44): cfstwt = 0x00008020
.
.
.
FR-620
78-11740-02
Syntax Description
Command Modes
EXEC
CommandHistory
Release
Modification
11.2
Usage Guidelines
The output of this command is generally useful for diagnostic tasks performed by technical support only:
router# show pci hardware
hardware PCI hardware registers
Each device on the PCI bus is assigned a PCI device number.
C2600, device numbers are as follows:
Device
0
1
2
3
4
5
6
7
8-14
15
Examples
For the
Device number
First LAN device
Second LAN device
AIM device (if present)
Not presently used
Port module - first PCI device
Port module - second PCI device
Port module - third PCI device
Port module - fourth PCI device
Not presently used
Xilinx PCI bridge
The following is partial sample output for the PCI hardware register, which also includes information on
all the PCI bridge registers. Table 90 describes the significant fields shown in the display.
router# show pci hardware
XILINX Host-PCI Bridge Registers:
Vendor / Device ID: 0x401310EE
Status / Command: 0x040001C6
PCI Slave Base Reg 0: 0x00000000
PCI Slave Base Reg 1: 0x04000000
FR-621
Table 90
Field
Description
Device/Vendor ID
Status/Command
The base address of PCI Target Region 0 for the Host-PCI bridge.
This region is used for Big-Endian transfers between PCI devices
and memory.
The base address of PCI Target Region 1 for the Host-PCI bridge.
This region is used for Little-Endian transfers between PCI devices
and memory.
FR-622
78-11740-02
show processes
To display information about the active processes, use the show processes command in EXEC mode.
show processes [history]
Syntax Description
history
Command Modes
Privileged EXEC
Command History
Release
Modification
10.0
12.2(2)T
Examples
The following is sample output from the show processes history command:
Router# show process history
PID Exectime(ms) Caller PC Process Name
3
12 0x0
Exec
16
0 0x603F4DEC GraphIt
21
0 0x603CFEF4 TTY Background
22
0 0x6042FD7C Per-Second Jobs
67
0 0x6015CD38 SMT input
39
0 0x60178804 FBM Timer
FR-623
16
0
21
0
22
0
16
0
21
0
22
0
67
0
39
0
24
0
11
0
69
0
69
0
51
0
69
0
36
0
69
0
--More-PID Exectime(ms)
16
0
21
0
22
0
34
0
19
0
36
0
12
0
69
0
44
0
65
4
25
8
16
0
21
0
22
0
67
0
39
0
2
0
16
0
21
0
22
0
16
0
21
0
22
0
--More-. . .
0x603F4DEC
0x603CFEF4
0x6042FD7C
0x603F4DEC
0x603CFEF4
0x6042FD7C
0x6015CD38
0x60178804
0x60425070
0x605210A8
0x605FDAF4
0x605FD568
0x60670B3C
0x605FD568
0x606E96DC
0x605FD568
GraphIt
TTY Background
Per-Second Jobs
GraphIt
TTY Background
Per-Second Jobs
SMT input
FBM Timer
Compute load avgs
ARP Input
DHCPD Database
DHCPD Database
IP Cache Ager
DHCPD Database
SSS Test Client
DHCPD Database
Field
Description
CPU utilization
for five seconds
CPU utilization for the last 5 seconds. The second number indicates the percent of
CPU time spent at the interrupt level.
one minute
five minutes
PID
Process ID.
FR-624
78-11740-02
Table 91
Note
Field
Description
Ty
PC
Runtime (ms)
Invoked
uSecs
Stacks
TTY
Process
5Sec
1Min
5Min
Because the network server has a 4-millisecond clock resolution, run times are considered reliable only
after a large number of invocations or a reasonable, measured run time.
For a list of process descriptions, see http://www.cisco.com/warp/public/63/showproc_cpu.html .
Related Commands
Command
Description
FR-625
Syntax Description
history
sorted
Command Modes
Privileged EXEC
Command History
Release
Modification
12.0
12.2(2)T
12.3(8)T
Usage Guidelines
When you use the optional history keyword, output shows (in ASCII graphical form) the total CPU
usage on the device over a period of time. Time periods are one minute, one hour, and 72 hours, displayed
in increments of one second, one minute, and one hour, respectively. Maximum usage is measured and
recorded every second; average usage is calculated on periods of more than one second.
Consistently high CPU utilization over an extended period of time indicates a problem and using the
show processes cpu command is useful for troubleshooting. Also, you can use the output of this
command in the Cisco Output Interpreter tool to display potential issues and fixes. Output Interpreter is
available to registered users of Cisco.com who are logged in and have Java Script enabled.
For a list of system processes, go to http://www.cisco.com/warp/public/63/showproc_cpu.html.
Examples
The following is sample output from the show processes cpu command without keywords:
Router# show processes cpu
CPU utilization for five seconds: 5%/2%; one minute: 3%; five minutes: 2%
PID Runtime (ms)
Invoked
uSecs
5Sec 1Min 5Min TTY Process
1
1736
58
29931
0%
0%
0% 0
Check heaps
2
68
585
116 1.00% 1.00%
0% 0
IP Input
3
0
744
0
0%
0%
0% 0
TCP Timer
4
0
2
0
0%
0%
0% 0
TCP Protocols
5
0
1
0
0%
0%
0% 0
BOOTP Server
6
16
130
123
0%
0%
0% 0
ARP Input
7
0
1
0
0%
0%
0% 0
Probe Input
8
0
7
0
0%
0%
0% 0
MOP Protocols
9
0
2
0
0%
0%
0% 0
Timers
10
692
64
10812
0%
0%
0% 0
Net Background
11
0
5
0
0%
0%
0% 0
Logger
12
0
38
0
0%
0%
0% 0
BGP Open
FR-626
78-11740-02
13
14
15
16
17
18
19
0
540
0
5100
88
152
224
1
3466
1
1367
4232
14650
99
0
155
0
3730
20
10
2262
0%
0%
0%
0%
0%
0%
0%
0%
0%
0%
0%
0%
0.20% 1.00%
0%
0%
0%
0%
0%
0% 1.00%
0
0
0
0
0
0
0
Net Input
TTY Background
BGP I/O
IGRP Router
BGP Router
BGP Scanner
Exec
The following is sample output of the one-hour portion of the output. The Y-axis of the graph is the CPU
utilization. The X-axis of the graph is the increment within the time period displayed in the graph. This
example shows the individual minutes during the previous hour. The most recent measurement is on the
left of the X-axis.
router# show processes cpu history
!--- One minute output omitted
6665776865756676676666667667677676766666766767767666566667
6378016198993513709771991443732358689932740858269643922613
100
90
80
* *
* *
* * * *
70 * * ***** * ** ***** *** **** ****** * *******
* *
60 #***##*##*#***#####*#*###*****#*###*#*#*##*#*##*#*##*****#
50 ##########################################################
40 ##########################################################
30 ##########################################################
20 ##########################################################
10 ##########################################################
0....5....1....1....2....2....3....3....4....4....5....5....
0
5
0
5
0
5
0
5
0
5
CPU% per minute (last 60 minutes)
* = maximum CPU% # = average CPU%
!--- 72-hour output omitted
The top two rows, read vertically, display the highest percentage of CPU utilization recorded during the
time increment. In this example, the CPU utilization for the last minute recorded is 66 percent. The
device may have reached 66 percent only once during that minute, or it may have reached 66 percent
multiple times. The device records only the peak reached during the time increment and the average over
the course of that increment.
The following is sample output from the show processes cpu command that shows an ARP probe
process:
Router# show processes cpu | include ARP
17
36
40
80
114
38140
0
0
0
0
389690
1
1
1
1
97
0
0
0
0
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0.00%
0
0
0
0
0
ARP Input
IP ARP Probe
ATM ARP INPUT
RARP Input
FR ARP
FR-627
Table 92
Note
Related Commands
Field
Description
CPU utilization
for five seconds
CPU utilization for the last 5 seconds and the percent of CPU time spent at the
interrupt level.
one minute
CPU utilization for the last minute and the percent of CPU time spent at the
interrupt level.
five minutes
CPU utilization for the last 5 minutes and the percent of CPU time spent at the
interrupt level.
PID
Process ID.
Runtime (ms)
Invoked
uSecs
5Sec
1Min
5Min
TTY
Process
Because platforms have a 4- to 8-millisecond clock resolution, run times are considered reliable only
after several invocations or a reasonable, measured run time.
Command
Description
FR-628
78-11740-02
Syntax Description
pid
(Optional) Process ID number of a specific process. This keyword shows detail for
only the specified process.
sorted
Command Modes
Privileged EXEC
Command History
Release
Modification
10.0
Examples
The following is sample output from the show processes memory command:
Router# show processes memory
Total: 5611448, Used: 2307548, Free: 3303900
PID TTY Allocated
Freed
Holding
Getbufs
0
0
199592
1236
1907220
0
0
0
400
76928
400
0
0
0
5431176
3340052
140760
349780
1
0
256
256
1724
0
2
0
264
0
5032
0
3
0
0
0
2724
0
4
0
97932
0
2852
32760
5
0
256
256
2724
0
6
0
92
0
2816
0
7
0
0
0
2724
0
8
0
0
0
2724
0
9
0
0
0
2724
0
10
0
892
476
3256
0
11
0
92
0
2816
0
12
0
216
0
2940
0
13
0
0
0
2724
0
14
0
15659136
15658584
3276
0
.
.
.
77
0
116
0
2844
0
2307224 Total
Retbufs
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Process
*Init*
*Sched*
*Dead*
Load Meter
Exec
Check heaps
Pool Manager
Timers
CXBus hot stall
IPC Zone Manager
IPC Realm Manager
IPC Seat Manager
ARP Input
SERIAL A'detect
Microcode Loader
RFSS watchdog
Env Mon
0 IPX-EIGRP Hello
FR-629
Table 93
Field
Description
Total:
Used:
Free:
PID
Process ID.
TTY
Allocated
Freed
Bytes of memory freed by the process, regardless of who originally allocated it.
Holding
Getbufs
Retbufs
Process
Process name.
*Init*
System initialization.
*Sched*
The scheduler.
*Dead*
Total
The following is sample output from the show process memory command when a PID is specified:
Router# show process memory 1
Proc Memory Summary for pid = 1
Holding = 6844
pc = 0x6049B900, size = 000006044, count = 0001
pc = 0x60480650, size = 000000612, count = 0001
pc = 0x6048254C, size = 000000188, count = 0001
Router#
Related Commands
Command
Description
show memory
show processes
FR-630
78-11740-02
show protocols
To display the configured protocols, use the show protocols EXEC command.
This command shows the global and interface-specific status of any configured Level 3 protocol; for
example, IP, DECnet, IPX, AppleTalk, and so on.
show protocols
Syntax Description
Command Modes
EXEC
Command History
Release
Modification
10.0
Examples
For more information on the parameters or protocols shown in this sample output, see the Cisco IOS
Network Protocols Configuration Guide, Part 1, Network Protocols Configuration Guide, Part 2, and
Network Protocols Configuration Guide, Part 3.
FR-631
show slot
To display information about the PCMCIA flash memory cards file system, use the show slot command
in user EXEC or privileged EXEC mode.
show slot [all | chips | filesys]
Syntax Description
all
(Optional) Displays all possible flash system information for all PCMCIA
flash cards in the system.
chips
filesys
Command Modes
User EXEC
Privileged EXEC
Command History
Release
Modification
12.0
Usage Guidelines
Note
Use the show slot command to display details about the files in a particular linear PCMCIA flash
memory card of less than 20 MB and some 32 MB linear PCMCIA cards.
Use the show disk command for ATA PCMCIA cards. Other forms of this commands are show disk0:
and show disk1:.
For more information regarding file systems and flash cards, access the PCMCIA Filesystem
Compatibility Matrix and Filesystem Information document at the following URL:
http://www.cisco.com/en/US/partner/products/hw/routers/ps341/products_tech_note09186a00800a751
5.shtml
To see which flash cards are used in your router, use the show version command and look at the bottom
portion of the output.
The following display indicates an ATA PCMCIA flash disk.
Router# show version
.
.
.
46976K bytes of ATA PCMCIA card at slot 0 (Sector size 512 bytes).
The following display indicates a linear PCMCIA flash card with 20480K bytes of flash memory in card
at slot 1 with a sector size of 128K.
Router# show version
.
.
.
20480K bytes of Flash PCMCIA card at slot 1 (Sector size 128K).
FR-632
78-11740-02
Note
Examples
In some cases the show slot command will not display the file systems, use show slot0: or show slot1:.
The following example displays information about slot 0. The output is self-explanatory.
Router# show slot
PCMCIA Slot0 flash directory:
File Length
Name/status
1
11081464 c3660-bin-mz.123-9.3.PI5b
[11081528 bytes used, 9627844 available, 20709372 total]
20480K bytes of processor board PCMCIA Slot0 flash (Read/Write)
The following example shows all possible flash system information for all PCMCIA flash cards in the
system.
Router# show slot all
Partition
Size
Used
1
20223K 10821K
Free
9402K
Bank-Size
4096K
State
Read/Write
Copy Mode
Direct
Bank
1
1
2
2
3
3
4
4
5
5
Code
89A0
89A0
89A0
89A0
89A0
89A0
89A0
89A0
89A0
89A0
Size
2048KB
2048KB
2048KB
2048KB
2048KB
2048KB
2048KB
2048KB
2048KB
2048KB
Name
INTEL
INTEL
INTEL
INTEL
INTEL
INTEL
INTEL
INTEL
INTEL
INTEL
28F016SA
28F016SA
28F016SA
28F016SA
28F016SA
28F016SA
28F016SA
28F016SA
28F016SA
28F016SA
Bank
1
1
2
2
3
3
4
4
5
5
Code
89A0
89A0
89A0
89A0
89A0
89A0
89A0
89A0
89A0
89A0
Size
2048KB
2048KB
2048KB
2048KB
2048KB
2048KB
2048KB
2048KB
2048KB
2048KB
Name
INTEL
INTEL
INTEL
INTEL
INTEL
INTEL
INTEL
INTEL
INTEL
INTEL
28F016SA
28F016SA
28F016SA
28F016SA
28F016SA
28F016SA
28F016SA
28F016SA
28F016SA
28F016SA
FR-633
Related Commands
Command
Description
dir slot0:
dir slot1:
show slot0:
Displays information about the PCMCIA flash memory cards file system
located in slot 0.
show slot1:
Displays information about the PCMCIA flash memory cards file system
located in slot 1.
FR-634
78-11740-02
show slot0:
To display information about the PCMCIA flash memory cards file system located in slot 0, use the
show slot0: command in user EXEC or privileged EXEC mode.
show slot0: [all | chips | filesys]
Syntax Description
all
(Optional) Displays all possible flash system information for all PCMCIA
flash cards in the system.
chips
filesys
Command Modes
User EXEC
Privileged EXEC
Command History
Release
Modification
12.0
Usage Guidelines
Note
Use the show slot0: command to display details about the files in a particular linear PCMCIA flash
memory card of less than 20 MB and some 32 MB linear PCMCIA cards.
Use the show disk command for ATA PCMCIA cards. Other forms of this commands are show disk0:
and show disk1:.
For more information regarding file systems and flash cards, access the PCMCIA Filesystem
Compatibility Matrix and Filesystem Information document at the following URL:
http://www.cisco.com/en/US/partner/products/hw/routers/ps341/products_tech_note09186a00800a751
5.shtml
To see which flash cards are used in your router, use the show version command and look at the bottom
portion of the output.
The following display indicates an ATA PCMCIA flash disk.
Router# show version
.
.
.
46976K bytes of ATA PCMCIA card at slot 0 (Sector size 512 bytes).
The following display indicates a linear PCMCIA flash card with 20480K bytes of flash memory in card
at slot 1 with a sector size of 128K.
Router# show version
.
.
.
20480K bytes of Flash PCMCIA card at slot 1 (Sector size 128K).
FR-635
Examples
The following example displays information about slot 0. The output is self-explanatory.
Router# show slot0:
PCMCIA Slot0 flash directory:
File Length
Name/status
1
11081464 c3660-bin-mz.123-9.3.PI5b
[11081528 bytes used, 9627844 available, 20709372 total]
20480K bytes of processor board PCMCIA Slot0 flash (Read/Write)
Router# show slot0: all
Partition
Size
Used
1
20223K 10821K
Free
9402K
Bank-Size
4096K
State
Read/Write
Copy Mode
Direct
Bank
1
1
2
2
3
3
4
4
5
5
Code
89A0
89A0
89A0
89A0
89A0
89A0
89A0
89A0
89A0
89A0
Size
2048KB
2048KB
2048KB
2048KB
2048KB
2048KB
2048KB
2048KB
2048KB
2048KB
Name
INTEL
INTEL
INTEL
INTEL
INTEL
INTEL
INTEL
INTEL
INTEL
INTEL
28F016SA
28F016SA
28F016SA
28F016SA
28F016SA
28F016SA
28F016SA
28F016SA
28F016SA
28F016SA
Related Commands
Bank
1
1
2
2
3
3
4
4
5
5
Code
89A0
89A0
89A0
89A0
89A0
89A0
89A0
89A0
89A0
89A0
Size
2048KB
2048KB
2048KB
2048KB
2048KB
2048KB
2048KB
2048KB
2048KB
2048KB
Name
INTEL
INTEL
INTEL
INTEL
INTEL
INTEL
INTEL
INTEL
INTEL
INTEL
28F016SA
28F016SA
28F016SA
28F016SA
28F016SA
28F016SA
28F016SA
28F016SA
28F016SA
28F016SA
Command
Description
dir slot0:
dir slot1:
show slot1:
Displays information about the PCMCIA flash memory cards file system
located in slot 1.
show slot
FR-636
78-11740-02
show slot1:
To display information about the PCMCIA flash memory cards file system located in slot 1, use the
show slot1: command in user EXEC or privileged EXEC mode.
show slot1: [all | chips | filesys]
Syntax Description
all
(Optional) Shows all possible flash system information for all PCMCIA
flash cards in the system.
chips
filesys
Command Modes
User EXEC
Privileged EXEC
Command History
Release
Modification
12.0
Usage Guidelines
Note
Use the show slot1: command to display details about the files in a particular linear PCMCIA flash
memory card of less than 20 MB and some 32 MB linear PCMCIA cards located in slot 1.
Use the show disk command for ATA PCMCIA cards. Other forms of this commands are show disk0:
and show disk1:.
For more information regarding file systems and flash cards, access the PCMCIA Filesystem
Compatibility Matrix and Filesystem Information document at the following URL:
http://www.cisco.com/en/US/partner/products/hw/routers/ps341/products_tech_note09186a00800a751
5.shtml
To see which flash cards are used in your router, use the show version command and look at the bottom
portion of the output.
The following display indicates an ATA PCMCIA flash disk.
Router# show version
.
.
.
46976K bytes of ATA PCMCIA card at slot 0 (Sector size 512 bytes).
The following display indicates a linear PCMCIA flash card with 20480K bytes of flash memory in card
at slot 1 with a sector size of 128K.
Router# show version
.
.
.
20480K bytes of Flash PCMCIA card at slot 1 (Sector size 128K).
FR-637
Examples
The following example displays information about slot 0 using the slot0: command form. The output
is self-explanatory.
Router# show slot1:
PCMCIA Slot1 flash directory:
File Length
Name/status
1
10907068 c3660-bin-mz.123-7.9.PI4
[10907132 bytes used, 5739008 available, 16646140 total]
16384K bytes of processor board PCMCIA Slot1 flash (Read/Write)
Router# show slot1: all
Partition
Size
Used
1
20223K 10821K
Free
9402K
Bank-Size
4096K
State
Read/Write
Copy Mode
Direct
Bank
1
1
2
2
3
3
4
4
5
5
Code
89A0
89A0
89A0
89A0
89A0
89A0
89A0
89A0
89A0
89A0
Size
2048KB
2048KB
2048KB
2048KB
2048KB
2048KB
2048KB
2048KB
2048KB
2048KB
Name
INTEL
INTEL
INTEL
INTEL
INTEL
INTEL
INTEL
INTEL
INTEL
INTEL
28F016SA
28F016SA
28F016SA
28F016SA
28F016SA
28F016SA
28F016SA
28F016SA
28F016SA
28F016SA
Bank
1
1
2
2
3
3
4
4
5
5
Code
89A0
89A0
89A0
89A0
89A0
89A0
89A0
89A0
89A0
89A0
Size
2048KB
2048KB
2048KB
2048KB
2048KB
2048KB
2048KB
2048KB
2048KB
2048KB
Name
INTEL
INTEL
INTEL
INTEL
INTEL
INTEL
INTEL
INTEL
INTEL
INTEL
28F016SA
28F016SA
28F016SA
28F016SA
28F016SA
28F016SA
28F016SA
28F016SA
28F016SA
28F016SA
FR-638
78-11740-02
Related Commands
Command
Description
dir slot0:
dir slot1:
show slot0:
Displays information about the PCMCIA flash memory cards file system
located in slot 0.
show slot
FR-639
show stacks
To monitor the stack usage of processes and interrupt routines, use the show stacks EXEC command.
show stacks
Syntax Description
Command Modes
EXEC
Command History
Release
Modification
10.0
Usage Guidelines
Examples
The display from this command includes the reason for the last system reboot. If the system was reloaded
because of a system failure, a saved system stack trace is displayed. This information is of use only to
your technical support representative in analyzing crashes in the field. It is included here in case you
need to read the displayed statistics to an engineer over the phone.
The following is sample output from the show stacks command following a system failure:
Router# show stacks
Minimum process stacks:
Free/Size Name
652/1000 Router Init
726/1000 Init
744/1000 BGP Open
686/1200 Virtual Exec
Interrupt level stacks:
Level
Called Free/Size Name
1
0 1000/1000 env-flash
3
738 900/1000 Multiport Communications Interfaces
5
178 970/1000 Console UART
System was restarted by bus error at PC 0xAD1F4, address 0xD0D0D1A
GS Software (GS3), Version 9.1(0.16), BETA TEST SOFTWARE
Compiled Tue 11-Aug-92 13:27 by jthomas
Stack trace from system failure:
FP: 0x29C158, RA: 0xACFD4
FP: 0x29C184, RA: 0xAD20C
FP: 0x29C1B0, RA: 0xACFD4
FP: 0x29C1DC, RA: 0xAD304
FP: 0x29C1F8, RA: 0xAF774
FP: 0x29C214, RA: 0xAF83E
FP: 0x29C228, RA: 0x3E0CA
FP: 0x29C244, RA: 0x3BD3C
FR-640
78-11740-02
Related Commands
Command
Description
show processes
FR-641
show subsys
To display the subsystem information, use the show subsys privileged EXEC command.
show subsys [class class | name name]
Syntax Description
class class
name name
Command Modes
Privileged EXEC
Command History
Release
Modification
11.1
Usage Guidelines
Use the show subsys command to confirm that all required features are in the running image.
Examples
In the following example, partial sample output is shown from the show subsys command:
Router# show subsys
static_map
arp
ether
compress
alignment
monvar
slot
oir
atm
ip_addrpool_sys
chat
dialer
flash_services
ip_localpool_sys
nvram_common
ASP
sonict
oc3suni
oc12suni
ds3suni
.
.
.
Class
Kernel
Kernel
Kernel
Kernel
Kernel
Kernel
Kernel
Kernel
Kernel
Library
Library
Library
Library
Library
Driver
Driver
Driver
Driver
Driver
Driver
Version
1.000.001
1.000.001
1.000.001
1.000.001
1.000.002
1.000.001
1.000.001
1.000.001
1.000.001
1.000.001
1.000.001
1.000.001
1.000.001
1.000.001
1.000.001
1.000.001
1.000.001
1.000.001
1.000.001
1.000.001
FR-642
78-11740-02
Field
Description
static_map
Class
Version
FR-643
show tcp
To display the status of TCP connections, use the show tcp EXEC command.
show tcp [line-number]
Syntax Description
line-number
Command Modes
EXEC
CommandHistory
Release
Modification
10.0
Examples
(Optional) Absolute line number of the line for which you want to
display Telnet connection status.
snduna:
67317228
rcvnxt: 1064897597
sndnxt:
rcvwnd:
SendWnd
0
0
0
KeepAlive
0
0
0
67317228
2144
sndwnd:
delrcvwnd:
GiveUp
0
0
0
PmtuAger
0
0
0
4096
0
SRTT: 317 ms, RTTO: 900 ms, RTV: 133 ms, KRTT: 0 ms
minRTT: 4 ms, maxRTT: 300 ms, ACK hold: 300 ms
Flags: higher precedence, idle user, retransmission timeout
Datagrams (max data segment is 536 bytes):
Rcvd: 41 (out of order: 0), with data: 34, total data bytes: 1596
Sent: 57 (retransmit: 1), with data: 35, total data bytes: 55
Table 95 describes the first five lines of output shown in the display.
Table 95
Field
Description
tty0
connection 1
FR-644
78-11740-02
Table 95
Field
Description
to host xxx
Name of the remote host to which the connection has been made.
Number of bytes that the lower-level TCP processes have read, but
the higher-level TCP processes have not yet processed.
Local host:
Local port:
Foreign host:
IP address of the remote host to which the TCP connection has been
made.
Foreign port:
FR-645
Table 95
Field
Description
input:
saved:
The following line of output shows the current time according to the system clock of the local host:
Event Timers (current time is 67341276):
The time shown is the number of milliseconds since the system started.
The following lines of output display the number of times that various local TCP timeout values were
reached during this connection. In this example, the local host re-sent data 30 times because it received
no response from the remote host, and it sent an acknowledgment many more times because there was
no data on which to piggyback.
Timer:
Starts:
Wakeups:
Next:
Retrans
30
1
0
TimeWait
0
0
0
AckHold
32
14
0
SendWnd
0
0
0
KeepAlive
0
0
0
GiveUp
0
0
0
PmtuAger
0
0
0
Field
Description
Timer:
Starts:
The number of times the timer has been started during this connection.
Wakeups:
Number of keepalives sent without receiving any response. (This field is reset to
zero when a response is received.)
Next:
The system clock setting that will trigger the next time this timer will go off.
Retrans
The Retransmission timer is used to time TCP packets that have not been
acknowledged and are waiting for retransmission.
TimeWait
The TimeWait timer is used to ensure that the remote system receives a request to
disconnect a session.
AckHold
SendWnd
The Send Window is used to ensure that there is no closed window due to a lost
TCP acknowledgment.
KeepAlive
The KeepAlive timer is used to control the transmission of test messages to the
remote TCP to ensure that the link has not been broken without the local TCPs
knowledge.
FR-646
78-11740-02
Table 96
Field
Description
GiveUp
The GiveUp timer determines the amount of time a local host will wait for an
acknowledgement (or other appropriate reply) of a transmitted message after the
the maximum number of retransmissions has been reached. If the timer expires,
the local host gives up retransmission attempts and declares the connection dead.
PmtuAger
The PMTU age timer is a time interval for how often TCP reestimates the path
MTU with a larger maximum segment size (MSS). When the age timer is used,
TCP path MTU becomes a dynamic process. If the MSS is smaller than what the
peer connection can manage, a larger MSS is tried every time the age timer
expires. The discovery process stops when the send MSS is as large as the peer
negotiated or the timer has been manually disabled by setting it to infinite.
The following lines of output display the sequence numbers that TCP uses to ensure sequenced, reliable
transport of data. The local host and remote host each use these sequence numbers for flow control and
to acknowledge receipt of datagrams. Table 97 describes the significant fields shown in the display.
iss:
67317172
irs: 1064896000
Table 97
snduna:
67317228
rcvnxt: 1064897597
sndnxt:
rcvwnd:
67317228
2144
sndwnd:
delrcvwnd:
4096
0
Field
Description
iss:
snduna:
Last send sequence number that the local host sent but has not received an
acknowledgment for.
sndnxt:
sndwnd:
irs:
rcvnxt:
Last receive sequence number that the local host has acknowledged.
rcvwnd:
delrcvwnd:
Delayed receive windowdata the local host has read from the connection,
but has not yet subtracted from the receive window the host has advertised
to the remote host. The value in this field gradually increases until it is
larger than a full-sized packet, at which point it is applied to the rcvwnd
field.
The following lines of output display values that the local host uses to keep track of transmission times
so that TCP can adjust to the network it is using.
Table 98 describes the significant fields shown in the display.
SRTT: 317 ms, RTTO: 900 ms, RTV: 133 ms, KRTT: 0 ms
minRTT: 4 ms, maxRTT: 300 ms, ACK hold: 300 ms
Flags: higher precedence, idle user, retransmission timeout
FR-647
Table 98
Field
Description
SRTT:
RTTO:
Round-trip timeout.
RTV:
KRTT:
New round-trip timeout (using the Karn algorithm). This field separately tracks the
round-trip time of packets that have been re-sent.
minRTT:
maxRTT:
ACK hold:
Time the local host will delay an acknowledgment in order to piggyback data on it.
Flags:
For more information on these fields, refer to Round Trip Time Estimation, P. Karn & C. Partridge, ACM
SIGCOMM-87, August 1987.
Table 99 describes the significant fields shown in the display.
Datagrams (max data segment is 536 bytes):
Rcvd: 41 (out of order: 0), with data: 34, total data bytes: 1596
Sent: 57 (retransmit: 1), with data: 35, total data bytes: 55
Table 99
Related Commands
Field
Description
Rcvd:
Number of datagrams the local host has received during this connection
(and the number of these datagrams that were out of order).
with data:
Sent:
Number of datagrams the local host sent during this connection (and the
number of these datagrams that needed to be re-sent).
with data:
Command
Description
FR-648
78-11740-02
Syntax Description
all
Command Modes
EXEC
Command History
Release
Modification
11.2
Examples
(Optional) Displays status for all endpoints. Without this keyword, endpoints
in the LISTEN state are not shown.
The following is sample output from the show tcp brief command while a user has connected into the
system via Telnet:
Router> show tcp brief
TCB
609789AC
Local Address
Router.cisco.com.23
Foreign Address
cider.cisco.com.3733
(state)
ESTAB
Related Commands
Field
Description
TCB
Local Address
Foreign Address
The foreign IP address and port (at the opposite end of the connection).
(state)
The state of the connection. States are described in the syntax description of the
show tcp command.
Command
Description
show tcp
FR-649
Syntax Description
motherboard
slot slot-number
Command Modes
EXEC
Command History
Release
Modification
11.2
Usage Guidelines
The show tdm connections command shows the connection memory for all TDM bus connections in the
access server if you do not limit the display to the motherboard or a slot.
Examples
In the following example, source stream 3 (ST3) channel 2 switched out of stream 6 (ST6) channel 2 is
shown:
AS5200# show tdm connections motherboard
MT8980 motherboard unit 0, Control Register = 0x1F, ODE Register = 0x06
Connection Memory for ST6:
Ch0: 0x62, Ch1: 0x00, Ch2: 0x00, Ch3: 0x00
Ch4: 0x00, Ch5: 0x00, Ch6: 0x00, Ch7: 0x00
Ch8: 0x00, Ch9: 0x00, Ch10: 0x00, Ch11: 0x00
Ch12: 0x00, Ch13: 0x00, Ch14: 0x00, Ch15: 0x00
Ch16: 0x00, Ch17: 0x00, Ch18: 0x00, Ch19: 0x00
Ch20: 0x00, Ch21: 0x00, Ch22: 0x00, Ch23: 0x00
Ch24: 0x00, Ch25: 0x00, Ch26: 0x00, Ch27: 0x00
Ch28: 0x00, Ch29: 0x00, Ch30: 0x00, Ch31: 0x00
To interpret the hexadecimal number 0x62 into meaningful information, you must translate it into binary
code. These two hexadecimal numbers represent a connection from any stream and a channel on any
stream. The number 6 translates into the binary code 0110, which represents the third-source stream. The
number 2 translates into the binary code 0010, which represents the second-source channel.
Stream 6 (ST6) channel 0 is the destination for ST3 channel 2 in this example.
Related Commands
Command
Description
show tcp
FR-650
78-11740-02
Syntax Description
motherboard
slot slot-number
Command Modes
EXEC
Command History
Release
Modification
11.2
Usage Guidelines
The data memory for all TDM bus connections in the access server is displayed if you do not specify a
motherboard or slot.
Examples
In the following example, a snapshot of TDM memory is shown where the normal ISDN idle pattern
(0x7E) is present on all channels of the TDM device resident on the motherboard:
AS5200# show tdm data motherboard
MT8980 motherboard unit
Data Memory for ST0:
Ch0: 0x7E, Ch1: 0x7E,
Ch4: 0x7E, Ch5: 0x7E,
Ch8: 0x7E, Ch9: 0x7E,
Ch12: 0x7E, Ch13: 0x7E,
Ch16: 0x7E, Ch17: 0x7E,
Ch20: 0x7E, Ch21: 0x7E,
Ch24: 0x7E, Ch25: 0x7E,
Ch28: 0x7E, Ch29: 0x7E,
Data Memory for ST1:
Ch0: 0x7E, Ch1: 0x7E,
Ch4: 0x7E, Ch5: 0x7E,
Ch8: 0x7E, Ch9: 0x7E,
Ch12: 0x7E, Ch13: 0x7E,
Ch16: 0x7E, Ch17: 0x7E,
Ch20: 0x7E, Ch21: 0x7E,
Ch24: 0x7E, Ch25: 0x7E,
Ch28: 0x7E, Ch29: 0x7E,
Related Commands
Command
0x7E,
0x7E,
0x7E,
0x7E,
0x7E,
0x7E,
0x7E,
0x7E,
Ch3:
Ch7:
Ch11:
Ch15:
Ch19:
Ch23:
Ch27:
Ch31:
0x7E
0x7E
0x7E
0x7E
0x7E
0x7E
0x7E
0x7E
Ch2:
Ch6:
Ch10:
Ch14:
Ch18:
Ch22:
Ch26:
Ch30:
0x7E,
0x7E,
0x7E,
0x7E,
0x7E,
0x7E,
0x7E,
0x7E,
Ch3:
Ch7:
Ch11:
Ch15:
Ch19:
Ch23:
Ch27:
Ch31:
0x7E
0x7E
0x7E
0x7E
0x7E
0x7E
0x7E
0x7E
Description
show tdm connections Displays data about the TDM bus connection memory in a Cisco AS5200
access server.
FR-651
show tech-support
To display general information about the router when reporting a problem, use the show tech-support
privileged EXEC command.
show tech-support [page] [password] [cef | ipmulticast | isis | mpls | ospf [process-ID | detail] |
rsvp]
Syntax Description
page
password
cef
ipc
ipmulticast
isis
mpls
ospf [ process-ID |
detail]
rsvp
Defaults
Command Modes
Privileged EXEC
Command History
Release
Modification
11.2
11.3(7), 11.2(16)
The output for this command was expanded to show additional information
for boot, bootflash, context, and traffic for all enabled protocols.
(CSCdj06229)
FR-652
78-11740-02
Usage Guidelines
Release
Modification
11.3(7)T
12.0
cef
ipmulticast
isis
mpls
ospf
The show tech-support command is useful for collecting a large amount of information about your
routing device for troubleshooting purposes. The output of this command can be provided to technical
support representatives when reporting a problem.
The show tech-support command displays the output of a number of show commands at once. The
output from this command will vary depending on your platform and configuration. For example, Access
Servers will display voice-related show output. Additionally, the show protocol traffic commands will
be displayed for only the protocols enabled on your device. The output of the show tech-support
command can include the output of the following commands:
show bootflash
show bootvar
show buffers
show cef
show context
show controllers
show interfaces
show ip cef
show ip interface
show ip traffic
show isis
show mpls
show running-config
show stacks
FR-653
show version
dir nvram:
Use of the optional cef, ipmulticast, ipc, isis, mpls , ospf, or rsvp keywords provides a way to display
a number of show commands specific to a particular protocol or process in addition to the show
commands listed previously.
For example, if your TAC support representative suspects that you may have a problem in your Cisco
Express Forwarding (CEF) configuration, you may be asked to provide the output of the show
tech-support cef command. The show tech-support [page] [password] cef command will display the
output from the following commands in addition to the output for the standard show tech-support
command:
Examples
For a sample display of the output from the show tech-support command, refer to the documentation
for the show commands listed in the Usage Guidelines section.
Related Commands
Command
Description
Displays information about the number and type of Apollo Domain packets
transmitted and received by the Cisco IOS software.
show appletalk traffic Displays statistics about AppleTalk traffic, including MacIP traffic.
show bootflash
show bootvar
Displays the contents of the BOOT environment variable, the name of the
configuration file pointed to by the CONFIG_FILE environment variable,
the contents of the BOOTLDR environment variable, and the configuration
register setting.
show buffers
FR-654
78-11740-02
Command
Description
show context
show controllers
show controllers
tech-support
show interfaces
show ip traffic
Displays information about the number and type of IPX packets transmitted
and received.
show processes
memory
show running-config
show stacks
show version
Displays the configuration of the system hardware, the software version, the
names and sources of configuration files, and the boot images.
Displays information about the number and type of XNS packets transmitted
and received by the Cisco IOS software.
FR-655
test flash
To test Flash memory on MCI and envm Flash EPROM interfaces, use the test flash EXEC command.
test flash
Syntax Description
Command Modes
EXEC
Command History
Release
Modification
10.0
Examples
Related Commands
Command
Description
test interfaces
test memory
FR-656
78-11740-02
test interfaces
To test the system interfaces on the modular router, use the test interfaces EXEC command.
test interfaces
Syntax Description
Command Modes
EXEC
Command History
Release
Modification
10.0
Usage Guidelines
The test interfaces EXEC command is intended for the factory checkout of network interfaces. It is not
intended for diagnosing problems with an operational router. The test interfaces output does not report
correct results if the router is attached to a live network. For each network interface that has an IP
address that can be tested in loopback (MCI and ciscoBus Ethernet and all serial interfaces), the test
interfaces command sends a series of ICMP echoes. Error counters are examined to determine the
operational status of the interface.
Examples
Related Commands
Command
Description
test flash
test memory
FR-657
test memory
To perform a test of Multibus memory (including nonvolatile memory) on the modular router, use the
test memory EXEC command. The memory test overwrites memory.
test memory
Syntax Description
Command Modes
EXEC
Command History
Release
Modification
10.0
Usage Guidelines
Examples
The memory test overwrites memory. If you use the test memory command, you will need to rewrite
nonvolatile memory. For example, if you test Multibus memory, which is the memory used by the CSC-R
4-Mbps Token Ring interfaces, you will need to reload the system before the network interfaces will
operate properly. The test memory command is intended primarily for use by Cisco personnel.
Related Commands
Command
Description
test flash
test interfaces
FR-658
78-11740-02
trace (privileged)
To discover the routes that packets will actually take when traveling to their destination, use the trace
privileged EXEC command.
trace [protocol] [destination]
Syntax Description
protocol
(Optional) Protocols that can be used are appletalk, clns, ip and vines.
destination
(Optional) Destination address or host name on the command line. The default
parameters for the appropriate protocol are assumed and the tracing action
begins.
Defaults
The protocol argument is based on the Cisco IOS software examination of the format of the destination
argument. For example, if the software finds a destination argument in IP format, the protocol value
defaults to ip.
Command Modes
Privileged EXEC
Command History
Release
Modification
10.0
Usage Guidelines
The trace command works by taking advantage of the error messages generated by routers when a
datagram exceeds its time-to-live (TTL) value.
The trace command starts by sending probe datagrams with a TTL value of one. This causes the first
router to discard the probe datagram and send back an error message. The trace command sends several
probes at each TTL level and displays the round-trip time for each.
The trace command sends out one probe at a time. Each outgoing packet may result in one or two error
messages. A time exceeded error message indicates that an intermediate router has seen and discarded
the probe. A destination unreachable error message indicates that the destination node has received
the probe and discarded it because it could not deliver the packet. If the timer goes off before a response
comes in, the trace command prints an asterisk (*).
The trace command terminates when the destination responds, when the maximum TTL is exceeded, or
when the user interrupts the trace with the escape sequence. By default, to invoke the escape sequence,
type Ctrl-^ X by simultaneously pressing and releasing the Ctrl, Shift, and 6 keys, and then pressing
the X key.
To use nondefault parameters and invoke an extended trace test, enter the command without a
destination argument. You will be stepped through a dialog to select the desired parameters.
Common Trace Problems
Due to bugs in the IP implementation of various hosts and routers, the IP trace command may behave
in unexpected ways.
FR-659
Not all destinations will respond correctly to a probe message by sending back an ICMP port
unreachable message. A long sequence of TTL levels with only asterisks, terminating only when the
maximum TTL has been reached, may indicate this problem.
There is a known problem with the way some hosts handle an ICMP TTL exceeded message. Some
hosts generate an ICMP message but they reuse the TTL of the incoming packet. Because this is zero,
the ICMP packets do not make it back. When you trace the path to such a host, you may see a set of TTL
values with asterisks (*). Eventually the TTL gets high enough that the ICMP message can get back. For
example, if the host is six hops away, the trace command will time out on responses 6 through 11.
Trace IP Routes
The following display shows sample IP trace output when a destination host name has been specified:
Router# trace ABA.NYC.mil
Type escape sequence to abort.
Tracing the route to ABA.NYC.mil (26.0.0.73)
1 DEBRIS.CISCO.COM (192.180.1.6) 1000 msec 8 msec 4 msec
2 BARRNET-GW.CISCO.COM (192.180.16.2) 8 msec 8 msec 8 msec
3 EXTERNAL-A-GATEWAY.STANFORD.EDU (192.42.110.225) 8 msec 4 msec 4 msec
4 BB2.SU.BARRNET.NET (192.200.254.6) 8 msec 8 msec 8 msec
5 SU.ARC.BARRNET.NET (192.200.3.8) 12 msec 12 msec 8 msec
6 MOFFETT-FLD-MB.in.MIL (192.52.195.1) 216 msec 120 msec 132 msec
7 ABA.NYC.mil (26.0.0.73) 412 msec 628 msec 664 msec
Field
Description
Indicates the sequence number of the router in the path to the host.
DEBRIS.CISCO.COM
192.180.1.6
Round-trip time for each of the three probes that are sent.
The following display shows a sample trace session involving the extended dialog of the trace
command:
Router# trace
Protocol [ip]:
Target IP address: mit.edu
Source address:
Numeric display [n]:
Timeout in seconds [3]:
Probe count [3]:
Minimum Time to Live [1]:
Maximum Time to Live [30]:
Port Number [33434]:
Loose, Strict, Record, Timestamp, Verbose[none]:
Type escape sequence to abort.
Tracing the route to MIT.EDU (18.72.2.1)
1 ICM-DC-2-V1.ICP.NET (192.108.209.17) 72 msec 72 msec 88 msec
2 ICM-FIX-E-H0-T3.ICP.NET (192.157.65.122) 80 msec 128 msec 80 msec
3 192.203.229.246 540 msec 88 msec 84 msec
4 T3-2.WASHINGTON-DC-CNSS58.T3.ANS.NET (140.222.58.3) 84 msec 116 msec 88 msec
FR-660
78-11740-02
5
6
7
8
9
10
11
12
Table 102 describes the fields that are unique to the extended trace sequence, as shown in the display.
Table 102
Field
Description
Target IP address
Source address
Numeric display
Timeout in seconds
Probe count
The number of probes to be sent at each TTL level. The default count
is 3.
The TTL value for the first probes. The default is 1, but it can be set to
a higher value to suppress the display of known hops.
Maximum Time to Live [30] The largest TTL value that can be used. The default is 30. The trace
command terminates when the destination is reached or when this
value is reached.
Port Number
The destination port used by the User Datagram Protocol (UDP) probe
messages. The default is 33434.
Loose
Allows you to specify a list of nodes that must be traversed when going
to the destination.
Strict
Allows you to specify a list of nodes that must be the only nodes
traversed when going to the destination.
Record
Timestamp
Allows you to specify the number of time stamps to leave room for.
Verbose
Table 103describes the characters that can appear in trace command output.
FR-661
Table 103
Related Commands
Char
Description
nn msec
For each node, the round-trip time (in milliseconds) for the specified number of
probes.
Host unreachable.
Network unreachable.
Protocol unreachable.
Source quench.
Port unreachable.
Command
Description
trace (user)
Discovers the CLNS routes that packets will actually take when traveling to
their destination.
FR-662
78-11740-02
trace (user)
To discover the IP routes that packets will actually take when traveling to their destination, use the trace
EXEC command.
trace [protocol] [destination]
Syntax Description
protocol
(Optional) Protocols that can be used are appletalk, clns, ip and vines.
destination
(Optional) Destination address or host name on the command line. The default
parameters for the appropriate protocol are assumed and the tracing action
begins.
Defaults
The protocol argument is based on the Cisco IOS software examination of the format of the destination
argument. For example, if the software finds a destination argument in IP format, the protocol defaults
to ip.
Command Modes
EXEC
Command History
Release
Modification
10.0
Usage Guidelines
The trace command works by taking advantage of the error messages generated by routers when a
datagram exceeds its time-to-live (TTL) value.
The trace command starts by sending probe datagrams with a TTL value of one. This causes the first
router to discard the probe datagram and send back a system message. The trace command sends several
probes at each TTL level and displays the round-trip time for each.
The trace command sends out one probe at a time. Each outgoing packet may result in one or two system
messages. A time exceeded system message indicates that an intermediate router has seen and
discarded the probe. A destination unreachable system message indicates that the destination node has
received the probe and discarded it because it could not deliver the packet. If the timer goes off before a
response comes in, trace prints an asterisk (*).
The trace command terminates when the destination responds, when the maximum TTL is exceeded, or
when the user interrupts the trace with the escape sequence. By default, to invoke the escape sequence,
type Ctrl-^ X by simultaneously pressing and releasing the Ctrl, Shift, and 6 keys, and then pressing
the X key.
Common Trace Problems
Due to bugs in the IP implementation of various hosts and routers, the IP trace command may behave
in unexpected ways.
Not all destinations will respond correctly to a probe message by sending back an ICMP port
unreachable message. A long sequence of TTL levels with only asterisks, terminating only when the
maximum TTL has been reached, may indicate this problem.
FR-663
There is a known problem with the way some hosts handle an ICMP TTL exceeded message. Some
hosts generate an ICMP message but they reuse the TTL of the incoming packet. Since this is zero, the
ICMP packets do not make it back. When you trace the path to such a host, you may see a set of TTL
values with asterisks (*). Eventually the TTL gets high enough that the ICMP message can get back.
For example, if the host is six hops away, trace will time out on responses 6 through 11.
Trace IP Routes
The following display shows sample IP trace output when a destination host name has been specified:
Router# trace ip ABA.NYC.mil
Type escape sequence to abort.
Tracing the route to ABA.NYC.mil (26.0.0.73)
1 DEBRIS.CISCO.COM (192.180.1.6) 1000 msec 8 msec 4 msec
2 BARRNET-GW.CISCO.COM (192.180.16.2) 8 msec 8 msec 8 msec
3 EXTERNAL-A-GATEWAY.STANFORD.EDU (192.42.110.225) 8 msec 4 msec 4 msec
4 BB2.SU.BARRNET.NET (192.200.254.6) 8 msec 8 msec 8 msec
5 SU.ARC.BARRNET.NET (192.200.3.8) 12 msec 12 msec 8 msec
6 MOFFETT-FLD-MB.in.MIL (192.52.195.1) 216 msec 120 msec 132 msec
7 ABA.NYC.mil (26.0.0.73) 412 msec 628 msec 664 msec
Field
Description
Indicates the sequence number of the router in the path to the host.
DEBRIS.CISCO.COM
192.180.1.61
Round-trip time for each of the three probes that are sent.
Table 105 describes the characters that can appear in trace output.
Table 105
Char
Description
nn msec
For each node, the round-trip time (in milliseconds) for the specified number of
probes.
Host unreachable.
Network unreachable.
Protocol unreachable.
Source quench.
Port unreachable.
FR-664
78-11740-02
Related Commands
Command
Description
trace (privileged)
Probes the routes that packets follow when traveling to their destination from
the router.
FR-665
FR-666
78-11740-02
SNMP Commands
This chapter describes Cisco IOS Release 12.2 commands used to configure Simple Network
Management Protocol (SNMP) on your routers for the purposes of network monitoring and management.
For SNMP configuration tasks and examples, refer to the Configuring SNMP Support chapter in the
Release 12.2 Cisco IOS Configuration Fundamentals Configuration Guide.
FR-667
SNMP Commands
no snmp-server
no snmp-server
To disable Simple Network Management Protocol (SNMP) agent operation, use the no snmp-server
global configuration command.
no snmp-server
Syntax Description
Defaults
None
Command Modes
Global configuration
Command History
Release
Modification
10.0
Usage Guidelines
This command disables all running versions of SNMP (SNMPv1, SNMPv2C, and SNMPv3) on the
device.
Examples
FR-668
78-11740-02
SNMP Commands
show management event
Syntax Description
Defaults
Command Modes
Privileged EXEC
Command History
Release
Modification
12.1(3)T
Usage Guidelines
The Event MIB allows you to configure your own traps, informs, or set operations through the use of an
external network management application. The show management event command is used to display
the values for the Events configured on your system. There are no Cisco IOS CLI commands for
configuring Event MIB values. For information on Event MIB functionality, see RFC 2981, available at
http://www.ietf.org.
Examples
The following example shows sample output of the show management event command:
Router# show management event
Mgmt Triggers:
(1): Owner: aseem
(1): 01, Comment: TestEvent, Sample: Abs, Freq: 120
Test: Existence Threshold Boolean
ObjectOwner: aseem, Object: sethi
OID: ifEntry.10.3, Enabled 1, Row Status 1
Existence Entry: , Absent, Changed
StartUp: Present, Absent
ObjOwn: , Obj: , EveOwn: aseem, Eve: 09
Boolean Entry:
Value: 10, Cmp: 1, Start: 1
ObjOwn: , Obj: , EveOwn: aseem, Eve: 09
Threshold Entry:
Rising: 50000, Falling: 20000
ObjOwn: ase, Obj: 01 RisEveOwn: ase, RisEve: 09 , FallEveOwn: ase, FallEve: 09
Delta Value Table:
(0): Thresh: Rising, Exis: 1, Read: 0, OID: ifEntry.10.3 , val: 69356097
Mgmt Events:
FR-669
SNMP Commands
show management event
Related Commands
Command
Description
debug management event Allows real-time monitoring of Event MIB activities for the purposes of
debugging.
FR-670
78-11740-02
SNMP Commands
show snmp
show snmp
To check the status of Simple Network Management Protocol (SNMP) communications, use the
show snmp EXEC command.
show snmp
Syntax Description
Command Modes
EXEC
Command History
Release
Modification
10.0
Usage Guidelines
Examples
This command provides counter information for SNMP operations. It also displays the chassis ID string
defined with the snmp-server chassis-id global configuration command.
FR-671
SNMP Commands
show snmp
0 Drops
SNMP Manager-role input packets
0 Inform response PDUs
2 Trap PDUs
7 Response PDUs
1 Responses with errors
SNMP informs: enabled
Informs in flight 0/25 (current/max)
Logging to 171.69.217.141.162
4 sent, 0 in-flight, 1 retries, 0 failed, 0 dropped
Logging to 171.69.58.33.162
0 sent, 0 in-flight, 0 retries, 0 failed, 0 dropped
Field
Description
Chassis
Chassis ID string.
Encoding errors
Number of requested
variables
Get-request PDUs
Get-next PDUs
Set-request PDUs
Number of SNMP requests that specified a MIB object that does not
exist.
General errors
Number of SNMP set requests that failed due to some other error. (It
was not a noSuchName error, badValue error, or any of the other
specific errors.)
Response PDUs
Trap PDUs
SNMP logging
sent
FR-672
78-11740-02
SNMP Commands
show snmp
Table 106
Field
dropped
Number of traps dropped. Traps are dropped when the trap queue for
a destination exceeds the maximum length of the queue, as set by the
snmp-server queue-length global configuration command.
Information related to packets sent by the router as an SNMP
manager.
Get-request PDUs
Get-next PDUs
Get-bulk PDUs
Set-request PDUs
Inform-request PDUs
Timeouts
Drops
Trap PDUs
Response PDUs
SNMP informs
Related Commands
Description
Informs in flight
Logging to
sent
in-flight
retries
failed
dropped
Command
Description
snmp-server chassis-id
snmp-server manager
snmp-server manager session-timeout Sets the amount of time before a nonactive session is
destroyed.
snmp-server queue-length
FR-673
SNMP Commands
show snmp engineID
Syntax Description
Command Modes
EXEC
Command History
Release
Modification
12.0(3)T
Usage Guidelines
An SNMP engine is a copy of SNMP that can reside on a local or remote device.
Examples
Related Commands
Field
Definition
Remote Engine ID
IP-addr
Port
Command
Description
snmp-server engineID
Configures a name for either the local or remote SNMP engine on the
router.
FR-674
78-11740-02
SNMP Commands
show snmp group
Syntax Description
Command Modes
EXEC
Command History
Release
Modification
12.0(3)T
Examples
The following example specifies the group name as public, the security model as v1, the read view name
as v1default, the notify view name as *tv.FFFFFFFF, and the storage type as volatile:
router# show snmp group
groupname: public
security model:v1
readview:v1default
writeview: no writeview specified
notifyview: *tv.FFFFFFFF
storage-type: volatile
Related Commands
Field
Definition
groupname
security model
The security model used by the group, either v1, v2c, or v3.
readview
writeview
notifyview
storage-type
Command
Description
snmp-server group
Configures a new SNMP group or a table that maps SNMP users to SNMP
views.
FR-675
SNMP Commands
show snmp pending
Syntax Description
Command Modes
EXEC
Command History
Release
Modification
11.3 T
Usage Guidelines
After the SNMP manager sends a request, the request is pending until the manager receives a response
or the request timeout expires.
Examples
The following is sample output from the show snmp pending command:
Router# show snmp pending
req
req
req
req
id:
id:
id:
id:
47,
49,
51,
53,
dest:
dest:
dest:
dest:
171.69.58.33.161,
171.69.58.33.161,
171.69.58.33.161,
171.69.58.33.161,
V2C
V2C
V2C
V2C
community:
community:
community:
community:
public,
public,
public,
public,
Expires
Expires
Expires
Expires
in
in
in
in
5
6
6
8
secs
secs
secs
secs
Related Commands
Field
Description
req id
dest
V2C community
Expires in
Command
Description
show snmp
snmp-server manager
snmp-server manager
session-timeout
FR-676
78-11740-02
SNMP Commands
show snmp sessions
Syntax Description
brief
Command Modes
EXEC
Command History
Release
Modification
11.3 T
Usage Guidelines
Sessions are created when the SNMP manager in the router sends SNMP requests, such as inform
requests, to a host or receives SNMP notifications from a host. One session is created for each
destination host. If there is no further communication between the router and host within the session
timeout period, the corresponding session will be deleted.
Examples
The following is sample output from the show snmp sessions command:
Router# show snmp sessions
Destination: 171.69.58.33.162, V2C community: public
Round-trip-times: 0/0/0 (min/max/last)
packets output
0 Gets, 0 GetNexts, 0 GetBulks, 0 Sets, 4 Informs
0 Timeouts, 0 Drops
packets input
0 Traps, 0 Informs, 0 Responses (0 errors)
Destination: 171.69.217.141.162, V2C community: public, Expires in 575 secs
Round-trip-times: 1/1/1 (min/max/last)
packets output
0 Gets, 0 GetNexts, 0 GetBulks, 0 Sets, 4 Informs
0 Timeouts, 0 Drops
packets input
0 Traps, 0 Informs, 4 Responses (0 errors)
The following is sample output from the show snmp sessions brief command:
Router# show snmp sessions brief
Destination: 171.69.58.33.161, V2C community: public, Expires in 55 secs
FR-677
SNMP Commands
show snmp sessions
Table 110
Field
Description
Destination
V2C community
Expires in
Round-trip-times
packets output
Gets
GetNexts
GetBulks
Sets
Informs
Timeouts
Drops
packets input
Related Commands
Traps
Informs
Responses
errors
Command
Description
show snmp
snmp-server manager
snmp-server manager
session-timeout
FR-678
78-11740-02
SNMP Commands
show snmp user
Syntax Description
Command Modes
EXEC
Command History
Release
Modification
12.0(3)T
Usage Guidelines
An SNMP user is a remote user for which an SNMP management operation is performed. For example,
inform operations can be sent to a user on a remote SNMP engine. The user is designated using the
snmp-server user command.
Examples
The following example specifies the username as authuser, the engine ID string as
00000009020000000C025808, and the storage-type as nonvolatile:
router# show snmp user
User name: authuser
Engine ID: 00000009020000000C025808
storage-type: nonvolatile
Related Commands
Field
Definition
User name
Engine ID
storage-type
Command
Description
snmp-server user
FR-679
SNMP Commands
snmp-server access-policy
snmp-server access-policy
This command is no longer valid. The functionality provided by this command has been removed from
the Cisco IOS software.
FR-680
78-11740-02
SNMP Commands
snmp-server chassis-id
snmp-server chassis-id
To provide a message line identifying the Simple Network Management Protocol (SNMP) server serial
number, use the snmp-server chassis-id global configuration command. To restore the default value, if
any, use the no form of this command.
snmp-server chassis-id text
no snmp-server chassis-id
Syntax Description
text
Defaults
On hardware platforms where the serial number can be machine read, the default is the serial number.
For example, a Cisco 7000 router has a default chassis-id value of its serial number.
Command Modes
Global configuration
Command History
Release
Modification
10.0
Usage Guidelines
The Cisco MIB provides a chassis MIB variable that enables the SNMP manager to gather data on system
card descriptions, chassis type, chassis hardware version, chassis ID string, software version of ROM
monitor, software version of system image in ROM, bytes of processor RAM installed, bytes of NVRAM
installed, bytes of NVRAM in use, current configuration register setting, and the value of the
configuration register at the next reload. The following installed card information is provided: type of
card, serial number, hardware version, software version, and chassis slot number.
The chassis ID message can be seen with the show snmp command.
Examples
Related Commands
Command
Description
show snmp
FR-681
SNMP Commands
snmp-server community
snmp-server community
To set up the community access string to permit access to the Simple Network Management Protocol
(SNMP), use the snmp-server community global configuration command. To remove the specified
community string, use the no form of this command.
snmp-server community string [view view-name] [ro | rw] [number]
no snmp-server community string
Syntax Description
Defaults
string
Community string that acts like a password and permits access to the SNMP
protocol.
view view-name
(Optional) Name of a previously defined view. The view defines the objects
available to the community.
ro
rw
number
(Optional) Integer from 1 to 99 that specifies an access list of IP addresses that are
allowed to use the community string to gain access to the SNMP agent.
Note
If the snmp-server community command is not used during the SNMP configuration session, it will
automatically be added to the configuration after the snmp host command is used. In this case, the
default password (string) for the snmp-server community will be taken from the snmp host
command.
Command Modes
Global configuration
Command History
Release
Modification
10.0
Usage Guidelines
The no snmp-server command disables all versions of SNMP (SNMPv1, SNMPv2C, SNMPv3).
The first snmp-server command that you enter enables all versions of SNMP.
Examples
The following example assigns the string comaccess to SNMP allowing read-only access and specifies
that IP access list 4 can use the community string:
Router(config)# snmp-server community comaccess ro 4
FR-682
78-11740-02
SNMP Commands
snmp-server community
The following example assigns the string mgr to SNMP allowing read-write access to the objects in the
restricted view:
Router(config)# snmp-server community mgr view restricted rw
Related Commands
Command
Description
access-list
Configures the access list mechanism for filtering frames by protocol type or
vendor code.
snmp-server view
FR-683
SNMP Commands
snmp-server contact
snmp-server contact
To set the system contact (sysContact) string, use the snmp-server contact global configuration
command. To remove the system contact information, use the no form of this command.
snmp-server contact text
no snmp-server contact
Syntax Description
text
Defaults
Command Modes
Global configuration
Command History
Release
Modification
10.0
Examples
Related Commands
Command
Description
snmp-server location
FR-684
78-11740-02
SNMP Commands
snmp-server context
snmp-server context
This command is no longer valid. The functionality provided by this command has been removed from
the Cisco IOS software.
FR-685
SNMP Commands
snmp-server enable informs
FR-686
78-11740-02
SNMP Commands
snmp-server enable traps
Syntax Description
notification-type
(5) ciscoDlswTrapCircuitUp
(6) ciscoDlswTrapCircuitDown
tconnEnables DLSw peer transport connection traps:
(1) ciscoDlswTrapTConnPartnerReject
(2) ciscoDlswTrapTConnProtViolation
(3) ciscoDlswTrapTConnUp
(4) ciscoDlswTrapTConnDown
FR-687
SNMP Commands
snmp-server enable traps
Defaults
This command is disabled by default. Most notification types are disabled. However, some notification
types cannot be controlled with this command.
If you enter this command with no notification-type keywords, the default is to enable all notification
types controlled by this command.
Command Modes
Global configuration
Command History
Release
Modification
10.3
This command was introduced with the frame-relay, isdn, and envmon trap
types.
12.0(2)T
12.0(3)T
Usage Guidelines
For additional notification types, see the Related Commands table for this command.
SNMP notifications can be sent as traps or inform requests. This command enables both traps and inform
requests for the specified notification types. To specify whether the notifications should be sent as traps
or informs, use the snmp-server host [traps | informs] command.
If you do not enter an snmp-server enable traps command, no notifications controlled by this command
are sent. In order to configure the router to send these SNMP notifications, you must enter at least one
snmp-server enable traps command. If you enter the command with no keywords, all notification types
are enabled. If you enter the command with a keyword, only the notification type related to that keyword
is enabled. In order to enable multiple types of notifications, you must issue a separate
snmp-server enable traps command for each notification type and notification option.
The snmp-server enable traps command is used in conjunction with the snmp-server host command.
Use the snmp-server host command to specify which host or hosts receive SNMP notifications. In order
to send notifications, you must configure at least one snmp-server host command.
FR-688
78-11740-02
SNMP Commands
snmp-server enable traps
Examples
The following example enables the router to send all traps to the host specified by the name
myhost.cisco.com, using the community string defined as public:
Router(config)# snmp-server enable traps
Router(config)# snmp-server host myhost.cisco.com public
The following example enables the router to send Frame Relay and environmental monitor traps to the
host myhost.cisco.com using the community string public:
Router(config)# snmp-server enable traps frame-relay
Router(config)# snmp-server enable traps envmon temperature
Router(config)# snmp-server host myhost.cisco.com public
The following example will not send traps to any host. The BGP traps are enabled for all hosts, but the
only traps enabled to be sent to a host are ISDN traps (which are not enabled in this example).
Router(config)# snmp-server enable traps bgp
Router(config)# snmp-server host bob public isdn
The following example enables the router to send all inform requests to the host at the address
myhost.cisco.com, using the community string defined as public:
Router(config)# snmp-server enable traps
Router(config)# snmp-server host myhost.cisco.com informs version 2c public
The following example sends HSRP MIB traps to the host myhost.cisco.com using the community string
public.
Router(config)# snmp-server enable traps hsrp
Router(config)# snmp-server host myhost.cisco.com traps version 2c public hsrp
Related Commands
Command
Description
snmp-server enable traps atm pvc Controls (enables or disables) ATM PVC SNMP notifications.
snmp-server enable traps bgp
snmp-server enable traps envmon Controls (enables or disables) environmental monitor SNMP
notifications.
snmp-server enable traps
frame-relay
snmp-server enable traps repeater Controls (enables or disables) RFC 1516 Hub notifications.
snmp-server host
snmp-server informs
FR-689
SNMP Commands
snmp-server enable traps
Command
Description
snmp-server trap-source
FR-690
78-11740-02
SNMP Commands
snmp-server enable traps aaa_server
Syntax Description
Defaults
Command Modes
Global configuration
Command History
Release
Modification
12.1(3)T
This command was introduced for the Cisco AS5300 and Cisco AS5800.
Usage Guidelines
SNMP notifications can be sent as traps or inform requests. This command enables both traps and inform
requests.
This command controls (enables or disables) AAA Server state change (casServerStateChange)
notifications. ServerStateChange notifications, when enabled, will be sent when the server moves from
an up to dead state or when a server moves from a dead to up state.
The Cisco AAA Server State is defined by the casState object in the Cisco AAA Server MIB. The
possible values are as follows:
A server is marked "dead" if it does not respond after maximum retransmissions. A server is marked "up"
again either after a waiting period or if some response is received from it. The initial value of casState
is "up(1)" at system startup. This will only transition to "dead(2)" if an attempt to communicate fails.
For a complete description of this notification and additional MIB functions, see the
CISCO-AAA-SERVER-MIB.my file, available on Cisco.com at http://www.cisco.com/public/mibs/v2/.
The snmp-server enable traps aaa_sever command is used in conjunction with the snmp-server host
command. Use the snmp-server host command to specify which host or hosts receive SNMP
notifications. To send SNMP notifications, you must configure at least one snmp-server host command.
Examples
The following example enables the router to send AAA Server up/down informs to the host at the address
myhost.cisco.com using the community string defined as public:
FR-691
SNMP Commands
snmp-server enable traps aaa_server
Related Commands
Command
Description
show caller
snmp-server host
snmp-server trap-source
FR-692
78-11740-02
SNMP Commands
snmp-server enable traps atm pvc
Syntax Description
interval seconds
fail-interval seconds
Defaults
(Optional) Minimum period for storing the failed time stamp, in the range
from 0 to 3600.
Command Modes
Global configuration
Command History
Release
Modification
12.0(1)T
This command was introduced for those platforms that support ATM PVC
Management.
Usage Guidelines
SNMP notifications can be sent as traps or inform requests. This command enables both traps and inform
requests for the specified notification types. ATM notifications are defined in the
CISCO-IETF-ATM2-PVCTRAP-MIB.my file, available from the Cisco FTP site at
ftp://www.cisco.com/public/mibs/v2/.
ATM PVC failure notification are sent when a PVC on an ATM interface fails or leaves the UP
operational state. Only one trap is generated per hardware interface, within the specified interval defined
by the interval keyword (stored as the atmIntfPvcNotificationInterval in the MIB). If other PVCs on the
same interface go DOWN during this interval, traps are generated and held until the fail-interval has
elapsed. Once the interval has elapsed, the traps are sent if the PVCs are still DOWN.
No notifications are generated when a PVC returns to the UP state after having been in the DOWN state.
If you need to detect the recovery of PVCs, you must use the SNMP management application to regularly
poll your router.
The snmp-server enable traps atm pvc command is used in conjunction with the snmp-server host
command. Use the snmp-server host command to specify which host or hosts receive SNMP
notifications. In order to send notifications, you must configure at least one snmp-server host command.
FR-693
SNMP Commands
snmp-server enable traps atm pvc
Examples
The following example shows the enabling of ATM PVC traps on a router, so that if PVC 0/1 goes down,
host 172.16.61.90 will receive the notifications:
!For ATM PVC Trap Support to work on your router, you must first have SNMP support and
!an IP routing protocol configured on your router:
Router(config)# snmp-server community public ro
Router(config)# snmp-server host 172.16.61.90 public
Router(config)# ip routing
Router(config)# router igrp 109
Router(config-router)# network 172.16.0.0
!
!Enable ATM PVC Trap Support and OAM management:
Router(config)# snmp-server enable traps atm pvc interval 40 fail-interval 10
Router(config)# interface atm 1/0.1
Router(config-if)# pvc 0/1
Router(config-if-atm-vc)# oam-pvc manage
Related Commands
Command
Description
snmp-server enable traps Enables all available SNMP notifications on your system.
snmp-server host
snmp-server trap-source
FR-694
78-11740-02
SNMP Commands
snmp-server enable traps bgp
Syntax Description
Defaults
Command Modes
Global configuration
Command History
Release
Modification
12.1(3)T
This command was introduced for the Cisco AS5300 and Cisco AS5800.
Usage Guidelines
SNMP notifications can be sent as traps or inform requests. This command enables both traps and inform
requests.
This command controls (enables or disables) Border Gateway Protocol server state change notifications,
as defined in the BGP4-MIB (enterprise 1.3.6.1.2.1.15.7). The notifications types are:
(1) bgpEstablished
(2) bgpBackwardTransition.
The BGP notifications are defined in the BGP-4 MIB as follows:
bgpTraps
bgpEstablished NOTIFICATION-TYPE
OBJECTS { bgpPeerLastError,
bgpPeerState
}
STATUS current
DESCRIPTION
"The BGP Established event is generated when
the BGP FSM enters the ESTABLISHED state."
::= { bgpTraps 1 }
bgpBackwardTransition NOTIFICATION-TYPE
OBJECTS { bgpPeerLastError,
bgpPeerState
}
STATUS current
DESCRIPTION
"The BGPBackwardTransition Event is generated
when the BGP FSM moves from a higher numbered
state to a lower numbered state."
::= { bgpTraps 2 }
FR-695
SNMP Commands
snmp-server enable traps bgp
For a complete description of these notifications and additional MIB functions, see the BGP4-MIB.my
file, available through the Cisco FTP site at ftp://www.cisco.com/public/mibs/v2/.
Note
You may notice incorrect BGP trap OID output when using the SNMP version 1 BGP4-MIB that is
available for download at ftp://ftp.cisco.com/pub/mibs/v1/BGP4-MIB-V1SMI.my. When a router
sends out BGP traps (notifications) about state changes on an SNMP version 1 monitored BGP peer,
the enterprise OID is incorrectly displayed as .1.3.6.1.2.1.15 (bgp) instead of .1.3.6.1.2.1.15.7
(bgpTraps). The problem is not due to any error with Cisco IOS software. This problem occurs
because the BGP4-MIB does not follow RFC 1908 rules regarding version 1 and version 2 trap
compliance. This MIB is controlled by IANA under the guidance of the IETF, and work is currently
in progress by the IETF to replace this MIB with a new version that represents the current state of
the BGP protocol. In the meantime, we recommend that you use the SNMP version 2 BGP4-MIB or
the CISCO-BGP4-MIB to avoid an incorrect trap OID.
The snmp-server enable traps bgp command is used in conjunction with the snmp-server host
command. Use the snmp-server host command to specify which host or hosts receive SNMP
notifications. To send SNMP notifications, you must configure at least one snmp-server host command.
Examples
The following example enables the router to send BGP state change informs to the host at the address
myhost.cisco.com using the community string defined as public:
Router(config)# snmp-server enable traps bgp
Router(config)# snmp-server host myhost.cisco.com informs version 2c public
Related Commands
Command
Description
snmp-server host
snmp-server trap-source
FR-696
78-11740-02
SNMP Commands
snmp-server enable traps calltracker
Syntax Description
Defaults
Command Modes
Global configuration
Command History
Release
Modification
12.1(3)T
This command was introduced for the Cisco AS5300 and Cisco AS580
access servers.
Usage Guidelines
SNMP notifications can be sent as traps or inform requests. This command enables both traps and inform
requests.
This command controls (enables or disables) Call Tracker CallSetup and CallTerminate notifications.
CallSetup notifications are generated at the start of each call, when an entry is created in the active table
(cctActiveTable), and CallTerminate notifications are generated at the end of each call, when an entry is
created in the history table (cctHistoryTable).
For a complete description of these notifications and additional MIB functions, refer to the
CISCO-CALL-TRACKER-MIB.my file, available on Cisco.com at
http://www.cisco.com/public/mibs/v2/.
The snmp-server enable traps calltracker command is used in conjunction with the snmp-server host
global configuration command. Use the snmp-server host command to specify which host or hosts
receive SNMP notifications. To send SNMP notifications, you must configure at least one snmp-server
host command.
Examples
The following example enables the router to send call-start and call-stop informs to the host at the
address myhost.cisco.com using the community string defined as public:
Router(config)# snmp-server enable traps calltracker
Router(config)# snmp-server host myhost.cisco.com informs version 2c public calltracker
FR-697
SNMP Commands
snmp-server enable traps calltracker
Related Commands
Command
Description
calltracker call-record
calltracker enable
Displays all of the information stored within the Call Tracker Active
or History Database for the latest call assigned to specified modem.
snmp-server host
snmp-server trap-source
FR-698
78-11740-02
SNMP Commands
snmp-server enable traps envmon
Syntax Description
shutdown
voltage
temperature
fan
supply
Defaults
Command Modes
Global configuration
Command History
Release
Modification
10.3
11.3(6)AA
Support for this command was introduced for the Cisco AS5300 access
server.
FR-699
SNMP Commands
snmp-server enable traps envmon
Usage Guidelines
SNMP notifications can be sent as traps or inform requests. This command enables both traps and inform
requests.
This command controls (enables or disables) Environmental Monitor (EnvMon) status notifications for
supported systems. Cisco enterprise EnvMon notifications are triggered when an environmental
threshold is exceeded. If none of the optional keywords are specified, all available environmental
notifications are enabled.
For a complete description of these notifications and additional MIB functions, see the
CISCO-ENVMON-MIB.my and CISCO-ACCESS-ENVMON-MIB.my files, available on Cisco.com at
http://www.cisco.com/public/mibs/v2/.
Status of the Environmental Monitor can be viewed using the show environment command.
The snmp-server enable traps envmon command is used in conjunction with the snmp-server host
command. Use the snmp-server host command to specify which host or hosts receive SNMP
notifications. To send SNMP notifications, you must configure at least one snmp-server host command.
Examples
The following example enables a Cisco 12000 GSR to send environmental failure informs to the host at
the address myhost.cisco.com using the community string defined as public:
Router(config)# snmp-server enable traps envmon
Router(config)# snmp-server host myhost.cisco.com informs version 2c public envmon
Related Commands
Command
Description
show environment
snmp-server host
snmp-server trap-source
FR-700
78-11740-02
SNMP Commands
snmp-server enable traps frame-relay
Syntax Description
Defaults
Command Modes
Global configuration
Command History
Release
Modification
10.3
Usage Guidelines
SNMP notifications can be sent as traps or inform requests. This command enables both traps and inform
requests.
This command controls (enables or disables) Data Link Connection Identifier (DLCI) Frame Relay
notifications, as defined in the RFC1315-MIB (enterprise 1.3.6.1.2.1.10.32).
The notification type is frDLCIStatusChange (1). This trap indicates that the indicated Virtual Circuit
(VC) has changed state, meaning that the VC has either been created or invalidated, or has toggled
between the active and inactive states.
Note
For large scale configurations (systems containing hundreds of Frame Relay point-to-point
subinterfaces), note that having Frame Relay notifications enabled could potentially have a negative
impact on network performance when there are line status changes.
For a complete description of this notification and additional MIB functions, see the RFC1315-MIB.my
file and the CISCO-FRAME-RELAY-MIB.my file, available in the v1 and v2 directories,
repectively, at the Cisco.com MIB web site at
http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml.
The snmp-server enable traps frame-relay command is used in conjunction with the snmp-server
host command. Use the snmp-server host command to specify which host or hosts receive SNMP
notifications. To send SNMP notifications, you must configure at least one snmp-server host command.
Examples
In the following examplethe router is configured to send Frame Relay DLCI state change informs to the
host at the address myhost.cisco.com using the community string defined as public:
FR-701
SNMP Commands
snmp-server enable traps frame-relay
Related Commands
Command
Description
snmp-server host
snmp-server trap-source
FR-702
78-11740-02
SNMP Commands
snmp-server enable traps isdn
Syntax Description
Defaults
call-information
demandNbrCallInformation (1)
This notification is sent to the manager whenever a successful call clears,
or a failed call attempt is determined to have ultimately failed. In the event
that call retry is active, then this is after all retry attempts have failed.
However, only one such notification is sent in between successful call
attempts; subsequent call attempts do not generate notifications of this
type.
demandNbrCallDetails (2)
This notification is sent to the manager whenever a call connects, or
clears, or a failed call attempt is determined to have ultimately failed. In
the event that call retry is active, then this is after all retry attempts have
failed. However, only one such notification is sent in between successful
call attempts; subsequent call attempts do not generate notifications of this
type.
chan-not-avail
isdnu-interface
layer2
Command Modes
Global configuration
Command History
Release
Modification
10.3
11.3
FR-703
SNMP Commands
snmp-server enable traps isdn
Usage Guidelines
Release
Modification
12.0
12.1(5)T
Support for the isdn chan-not-available option was added for the
Cisco AS5300, Cisco AS5400, and Cisco AS5800 access servers only.
SNMP notifications can be sent as traps or inform requests. This command enables both traps and inform
requests for the specified notification types. ISDN notifications are defined in the
CISCO-ISDN-MIB.my and CISCO-ISDNU-IF-MIB.my files, available on Cisco.com at
http://www.cisco.com/public/mibs/v2/.
Availability of notifications will depend on your platform. To see what notifications are available, use
the snmp-server enable traps isdn ? command.
If you do not enter an snmp-server enable traps isdn command, no notifications controlled by this
command are sent. In order to configure the router to send these SNMP notifications, you must enter at
least one snmp-server enable traps isdn command. If you enter the command with no keywords, all
notification types are enabled. If you enter the command with a keyword, only the notification type
related to that keyword is enabled.
The snmp-server enable traps snmp command is used in conjunction with the snmp-server host
command. Use the snmp-server host command to specify which host or hosts receive SNMP
notifications. To send SNMP notifications, you must configure at least one snmp-server host command.
Examples
The following example shows the checking of what notification types are available on a Cisco AS5300,
and the enabling of channel-not-available and layer2 informs:
NAS(config)#snmp-server enable traps
call-information Enable SNMP isdn
chan-not-avail
Enable SNMP isdn
layer2
Enable SNMP isdn
<cr>
isdn ?
call information traps
channel not avail traps
layer2 transition traps
Related Commands
Command
Description
snmp-server enable traps Enables all available SNMP notifications on your system.
snmp-server host
snmp-server informs
snmp-server trap-source
FR-704
78-11740-02
SNMP Commands
snmp-server enable traps snmp
Syntax Description
Defaults
authentication
linkup
linkdown
coldstart
warmstart
Command Modes
Global configuration
FR-705
SNMP Commands
snmp-server enable traps snmp
Command History
Release
Modification
11.3
12.1(3)T
12.1(5)T
Usage Guidelines
linkup
linkdown
coldstart
SNMP notifications can be sent as traps or inform requests. This command enables both traps and inform
requests for the specified notification types.
If you do not enter an snmp-server enable traps snmp command, no notifications controlled by this
command are sent. In order to configure the router to send these SNMP notifications, you must enter at
least one snmp-server enable traps snmp command. If you enter the command with no keywords, all
notification types are enabled. If you enter the command with a keyword, only the notification type
related to that keyword is enabled.
The snmp-server enable traps snmp command is used in conjunction with the snmp-server host
command. Use the snmp-server host command to specify which host or hosts receive SNMP
notifications. In order to send notifications, you must configure at least one snmp-server host command.
For a host to receive a notification controlled by this command, both the snmp-server enable traps
command and the snmp-server host command for that host must be enabled. If the notification type is
not controlled by this command, just the appropriate snmp-server host command must be enabled.
The snmp-server enable traps snmp [ linkup] [linkdown] form of this command globally enables or
disables SNMP linkUp and linkDown traps. After enabling either of these traps globally, you can disable
these traps on specific interfaces using the no snmp trap link-status command in interface
configuration mode. Note that on the interface level, linkUp and linkDown traps are enabled by default.
This means that you do not have to enable these notifications on a per-interface basis. However, linkUp
and linkDown notifications will not be sent unless you enable them globally using the snmp-server
enable traps snmp command.
Examples
The following example enables the router to send all traps to the host myhost.cisco.com, using the
community string defined as public:
Router(config)# snmp-server enable traps snmp
Router(config)# snmp-server host myhost.cisco.com public snmp
The following example enables the router to send all inform notifications to the host myhost.cisco.com
using the community string defined as public:
Router(config)# snmp-server enable traps snmp
Router(config)# snmp-server host myhost.cisco.com informs version 2c public snmp
The following example shows the enabling all SNMP trap types, then the disabling of only the linkUp
and linkDown traps.
Router> enable
Password:
Router# configure terminal
FR-706
78-11740-02
SNMP Commands
snmp-server enable traps snmp
Related Commands
Command
Description
snmp-server enable traps Enables all available SNMP notifications on your system.
snmp-server host
snmp-server informs
snmp-server trap-source
FR-707
SNMP Commands
snmp-server enable traps repeater
Syntax Description
health
reset
Defaults
rptrFailure(3)repeater-related failure
groupFailure(4)group-related failure
portFailure(5)port-related failure
Command Modes
Global configuration
Command History
Release
Modification
11.1
Usage Guidelines
SNMP notifications can be sent as traps or inform requests. This command enables both traps and inform
requests.
This command controls (enables or disables) Repeater MIB notifications, as defined in RFC 1516. RFC
1516 defines objects for managing IEEE 802.3 10 Mbps baseband repeaters, also known as hubs.
FR-708
78-11740-02
SNMP Commands
snmp-server enable traps repeater
There are two sets of notifications available for this command. The following notification is defined in
the CISCO-REPEATER-MIB (enterprise 1.3.6.1.4.1.9.9.22.3):
1 rptrHealth
2 rptrGroupChange
3 rptrResetEvent
For a complete description of the repeater notifications and additional MIB functions, refer to the
CISCO-REPEATER-MIB.my and CISCO-REPEATER-MIB-V1SMI.my files, available on Cisco.com at
http://www.cisco.com/public/mibs/.
The snmp-server enable traps repeater command is used in conjunction with the snmp-server host
command. Use the snmp-server host command to specify which host or hosts receive SNMP
notifications. To send SNMP notifications, you must configure at least one snmp-server host command.
Examples
The following example enables the router to send repeater inform notifications to the host at the address
myhost.cisco.com using the community string defined as public:
Router(config)# snmp-server enable traps repeater
Router(config)# snmp-server host myhost.cisco.com informs version 2c public
Related Commands
Command
Description
snmp-server host
snmp-server trap-source
FR-709
SNMP Commands
snmp-server enable traps voice poor-qov
Syntax Description
Defaults
Command Modes
Global configuration
Command History
Release
Modification
12.1(3)T
This command was introduced for the Cisco AS5300 and Cisco AS5800.
Usage Guidelines
SNMP notifications can be sent as traps or inform requests. This command enables both traps and inform
requests.
This command controls (enables or disables) poor-quality-of-voice notifications. The
poor-quality-of-voice notification is defined in CISCO-VOICE-DIAL-CONTROL-MIB as follows:
enterprise 1.3.6.1.4.1.9.9.63.2
(1) cvdcPoorQoVNotification
For a complete description of this notification and additional MIB functions, see the
CISCO-VOICE-DIAL-CONTROL-MIB.my file, available on Cisco.com at
http://www.cisco.com/public/mibs/v2/.
The snmp-server enable traps voice poor-qov command is used in conjunction with the
snmp-server host command. Use the snmp-server host command to specify which host or hosts receive
SNMP notifications. To send SNMP notifications, you must configure at least one snmp-server host
command.
Examples
The following example enables the router to poor-quality-of-voice informs to the host at the address
myhost.cisco.com using the community string defined as public:
Router(config)# snmp-server enable traps voice poor-qov
Router(config)# snmp-server host myhost.cisco.com informs version 2c public
FR-710
78-11740-02
SNMP Commands
snmp-server enable traps voice poor-qov
Related Commands
Command
Description
snmp-server host
snmp-server trap-source
FR-711
SNMP Commands
snmp-server engineID
snmp-server engineID
To configure a name for either the local or remote Simple Network Management Protocol (SNMP)
engine on the router, use the snmp-server engineID global configuration command. To remove the
configured engine ID, use the no form of this command.
snmp-server engineID {local engineid-string |
remote ip-address [udp-port port] engineid-string}
no snmp-server engineID
Syntax Description
Defaults
local
Specifies the local copy of SNMP on the router. (You must specify either
local or remote.)
engineid-string
remote
Specifies the remote copy of SNMP on the router. (You must specify either
local or remote.)
ip-address
The IP address of the device that contains the remote copy of SNMP.
udp-port
port
(Optional) The socket number on the remote device that contains the remote
copy of SNMP.
An SNMP engine ID is generated automatically but is not displayed or stored in the running
configuration. You can display the default or configured engine ID by using the show snmp engineID
EXEC command.
The default udp-port for remote engines is 161.
Command Modes
Global configuration
Command History
Release
Modification
12.0(3)T
Usage Guidelines
Note that you need not specify the entire 24-character engine ID if it contains trailing zeros. Specify only
the portion of the Engine ID up until the point where only zeros remain in the value. To configure an
engine ID of 123400000000000000000000, you can specify the value 1234, for example, snmp-server
engineID local 1234.
Changing the value of snmpEngineID has important side-effects. A user's password (entered on the
command line) is converted to an MD5 or SHA security digest. This digest is based on both the password
and the local engine ID. The command line password is then destroyed, as required by
RFC 2274.
Because of this deletion, if the local value of engineID changes, the security digests of SNMPv3 users
will be invalid, and the users will have to be reconfigured.
FR-712
78-11740-02
SNMP Commands
snmp-server engineID
Similar restrictions require the reconfiguration of community strings when the engine ID changes. A
remote engine ID is required when an SNMPv3 inform is configured. The remote engine ID is used to
compute the security digest for authenticating and encrypting packets sent to a user on the remote host.
Please refer to the examples in the Configuring Informs section in the snmp-server host command
reference page.
Related Commands
Command
Description
Displays the identification of the local SNMP engine and all remote engines
that have been configured on the router.
snmp-server host
FR-713
SNMP Commands
snmp-server group
snmp-server group
To configure a new Simple Network Management Protocol (SNMP) group, or a table that maps SNMP
users to SNMP views, use the snmp-server group global configuration command. To remove a specified
SNMP group, use the no form of this command.
snmp-server group groupname {v1 | v2c | v3 {auth | noauth | priv}} [read readview]
[write writeview] [notify notifyview ] [access access-list]
no snmp-server group
Syntax Description
Defaults
groupname
v1
v2c
The second least secure of the possible security models. It allows for the
transmission of informs and counter 64, which allows for integers twice the
width of what is normally allowed.
v3
auth
noauth
priv
read
readview
A string (not to exceed 64 characters) that is the name of the view that
enables you only to view the contents of the agent.
write
writeview
A string (not to exceed 64 characters) that is the name of the view that
enables you to enter data and configure the contents of the agent.
notify
notifyview
A string (not to exceed 64 characters) that is the name of the view that
enables you to specify a notify, inform, or trap.
access
access-list
A string (not to exceed 64 characters) that is the name of the access list.
Default
Definition
readview
FR-714
78-11740-02
SNMP Commands
snmp-server group
Table 112
Default
Definition
writeview
Nothing is defined for the write view (that is, the null OID). You must
configure write access.
notifyview
Nothing is defined for the notify view (that is, the null OID). If a view
is specified, any notifications in that view that are generated will be sent
to all users associated with the group (provided an SNMP server host
configuration exists for the user).
Command Modes
Global configuration
Command History
Release
Modification
11.(3)T
Usage Guidelines
When a community string is configured internally, two groups with the name public are autogenerated,
one for the v1 security model and the other for the v2c security model. Similarly, deleting a community
string will delete a v1 group with the name public and a v2c group with the name public.
Configuring Notify Views
Do not specify a notify view when configuring an SNMP group for the following reasons:
The snmp-server host command autogenerates a notify view for the user, and then adds it to the
group associated with that user.
Modifying the groups notify view will affect all users associated with that group.
If a group has a notify view that is set using SNMP, you may need to change the notify view.
The snmp-server host command may have been configured before the snmp-server group
command. In this case, you must either reconfigure the snmp-server host command, or specify the
appropriate notify view.
Instead of specifying the notify view for a group as part of the snmp-server group command, use the
following commands in global configuration mode:
Step
Command
Purpose
1.
snmp-server user
2.
snmp-server group
3.
snmp-server host
FR-715
SNMP Commands
snmp-server group
No default values exist for authentication or privacy algorithms when you configure the command. Also,
no default passwords exist. The minimum length for a password is one character, although Cisco
recommends using eight characters for security. If you forget a password, you cannot recover it and will
need to reconfigure the user. You can specify either a plain-text password or a localized MD5 digest.
The following example shows how to enter a plain-text password for the string arizona2 for user John in
group Johngroup, type the following command line:
snmp-server user John Johngroup v3 auth md5 arizona2
When you enter a show running-config command, you will not see a line for this user. To see if this user
has been added to the configuration, type the show snmp user command.
If you have the localized MD5 or SHA digest, you can specify that string instead of the plain-text
password. The digest should be formatted as aa:bb:cc:dd where aa, bb, and cc are hex values. Also, the
digest should be exactly 16 octets long.
The following example shows how to specify the command with a digest name of
00:11:22:33:44:55:66:77:88:99:AA:BB:CC:DD:EE:FF:
Router(config)# snmp-server user John Johngroup v3 encrypted auth md5
00:11:22:33:44:55:66:77:88:99:AA:BB:CC:DD:EE:FF
Related Commands
Command
Description
Displays the names of groups on the router and the security model, the status
of the different views, and the storage type of each group.
FR-716
78-11740-02
SNMP Commands
snmp-server host
snmp-server host
To specify the recipient of a Simple Network Management Protocol (SNMP) notification operation, use
the snmp-server host global configuration command. To remove the specified host, use the no form of
this command.
snmp-server host host-addr [traps | informs] [version {1 | 2c | 3 [auth | noauth | priv]}]
community-string [udp-port port] [notification-type]
no snmp-server host host [traps | informs]
Syntax Description
host-addr
traps
informs
version
(Optional) Version of the SNMP used to send the traps. Version 3 is the most
secure model, because it allows packet encryption with the priv keyword. If you
use the version keyword, one of the following must be specified:
2cSNMPv2C.
3SNMPv3. The following three optional keywords can follow the version 3
keyword:
auth (Optional). Enables Message Digest 5 (MD5) and Secure Hash
FR-717
SNMP Commands
snmp-server host
notification-type
Defaults
voiceSends SNMP poor quality of voice traps, when used with the snmp
enable peer-trap poor qov command.
FR-718
78-11740-02
SNMP Commands
snmp-server host
Note
If the community-string is not defined using the snmp-server community command prior to using
this command, the default form of the snmp-server community command will automatically be
inserted into the configuration. The password (community-string) used for this automatic
configuration of the snmp-server community will be the same as specified in the snmp-server host
command. This is the default behavior for Cisco IOS Release 12.0(3) and later.
Command Modes
Global configuration
Command History
Release
Usage Guidelines
Modification
10.0
12.0(3)T
hsrp
12.1(3)T
The calltracker notification-type keyword was added for the Cisco AS5300
and AS5800 platforms.
SNMP notifications can be sent as traps or inform requests. Traps are unreliable because the receiver
does not send acknowledgments when it receives traps. The sender cannot determine if the traps were
received. However, an SNMP entity that receives an inform request acknowledges the message with an
SNMP response PDU. If the sender never receives the response, the inform request can be sent again.
Thus, informs are more likely to reach their intended destination.
However, informs consume more resources in the agent and in the network. Unlike a trap, which is
discarded as soon as it is sent, an inform request must be held in memory until a response is received or
the request times out. Also, traps are sent only once, while an inform may be retried several times. The
retries increase traffic and contribute to a higher overhead on the network.
If you do not enter an snmp-server host command, no notifications are sent. In order to configure the
router to send SNMP notifications, you must enter at least one snmp-server host command. If you enter
the command with no keywords, all trap types are enabled for the host.
In order to enable multiple hosts, you must issue a separate snmp-server host command for each host.
You can specify multiple notification types in the command for each host.
When multiple snmp-server host commands are given for the same host and kind of notification (trap
or inform), each succeeding command overwrites the previous command. Only the last snmp-server
host command will be in effect. For example, if you enter an snmp-server host inform command for a
host and then enter another snmp-server host inform command for the same host, the second command
will replace the first.
The snmp-server host command is used in conjunction with the snmp-server enable command. Use
the snmp-server enable command to specify which SNMP notifications are sent globally. For a host to
receive most notifications, at least one snmp-server enable command and the snmp-server host
command for that host must be enabled.
FR-719
SNMP Commands
snmp-server host
However, some notification types cannot be controlled with the snmp-server enable command. For
example, some notification types are always enabled. Other notification types are enabled by a different
command. For example, the linkUpDown notifications are controlled by the snmp trap link-status
command. These notification types do not require an snmp-server enable command.
A notification-type options availability depends on the router type and Cisco IOS software features
supported on the router. For example, the envmon notification-type is available only if the
environmental monitor is part of the system. To see what notification types are available on your system,
use the command help ? at the end of the snmp-server host command.
Examples
If you want to configure a unique snmp community string for traps, but you want to prevent snmp polling
access with this string, the configuration should include an access-list. In the following example, the
community string is named comaccess and the access list is numbered 10:
Router(config)# snmp-server community comaccess ro 10
Router(config)# snmp-server host 172.20.2.160 comaccess
Router(config)# access-list 10 deny any
The following example sends RFC 1157 SNMP traps to the host specified by the name
myhost.cisco.com. Other traps are enabled, but only SNMP traps are sent because only snmp is specified
in the snmp-server host command. The community string is defined as comaccess.
Router(config)# snmp-server enable traps
Router(config)# snmp-server host myhost.cisco.com comaccess snmp
The following example sends the SNMP and Cisco environmental monitor enterprise-specific traps to
address 172.30.2.160:
Router(config)# snmp-server enable traps snmp
Router(config)# snmp-server enable traps envmon
Router(config)# snmp-server host 172.30.2.160 public snmp envmon
The following example enables the router to send all traps to the host myhost.cisco.com using the
community string public:
Router(config)# snmp-server enable traps
Router(config)# snmp-server host myhost.cisco.com public
The following example will not send traps to any host. The BGP traps are enabled for all hosts, but only
the ISDN traps are enabled to be sent to a host.
Router(config)# snmp-server enable traps bgp
Router(config)# snmp-server host bob public isdn
The following example enables the router to send all inform requests to the host myhost.cisco.com using
the community string public:
Router(config)# snmp-server enable traps
Router(config)# snmp-server host myhost.cisco.com informs version 2c public
The following example sends HSRP MIB informs to the host specified by the name myhost.cisco.com.
The community string is defined as public.
Router(config)# snmp-server enable traps hsrp
Router(config)# snmp-server host myhost.cisco.com informs version 2c public hsrp
FR-720
78-11740-02
SNMP Commands
snmp-server host
Related Commands
Command
Description
snmp-server informs
snmp-server trap-source
snmp-server trap-timeout
FR-721
SNMP Commands
snmp-server informs
snmp-server informs
To specify inform request options, use the snmp-server informs global configuration command. To
return the settings to the defaults, use the no form of this command.
snmp-server informs [retries retries] [timeout seconds] [pending pending]
no snmp-server informs [retries retries] [timeout seconds] [pending pending]
Syntax Description
retries retries
timeout seconds
pending pending
Defaults
Inform requests are resent three times. Informs are resent after 30 seconds if no response is received.
The maximum number of informs waiting for acknowledgments at any one time is 25.
Command Modes
Global configuration
Command History
Release
Modification
11.3 T
Examples
The following example increases the pending queue size if you are seeing a large number of inform
drops:
snmp-server informs pending 50
The following example increases the default timeout if you are sending informs over slow network links.
Because informs will be sitting in the queue for a longer period of time, you may also need to increase
the pending queue size.
snmp-server informs timeout 60 pending 40
The following example decreases the default timeout if you are sending informs over very fast links:
snmp-server informs timeout 5
The following example increases the retry count if you are sending informs over unreliable links.
Because informs will be sitting in the queue for a longer period of time, you may need to increase the
pending queue size.
snmp-server informs retries 10 pending 45
FR-722
78-11740-02
SNMP Commands
snmp-server informs
Related Commands
Command
Description
FR-723
SNMP Commands
snmp-server location
snmp-server location
To set the system location string, use the snmp-server location global configuration command. To
remove the location string, use the no form of this command.
snmp-server location text
no snmp-server location
Syntax Description
text
Defaults
Command Modes
Global configuration
Command History
Release
Modification
10.0
Examples
Related Commands
Command
Description
snmp-server contact
FR-724
78-11740-02
SNMP Commands
snmp-server manager
snmp-server manager
To start the Simple Network Management Protocol (SNMP) manager process, use the snmp-server
manager global configuration command. To stop the SNMP manager process, use the no form of this
command.
snmp-server manager
no snmp-server manager
Syntax Description
Defaults
Disabled
Command Modes
Global configuration
Command History
Release
Modification
11.3 T
Usage Guidelines
The SNMP manager process sends SNMP requests to agents and receives SNMP responses and
notifications from agents. When the SNMP manager process is enabled, the router can query other
SNMP agents and process incoming SNMP traps.
Most network security policies assume that routers will be accepting SNMP requests, sending SNMP
responses, and sending SNMP notifications. With the SNMP manager functionality enabled, the router
may also be sending SNMP requests, receiving SNMP responses, and receiving SNMP notifications. The
security policy implementation may need to be updated prior to enabling this functionality.
SNMP requests are typically sent to UDP port 161. SNMP responses are typically sent from UDP port
161. SNMP notifications are typically sent to UDP port 162.
Examples
Related Commands
Command
Description
show snmp
snmp-server manager
session-timeout
FR-725
SNMP Commands
snmp-server manager session-timeout
Syntax Description
seconds
Defaults
Command Modes
Global configuration
Command History
Release
Modification
11.3 T
Usage Guidelines
Sessions are created when the SNMP manager in the router sends SNMP requests, such as inform
requests, to a host or receives SNMP notifications from a host. One session is created for each
destination host. If there is no further communication between the router and host within the session
timeout period, the session will be deleted.
The router tracks statistics, such as the average round-trip time required to reach the host, for each
session. Using the statistics for a session, the SNMP manager in the router can set reasonable timeout
periods for future requests, such as informs, for that host. If the session is deleted, all statistics are lost.
If another session with the same host is later created, the request timeout value for replies will return to
the default value.
However, sessions consume memory. A reasonable session timeout value should be large enough such
that regularly used sessions are not prematurely deleted, yet small enough such that irregularly used, or
one-shot sessions, are purged expeditiously.
Examples
The following example sets the session timeout to a larger value than the default:
snmp-server manager
snmp-server manager session-timeout 1000
FR-726
78-11740-02
SNMP Commands
snmp-server manager session-timeout
Related Commands
Command
Description
FR-727
SNMP Commands
snmp-server packetsize
snmp-server packetsize
To establish control over the largest Simple Network Management Protocol (SNMP) packet size
permitted when the SNMP server is receiving a request or generating a reply, use the snmp-server
packetsize global configuration command. To restore the default value, use the no form of this
command.
snmp-server packetsize byte-count
no snmp-server packetsize
Syntax Description
byte-count
Defaults
1500 bytes
Command Modes
Global configuration
Command History
Release
Modification
10.0
Examples
Integer byte count from 484 to 8192. The default is 1500 bytes.
The following example establishes a packet filtering of a maximum size of 1024 bytes:
snmp-server packetsize 1024
Related Commands
Command
Description
snmp-server queue-length
FR-728
78-11740-02
SNMP Commands
snmp-server queue-length
snmp-server queue-length
To establish the message queue length for each trap host, use the snmp-server queue-length global
configuration command.
snmp-server queue-length length
Syntax Description
length
Defaults
10 events
Command Modes
Global configuration
Command History
Release
Modification
10.0
Usage Guidelines
Integer that specifies the number of trap events that can be held before the queue
must be emptied.
This command defines the length of the message queue for each trap host. Once a trap message is
successfully transmitted, software will continue to empty the queue, but never faster than at a rate of four
trap messages per second.
During device bootup, there is a possibility that some traps could be dropped because of trap queue
overflow on the device. If you suspect this is occuring, you can increase the size of the trap queue (for
example, to 100) to determine if traps are then able to be sent during bootup.
Examples
Related Commands
Command
Description
snmp-server packetsize
Establishes control over the largest SNMP packet size permitted when
the SNMP server is receiving a request or generating a reply.
FR-729
SNMP Commands
snmp-server system-shutdown
snmp-server system-shutdown
To use the Simple Network Management Protocol (SNMP) message reload feature, the router
configuration must include the snmp-server system-shutdown global configuration command. To
prevent an SNMP system-shutdown request (from an SNMP manager) from resetting the Cisco agent,
use the no form of this command.
snmp-server system-shutdown
no snmp-server system-shutdown
Syntax Description
Defaults
Command Modes
Global configuration
Command History
Release
Modification
10.0
Examples
FR-730
78-11740-02
SNMP Commands
snmp-server tftp-server-list
snmp-server tftp-server-list
To limit the TFTP servers used via Simple Network Management Protocol (SNMP) controlled TFTP
operations (saving and loading configuration files) to the servers specified in an access list, use the
snmp-server tftp-server-list global configuration command. To disable this feature, use the no form of
this command.
snmp-server tftp-server-list number
no snmp-server tftp-server-list
Syntax Description
number
Defaults
Disabled
Command Modes
Global configuration
Command History
Release
Modification
10.2
Examples
The following example limits the TFTP servers that can be used for configuration file copies via SNMP
to the servers in access list 44:
snmp-server tftp-server-list 44
FR-731
SNMP Commands
snmp-server trap-authentication
snmp-server trap-authentication
The snmp-server trap-authentication command has been replaced by the snmp-server enable traps
snmp authentication command. See the description of the snmp-server enable traps snmp command
in this chapter for more information.
FR-732
78-11740-02
SNMP Commands
snmp-server trap link
Syntax Description
ietf
Defaults
Command Modes
Global configuration
Command History
Release
Modification
12.1(2)T
Usage Guidelines
This required keyword indicates to the command parser that you would like
to link functionality of SNMP linkUp/linkDown traps to the Internet
Engineering Task Force (IETF) standard (as opposed to the previous Cisco
implementation).
The snmp-server trap link ietf command is used to configure your router to use the RFC2233 IETF
standards-based implementation of linkUp/linkDown traps. This command is disabled by default to
allow you to continue using the earlier Cisco implementation of linkUp/linkDown traps if you so choose.
However, please note that when using the default Cisco object definitions, linkUp/linkDown traps are not
generated correctly for sub-interfaces. In the default implementation an arbitrary value is used for the
locIfReason object in linkUp/linkDown traps for sub-interfaces, which may give you unintended results.
This is because the locIfReason object is not defined for sub-interfaces in the current Cisco implementation,
which uses OLD-CISCO-INTERFACES-MIB.my.
If you do not enable this functionality, the link trap varbind list will consist of {ifIndex, ifDescr, ifType,
locIfReason}. After you enable this functionality with the snmp-server trap link ietf command, the
varbind list will consist of {inIndex, ifAdminStatus,ifOperStatus, if Descr, ifType}. The locIfReason
object will also be conditionally included in this list depending on whether meaningful information can
be retrieved for that object. A configured sub-interface will generate retrievable information. On
non-HWIDB interfaces, there will be no defined value for locIfReason, so it will be omitted from the
trap message.
Examples
The following example shows the enabling of the RFC 2233 linkUp/linkDown traps, starting in
privileged EXEC mode:
FR-733
SNMP Commands
snmp-server trap link
Related Commands
Command
Description
FR-734
78-11740-02
SNMP Commands
snmp-server trap-source
snmp-server trap-source
To specify the interface (and hence the corresponding IP address) that an Simple Network Management
Protocol (SNMP) trap should originate from, use the snmp-server trap-source global configuration
command. To remove the source designation, use the no form of the command.
snmp-server trap-source interface
no snmp-server trap-source
Syntax Description
interface
Defaults
No interface is specified.
Command Modes
Global configuration
Command History
Release
Modification
10.0
Interface from which the SNMP trap originates. The argument includes the
interface type and number in platform-specific syntax (for example,
type/slot/port).
Usage Guidelines
When an SNMP trap or inform is sent from a Cisco SNMP server, it has a notification address of
whatever interface it happened to go out of at that time. Use this command monitor notifications from a
particular interface.
Examples
The following example specifies that the IP address for interface Ethernet 0 is the source for all SNMP
notifications:
Router(config)# snmp-server trap-source ethernet 0
The following example specifies that the IP address for the ethernet interface in slot2, port 1 is the source
for all SNMP notifications:
Router(config)# snmp-server trap-source ethernet 2/1
Related Commands
Command
Description
snmp-server host
FR-735
SNMP Commands
snmp-server trap-timeout
snmp-server trap-timeout
To define how often to try resending trap messages on the retransmission queue, use the
snmp-server trap-timeout global configuration command.
snmp-server trap-timeout seconds
Syntax Description
seconds
Defaults
30 seconds
Command Modes
Global configuration
Command History
Release
Modification
10.0
Integer that sets the interval (in seconds) for resending the messages.
Usage Guidelines
Before the Cisco IOS software tries to send a trap, it looks for a route to the destination address. If there
is no known route, the trap is saved in a retransmission queue. The server trap-timeout command
determines the number of seconds between retransmission attempts.
Examples
The following example sets an interval of 20 seconds to try resending trap messages on the
retransmission queue:
snmp-server trap-timeout 20
Related Commands
Command
Description
snmp-server host
snmp-server queue-length
FR-736
78-11740-02
SNMP Commands
snmp-server user
snmp-server user
To configure a new user to a Simple Network Management Protocol (SNMP) group, use the
snmp-server user global configuration command. To remove a user from an SNMP group, use the no
form of the command.
snmp-server user username groupname [remote host [udp-port port]]
{v1 | v2c | v3 [encrypted] [auth {md5 | sha} auth-password]} [access access-list]
no snmp-server user
Syntax Description
Defaults
username
The name of the user on the host that connects to the agent.
groupname
remote host
(Optional) Specifies a remote SNMP entity to which the user belongs, and
the hostname or IP address of that entity.
udp-port port
(Optional) Specifies the UDP port number of the remote host. The default
is UDP port 162.
v1
v2c
v3
Specifies that the SNMPv3 security model should be used. Allows the use
of the encrypted and/or auth keywords.
encrypted
auth
md5
sha
auth-password
access access-list
Table 113 describes default behaviors for encryption, passwords and access lists.
Table 113
Characteristic
Default
encryption
passwords
access lists
remote users
FR-737
SNMP Commands
snmp-server user
Command Modes
Global configuration
Command History
Release
Modification
12.0(3)T
Usage Guidelines
To configure a remote user, specify the IP address or port number for the remote SNMP agent of the
device where the user resides. Also, before you configure remote users for a particular agent, configure
the SNMP engine ID, using the command snmp-server engineID with the remote option. The remote
agents SNMP engine ID is needed when computing the authentication/privacy digests from the
password. If the remote engine ID is not configured first, the configuration command will fail.
SNMP passwords are localized using the SNMP engine ID of the authoritative SNMP engine. For
informs, the authoritative SNMP agent is the remote agent. You need to configure the remote agents
SNMP engine ID in the SNMP database before you can send proxy requests or informs to it.
Related Commands
Command
Description
FR-738
78-11740-02
SNMP Commands
snmp-server view
snmp-server view
To create or update a view entry, use the snmp-server view global configuration command. To remove
the specified Simple Network Management Protocol (SNMP) server view entry, use the no form of this
command.
snmp-server view view-name oid-tree {included | excluded}
no snmp-server view view-name
Syntax Description
view-name
Label for the view record that you are updating or creating. The name
is used to reference the record.
oid-tree
included | excluded
Defaults
Command Modes
Global configuration
Command History
Release
Modification
10.0
Usage Guidelines
Other SNMP commands require a view as an argument. You use this command to create a view to be
used as arguments for other commands that create records including a view.
Two standard predefined views can be used when a view is required, instead of defining a view. One is
everything, which indicates that the user can see all objects. The other is restricted, which indicates that
the user can see three groups: system, snmpStats, and snmpParties. The predefined views are described
in RFC 1447.
The first snmp-server command that you enter enables both versions of SNMP.
Examples
The following example creates a view that includes all objects in the MIB-II subtree:
snmp-server view mib2 mib-2 included
The following example creates a view that includes all objects in the MIB-II system group and all objects
in the Cisco enterprise MIB:
snmp-server view phred system included
snmp-server view phred cisco included
FR-739
SNMP Commands
snmp-server view
The following example creates a view that includes all objects in the MIB-II system group except for
sysServices (System 7) and all objects for interface 1 in the MIB-II interfaces group:
snmp-server view agon system included
snmp-server view agon system.7 excluded
snmp-server view agon ifEntry.*.1 included
Related Commands
Command
Description
snmp-server community
FR-740
78-11740-02
SNMP Commands
snmp trap link-status
Syntax Description
Defaults
Command Modes
Interface configuration
Command History
Release
Modification
10.0
Usage Guidelines
By default, SNMP link traps are sent when an interface goes up or down. For interfaces expected to go
up and down during normal usage, such as ISDN interfaces, the output generated by these traps may not
be useful. The no form of this command disables these traps.
Examples
The following example disables the sending of SNMP link traps related to the ISDN BRI 0 interface:
interface bri 0
no snmp trap link-status
FR-741
SNMP Commands
snmp trap link-status
FR-742
78-11740-02
CDP Commands
This chapter describes commands used to monitor the router and network using Cisco Discovery
Protocol (CDP).
For system management configuration tasks and examples, refer to the Configuring Cisco Discovery
Protocol chapter in the Release 12.2 Cisco IOS Configuration Fundamentals Configuration Guide.
FR-743
CDP Commands
cdp advertise-v2
cdp advertise-v2
To enable Cisco Discovery Protocol Version 2 (CDPv2) advertising functionality on a device, use the
cdp advertise-v2 global configuration command. To disable advertising CDPv2 functionality, use the
no form of the command.
cdp advertise-v2
no cdp advertise-v2
Syntax Description
Defaults
Enabled
Command Modes
Global configuration
Command History
Release
Modification
12.0(3)T
Usage Guidelines
CDP Version 2 has three additional type-length values (TLVs): they are VTP Management Domain
Name, Native VLAN, and full/half-Duplex.
Examples
In the following example, CDP Version 2 advertisements are diabled on the router:
Router#show cdp
Global CDP information:
Sending CDP packets every 60 seconds
Sending a holdtime value of 180 seconds
Sending CDPv2 advertisements is enabled
Router#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)#no cdp advertise-v2
Router(config)#end
Router#show cdp
Global CDP information:
Sending CDP packets every 60 seconds
Sending a holdtime value of 180 seconds
Sending CDPv2 advertisements is not enabled
Router#
Related Commands
Command
Description
cdp enable
cdp run
FR-744
78-11740-02
CDP Commands
cdp enable
cdp enable
To enable Cisco Discovery Protocol (CDP) on an interface, use the cdp enable interface configuration
command. To disable CDP on an interface, use the no form of this command.
cdp enable
no cdp enable
Syntax Description
Defaults
Command Modes
Interface configuration
Command History
Release
Modification
10.3
Usage Guidelines
Note
Examples
CDP is enabled by default at the global level and on each supported interface in order to send or receive
CDP information. However, some interfaces, such as ATM interfaces, do not support CDP.
The cdp enable, cdp timer, and cdp run commands affect the operation of the IP on demand routing
feature (that is, the router odr global configuration command). For more information on the router
odr command, see the On-Demand Routing Commands chapter in the Cisco IOS IP and IP
Routing Command Reference.
Related Commands
Command
Description
cdp run
cdp timer
Specifies how often the Cisco IOS software sends CDP updates.
router odr
FR-745
CDP Commands
cdp holdtime
cdp holdtime
To specify the amount of time the receiving device should hold a Cisco Discovery Protocol (CDP) packet
from your router before discarding it, use the cdp holdtime global configuration command. To revert to
the default setting, use the no form of this command.
cdp holdtime seconds
no cdp holdtime
Syntax Description
seconds
Defaults
180 seconds
Command Modes
Global configuration
Command History
Release
Modification
10.3
Usage Guidelines
CDP packets are sent with a time to live, or hold time, value. The receiving device will discard the CDP
information in the CDP packet after the hold time has elapsed.
You can set the hold time lower than the default setting of 180 seconds if you want the receiving devices
to update their CDP info more rapidly.
The CDP hold time must be set to a higher number of seconds than the time between CDP transmissions,
which is set using the cdp timer command.
Examples
In the following example, the CDP packets being sent from the router are configured with a hold time of
60 seconds.
Router(config)#cdp holdtime 60
Related Commands
Command
Description
cdp timer
Specifies how often the Cisco IOS software sends CDP updates.
show cdp
FR-746
78-11740-02
CDP Commands
cdp log mismatch duplex
Syntax Description
Defaults
Command Modes
Global configuration
Interface configuration
Command History
Release
Modification
12.0
Usage Guidelines
When you enter the cdp log mismatch duplex command in global configuration mode, duplex
mismatches are displayed on all Ethernet interfaces on the router. When you enter this command in
interface configuration mode, only duplex mismatches for the specified Ethernet interface are displayed.
If the cdp log mismatch duplex command is disabled in global configuration mode, it cannot be
configured per interface using interface configuration mode.
Duplex mismatch can occur only on Ethernet interfaces.
Examples
The following example of the cdp log mismatch duplex command in global configuration mode enables
the display of duplex messages from all Ethernet interfaces on the router:
Router(config)# cdp log mismatch duplex
The following example of the cdp log mismatch duplex command in interface configuration mode
enables only the display of duplex messages that may be generated from Ethernet interface 2/1:
Router(config-if)# interface ethernet2/1
Router(config-if)# cdp log mismatch duplex
The following is sample output from the show running-config command. The bold text shows that the
cdp log mismatch duplex command is disabled globally.
Router# show running-config
Building configuration...
FR-747
CDP Commands
cdp log mismatch duplex
Related Commands
Command
Description
show running-config
FR-748
78-11740-02
CDP Commands
cdp run
cdp run
To enable Cisco Discovery Protocol (CDP), use the cdp run global configuration command. To disable
CDP, use the no form of this command.
cdp run
no cdp run
Syntax Description
Defaults
Enabled
Command Modes
Global configuration
Command History
Release
Modification
10.3
Usage Guidelines
Note
Examples
CDP is enabled on your router by default, which means the Cisco IOS software will receive CDP
information. CDP also is enabled on supported interfaces by default. To disable CDP on an interface, use
the no cdp enable interface configuration command.
Becuase ODR (on demand routing) uses CDP, the cdp enable, cdp timer, and cdp run commands
affect the operation of the router odr global configuration command. For more information on the
router odr command, see the Release 12.2 Cisco IOS IP Command Reference, Volume 2 of 3:
Routing Protocols document.
In the following example, CDP is disabled globally, then the user attempts to enable CDP on the Ethernet
0 interface:
Router(config)#no cdp run
Router(config)#end
Router#show cdp
% CDP is not enabled
Router#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)#int eth0
Router(config-if)#cdp enable
% Cannot enable CDP on this interface, since CDP is not running
Router(config-if)#
FR-749
CDP Commands
cdp run
Related Commands
Command
Description
cdp enable
cdp timer
Specifies how often the Cisco IOS software sends CDP updates.
router odr
FR-750
78-11740-02
CDP Commands
cdp timer
cdp timer
To specify how often the Cisco IOS software sends Cisco Discovery Protocol (CDP) updates, use the
cdp timer global configuration command. To revert to the default setting, use the no form of this
command.
cdp timer seconds
no cdp timer
Syntax Description
seconds
Defaults
60 seconds
Command Modes
Global configuration
Command History
Release
Modification
10.3
Usage Guidelines
Note
Examples
Specifies how often the Cisco IOS software sends CDP updates.
The trade-off with sending more frequent transmissions is providing up-to-date information versus using
bandwidth more often.
The cdp enable, cdp timer, and cdp run commands affect the operation of the IP on demand routing
feature (that is, the router odr global configuration command). For more information on the router
odr command, see the On-Demand Routing Commands chapter in the Cisco IOS IP and IP
Routing Command Reference.
In the following example, CDP updates are sent every 80 seconds, less frequently than the default setting
of 60 seconds. You might want to make this change if you are concerned about preserving bandwidth.
cdp timer 80
Related Commands
Command
Description
cdp enable
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.
FR-751
CDP Commands
cdp timer
Command
Description
router odr
show cdp
FR-752
78-11740-02
CDP Commands
clear cdp counters
Syntax Description
Command Modes
Privileged EXEC
Command History
Release
Modification
10.3
Examples
The following example clears the CDP counters. The show cdp traffic output shows that all of the traffic
counters have been reset to zero.
Router# clear cdp counters
Router# show cdp traffic
CDP counters:
Packets output: 0, Input: 0
Hdr syntax: 0, Chksum error: 0, Encaps failed: 0
No memory: 0, Invalid packet: 0, Fragmented: 0
Related Commands
Command
Description
FR-753
CDP Commands
clear cdp table
Syntax Description
Command Modes
Privileged EXEC
Command History
Release
Modification
10.3
Examples
The following example clears the CDP table. The output of the show cdp neighbors command shows
that all information has been deleted from the table.
Router# clear cdp table
CDP-AD: Deleted table entry for neon.cisco.com, interface Ethernet0
CDP-AD: Deleted table entry for neon.cisco.com, interface Serial0
Router# show cdp neighbors
Capability Codes: R - Router, T - Trans Bridge, B - Source Route Bridge
S - Switch, H - Host, I - IGMP
Device ID
Related Commands
Local Intrfce
Holdtme
Capability
Command
Description
Platform
Port ID
FR-754
78-11740-02
CDP Commands
show cdp
show cdp
To display global Cisco Discovery Protocol (CDP) information, including timer and hold-time
information, use the show cdp privileged EXEC command.
show cdp
Syntax Description
Command Modes
Privileged EXEC
Command History
Release
Modification
10.3
12.0(3)T
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:
router# show cdp
Global CDP information:
Sending CDP packets every 60 seconds
Sending a holdtime value of 180 seconds
Sending CDPv2 advertisements is enabled
Field
Definition
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.
FR-755
CDP Commands
show cdp
Related Commands
Command
Description
cdp advertise-v2
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.
FR-756
78-11740-02
CDP Commands
show cdp entry
Syntax Description
device-name
device-name*
You can enter an 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.
protocol
version
Command Modes
Privileged EXEC
Command History
Release
Modification
10.3
Examples
The following is sample output from the show cdp entry command with no limits. Information about
the neighbor device.cisco.com is displayed, including device ID, address and protocol, platform,
interface, hold time, and version.
Router# show cdp entry device.cisco.com
------------------------Device ID: device.cisco.com
Entry address(es):
IP address: 192.168.68.18
CLNS address: 490001.1111.1111.1111.00
DECnet address: 10.1
Platform: cisco 4500, Capabilities: Router
Interface: Ethernet0/1, Port ID (outgoing port): Ethernet0
Holdtime : 125 sec
Version :
Cisco IOS Software
Cisco IOS (tm) 4500 Software (C4500-J-M), Version 12.1(2)
Copyright (c) 1986-2000 by cisco Systems, Inc.
Compiled Mon 07-Apr-00 19:51 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
FR-757
CDP Commands
show cdp entry
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 IOS Software
Cisco IOS (tm) 4500 Software (C4500-J-M), Version 12.1(2)
Copyright (c) 1986-2000 by cisco Systems, Inc.
Compiled Mon 07-Apr-00 19:51 by joeuser
Related Commands
Command
Description
show cdp
FR-758
78-11740-02
CDP Commands
show cdp interface
Syntax Description
type
number
Command Modes
Privileged EXEC
Command History
Release
Modification
10.3
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
Holdtime is 180 seconds
Ethernet0 is up, line protocol is up, encapsulation is ARPA
Sending CDP packets every 60 seconds
Holdtime is 180 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
Holdtime is 180 seconds
Related Commands
Command
Description
show cdp
FR-759
CDP Commands
show cdp interface
Command
Description
FR-760
78-11740-02
CDP Commands
show cdp neighbors
Syntax Description
type
(Optional) Type of the interface connected to the neighbors about which you
want information.
number
detail
Command Modes
Privileged EXEC
Command History
Release
Modification
10.3
12.0(3)T
The output for the detail form of this command was expanded to include
CDP Version 2 information.
Examples
The following is sample output for 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
lab-7206
lab-as5300-1
lab-as5300-2
lab-as5300-3
lab-as5300-4
lab-3621
008024 2758E0
Local Intrfce
Eth 0
Eth 0
Eth 0
Eth 0
Eth 0
Eth 0
Eth 0
Holdtme
157
163
159
122
132
140
132
Capability
R
R
R
R
R
R S
T
Platform Port ID
7206VXR
Fas 0/0/0
AS5300
Fas 0
AS5300
Eth 0
AS5300
Eth 0
AS5300
Fas 0/0
3631-telcoFas 0/0
CAT3000
1/2
FR-761
CDP Commands
show cdp neighbors
Table 115
Field
Definition
Device ID
Local Intrfce
Holdtme
Capability
Platform
Port ID
The following is sample output for the show cdp neighbors detail command.
router#show cdp neighbors detail
------------------------Device ID: lab-7206
Entry address(es):
IP address: 172.19.169.83
Platform: cisco 7206VXR, Capabilities: Router
Interface: Ethernet0, Port ID (outgoing port): FastEthernet0/0/0
Holdtime : 123 sec
Version :
Cisco Internetwork Operating System Software
IOS (tm) 5800 Software (C5800-P4-M), Version 12.1(2)
Copyright (c) 1986-2002 by Cisco Systems, Inc.
advertisement version: 2
Duplex: half
------------------------Device ID: lab-as5300-1
Entry address(es):
IP address: 172.19.169.87
Platform: cisco AS5300, Capabilities: Router
--More-.
.
.
FR-762
78-11740-02
CDP Commands
show cdp neighbors
Table 116 describes the fields displayed in the show cdp neighbors output.
Table 116
Related Commands
Field
Definition
Device ID
Entry address(es)
Platform
Capabilities
Interface
Holdtime
Version:
advertisement version:
Duplex:
Native VLAN
Command
Description
show cdp
FR-763
CDP Commands
show cdp traffic
Syntax Description
Command Modes
Privileged EXEC
Command History
Release
Modification
10.3
Examples
The following example specifies information associated with the show cdp traffic command:
router# show cdp traffic
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
Field
Definition
Input
Hdr syntax
Chksum error
Encaps failed
FR-764
78-11740-02
CDP Commands
show cdp traffic
Table 117
Field
Definition
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
Fragmented
Input
Related Commands
Command
Description
show cdp
FR-765
CDP Commands
show cdp traffic
FR-766
78-11740-02
RMON Commands
This chapter describes commands used to monitor the router and network Remote Monitoring (RMON).
For system management configuration tasks and examples, refer to the Configuring RMON Support
chapter in the Release 12.2 Cisco IOS Configuration Fundamentals Configuration Guide.
FR-767
RMON Commands
rmon
rmon
To enable Remote Monitoring (RMON) on an Ethernet interface, use the rmon interface configuration
command. To disable RMON on the interface, use the no form of this command.
rmon {native | promiscuous}
no rmon
Syntax Description
native
Enables RMON on the Ethernet interface. In native mode, the router processes
only packets destined for this interface.
promiscuous
Defaults
Command Modes
Interface configuration
Command History
Release
Modification
11.1
Usage Guidelines
Note
This command enables RMON on Ethernet interfaces. A generic RMON console application is
recommended in order to use the RMON network management capabilities. SNMP must also be
configured. RMON provides visibility of individual nodal activity and allows you to monitor all nodes
and their interaction on a LAN segment. When the rmon command is issued, the router automatically
installs an Ethernet statistics study for the associated interface.
RMON can be very data and processor intensive. Users should measure usage effects to ensure that
router performance is not degraded and to minimize excessive management traffic overhead. Native
mode is less intensive than promiscuous mode.
All Cisco IOS software feature sets support RMON alarm and event groups. Additional RMON groups
are supported in certain feature sets. Refer to the Release Notes for feature set descriptions. As a security
precaution, support for the packet capture group allows capture of packet header information only; data
payloads are not captured.
The RMON MIB is described in RFC 1757.
Examples
The following example enables RMON on Ethernet interface 0 and allows the router to examine only
packets destined for the interface:
interface ethernet 0
rmon native
FR-768
78-11740-02
RMON Commands
rmon
Related Commands
Command
Description
rmon alarm
rmon event
Adds or removes an event in the RMON event table that is associated with
an RMON event number.
rmon queuesize
Changes the size of the queue that holds packets for analysis by the RMON
process.
show rmon
FR-769
RMON Commands
rmon alarm
rmon alarm
To set an alarm on any MIB object, use the rmon alarm global configuration command. To disable the
alarm, use the no form of this command.
rmon alarm number variable interval {delta | absolute} rising-threshold value [event-number]
falling-threshold value [event-number] [owner string]
no rmon alarm number
Syntax Description
number
variable
MIB object to monitor, which translates into the alarmVariable used in the
alarmTable of the RMON MIB.
interval
Time in seconds the alarm monitors the MIB variable, which is identical to
the alarmInterval used in the alarmTable of the RMON MIB.
delta
Tests the change between MIB variables, which affects the alarmSampleType
in the alarmTable of the RMON MIB.
absolute
Tests each MIB variable directly, which affects the alarmSampleType in the
alarmTable of the RMON MIB.
rising-threshold
value
event-number
falling-threshold
value
owner string
Defaults
No alarms configured
Command Modes
Global configuration
Command History
Release
Modification
11.2
Usage Guidelines
The MIB object must be specified as a dotted decimal value after the entry sequence (for example,
ifEntry.10.1). You cannot specify the variable name and the instance (for example, ifInOctets.1) or the
entire dotted decimal notation. The variable must be of the form entry.integer.instance.
To disable the RMON alarms, you must use the no form of the command on each configured alarm. For
example, enter no rmon alarm 1, where the 1 identifies which alarm is to be removed.
FR-770
78-11740-02
RMON Commands
rmon alarm
See RFC 1757 for more information about the RMON alarm group.
Examples
The following example configures an RMON alarm using the rmon alarm command:
rmon alarm 10 ifEntry.20.1 20 delta rising-threshold 15 1 falling-threshold 0
owner jjohnson
This example configures RMON alarm number 10. The alarm monitors the MIB variable ifEntry.20.1
once every 20 seconds until the alarm is disabled, and checks the change in the variables rise or fall. If
the ifEntry.20.1 value shows a MIB counter increase of 15 or more, such as from 100000 to 100015, the
alarm is triggered. The alarm in turn triggers event number 1, which is configured with the rmon event
command. Possible events include a log entry or a SNMP trap. If the ifEntry.20.1 value changes by 0
(falling-threshold 0), the alarm is reset and can be triggered again.
Related Commands
Command
Description
rmon
rmon event
Adds or removes an event in the RMON event table that is associated with
an RMON event number.
show rmon
FR-771
RMON Commands
rmon capture-userdata
rmon capture-userdata
To disable the packet zeroing feature that initializes the user payload portion of each Remote Monitoring
(RMON) MIB packet, use the rmon capture-userdata global configuration command. To enable packet
zeroing, use the no form of this command.
rmon capture-userdata
no rmon capture-userdata
Syntax Description
Defaults
Command Modes
Global configuration
Command History
Release
Modification
12.0(5)T
Usage Guidelines
Examples
Related Commands
Command
Description
FR-772
78-11740-02
RMON Commands
rmon collection history
Syntax Description
controlEntry
integer
owner
ownername
buckets
bucket-number
interval
seconds
Defaults
Command Modes
Interface configuration
Command History
Release
Modification
12.0(5)T
Usage Guidelines
Use the show rmon capture and show rmon matrix commands to display RMON statistics.
Examples
The following command enables an RMON MIB collection history group of statistics with an ID number
of 20 and an owner of john:
rmon collection history controlEntry 20 owner john
FR-773
RMON Commands
rmon collection history
Related Commands
Command
Description
FR-774
78-11740-02
RMON Commands
rmon collection host
Syntax Description
controlEntry
integer
owner
ownername
Defaults
Command Modes
Interface configuration
Command History
Release
Modification
12.0(5)T
Usage Guidelines
Use the show rmon hosts and show rmon matrix commands to display RMON statistics.
Examples
The following command enables an RMON collection host group of statistics with an ID number of 20
and an owner of john:
rmon collection host controlEntry 20 owner john
Related Commands
Command
Description
FR-775
RMON Commands
rmon collection matrix
Syntax Description
controlEntry
integer
owner
ownername
Defaults
Command Modes
Interface configuration
Command History
Release
Modification
12.0(5)T
Usage Guidelines
Examples
The following command enables the RMON collection matrix group of statistics with an ID number of
20 and an owner of john:
rmon collection matrix controlEntry 20 owner john
Related Commands
Command
Description
FR-776
78-11740-02
RMON Commands
rmon collection rmon1
Syntax Description
controlEntry
integer
owner
ownername
Defaults
Command Modes
Interface configuration
Command History
Release
Modification
12.0(5)T
Usage Guidelines
Examples
The following command enables the RMON collection rmon1 group of statistics with an ID of 20 and
an owner of john:
rmon collection rmon1 controlEntry 20 owner john
Related Commands
Command
Description
FR-777
RMON Commands
rmon event
rmon event
To add or remove an event in the RMON event table that is associated with an RMON event number, use
the rmon event global configuration command. To disable RMON on the interface, use the no form of
this command.
rmon event number [log] [trap community] [description string] [owner string]
no rmon event number
Syntax Description
number
log
(Optional) Generates an RMON log entry when the event is triggered and sets
the eventType in the RMON MIB to log or log-and-trap.
trap community
(Optional) SNMP community string used for this trap. Configures the setting of
the eventType in the RMON MIB for this row as either snmp-trap or
log-and-trap. This value is identical to the eventCommunityValue in the
eventTable in the RMON MIB.
description string
owner string
Defaults
No events configured
Command Modes
Global configuration
Command History
Release
Modification
11.2
Usage Guidelines
This command applies only to the Cisco 2500 series and Cisco AS5200 series.
See RFC 1757 for more information about the RMON MIB.
Examples
This example configuration creates RMON event number 1, which is defined as High ifOutErrors, and
generates a log entry when the event is triggered by an alarm. The user sdurham owns the row that is
created in the event table by this command. This configuration also generates a Simple Network
Management Protocol (SNMP) trap when the event is triggered.
FR-778
78-11740-02
RMON Commands
rmon event
Related Commands
Command
Description
rmon
show rmon
FR-779
RMON Commands
rmon queuesize
rmon queuesize
To change the size of the queue that holds packets for analysis by the Remote Monitoring (RMON)
process, use the rmon queuesize global configuration command. To restore the default value, use the no
form of this command.
rmon queuesize size
no rmon queuesize
Syntax Description
size
Defaults
64 packets
Command Modes
Global configuration
Command History
Release
Modification
11.1
Usage Guidelines
This command applies to the RMON function, which is available on Ethernet interfaces of Cisco 2500
series and Cisco AS5200 series routers only.
You might want to increase the queue size if the RMON function indicates it is dropping packets. You
can determine this from the output of the show rmon command or from the etherStatsDropEvents object
in the etherStats table. A feasible maximum queue size depends on the amount of memory available in
the router and the configuration of the buffer pool.
Examples
The following example configures the RMON queue size to be 128 packets:
rmon queuesize 128
Related Commands
Command
Description
show rmon
FR-780
78-11740-02
RMON Commands
show rmon
show rmon
To display the current RMON agent status on the router, use the show rmon EXEC command.
show rmon [alarms | capture | events | filter | history | hosts | matrix | statistics | task | topn]
Syntax Description
alarms
capture
events
filter
history
hosts
matrix
statistics
task
topn
Defaults
Command Modes
EXEC
Command History
Release
Modification
11.1
Usage Guidelines
Refer to the specific show rmon command for an example and description of the fields.
For additional information, refer to the RMON MIB described in RFC 1757.
Examples
The following is sample output from the show rmon command. All counters are from the time the router
was initialized.
Router# show rmon
145678 packets input (34562 promiscuous), 0 drops
145678 packets processed, 0 on queue, queue utilization 15/64
FR-781
RMON Commands
show rmon
Field
Description
x packets input
x promiscuous
Number of input packets that were seen by the router only because
RMON placed the interface in promiscuous mode.
x drops
Number of input packets that could not be processed because the RMON
queue overflowed.
x packets processed Number of input packets actually processed by the RMON task.
Related Commands
x on queue
Number of input packets that are sitting on the RMON queue, waiting to
be processed.
queue utilization
x/y
Command
Description
rmon
rmon alarm
rmon event
Adds or removes an event in the RMON event table that is associated with
an RMON event number.
rmon queuesize
Changes the size of the queue that holds packets for analysis by the RMON
process.
FR-782
78-11740-02
RMON Commands
show rmon alarms
Syntax Description
Command Modes
EXEC
Command History
Release
Modification
11.2
Usage Guidelines
For additional information, refer to the RMON MIB described in RFC 1757.
You must have first enabled RMON on the interface, and configured RMON alarms to display alarm
information with the show rmon alarms command.
Examples
The following is sample output from the show rmon alarms command:
Router# show rmon alarms
Alarm 2 is active, owned by manager1
Monitors ifEntry.1.1 every 30 seconds
Taking delta samples, last value was 0
Rising threshold is 15, assigned to event 12
Falling threshold is 0, assigned to event 0
On startup enable rising or falling alarm
Field
Description
Monitors ifEntry.1.1
every 30 seconds
FR-783
RMON Commands
show rmon alarms
Table 119
Related Commands
Field
Description
Rising threshold is
assigned to event
Falling threshold is
assigned to event
Alarm that may be sent when this entry is first set to valid.
Equivalent to alarmStartupAlarm in RMON.
Command
Description
rmon
rmon alarm
show rmon
FR-784
78-11740-02
RMON Commands
show rmon capture
Syntax Description
Command Modes
EXEC
Command History
Release
Modification
11.2
Usage Guidelines
For additional information, refer to the RMON MIB described in RFC 1757.
You must have first enabled RMON on the interface, and configured RMON alarms and events to display
alarm information with the show rmon capture command.
This command is available on the Cisco 2500 series and Cisco AS5200 series only.
Examples
The following is sample output from the show rmon capture command:
Router# show rmon capture
Buffer 4096 is active, owned by manager1
Captured data is from channel 4096
Slice size is 128, download size is 128
Download offset is 0
Full Status is spaceAvailable, full action is lockWhenFull
Granted 65536 octets out of 65536 requested
Buffer has been on since 00:01:16, and has captured 1 packets
Current capture buffer entries:
Packet 1 was captured 416 ms since buffer was turned on
Its length is 326 octets and has a status type of 0
Packet ID is 634, and contains the following data:
00 00 0c 03 12 ce 00 00 0c 08 9d 4e 08 00 45 00
01 34 01 42 00 00 1d 11 e3 01 ab 45 30 15 ac 15
31 06 05 98 00 a1 01 20 9f a8 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00
FR-785
RMON Commands
show rmon capture
Table 120
Field
Description
owned by manager1
Slice size is
download size is
Download offset is
Packet ID is
FR-786
78-11740-02
RMON Commands
show rmon capture
Related Commands
Command
Description
rmon
rmon alarm
rmon event
Adds or removes an event in the RMON event table that is associated with
an RMON event number.
show rmon
FR-787
RMON Commands
show rmon events
Syntax Description
Command Modes
EXEC
Command History
Release
Modification
11.2
Usage Guidelines
For additional information, refer to the RMON MIB described in RFC 1757.
You must have first enabled RMON on the interface, and configured RMON events to display alarm
information with the show rmon events command.
Examples
The following is sample output from the show rmon events command:
Router# show rmon events
Event 12 is active, owned by manager1
Description is interface-errors
Event firing causes log and trap to community rmonTrap, last fired 00:00:00
Field
Description
Description is interface-errors
community rmonTrap
last fired
FR-788
78-11740-02
RMON Commands
show rmon events
Related Commands
Command
Description
rmon
rmon event
Adds or removes an event in the RMON event table that is associated with
an RMON event number.
show rmon
FR-789
RMON Commands
show rmon filter
Syntax Description
Command Modes
EXEC
Command History
Release
Modification
11.2
Usage Guidelines
For additional information, refer to the RMON MIB described in RFC 1757.
You must have first enabled RMON on the interface, and configured RMON alarms and events to display
alarm information with the show rmon filter command.
This command is available on the Cisco 2500 series and Cisco AS5200 series only.
Examples
The following is sample output from the show rmon filter command:
Router# show rmon filter
Filter 4096 is active, and owned by manager1
Data offset is 12, with
Data of 08 00 00 00 00 00 00 00 00 00 00 00 00 00 ab 45 30 15 ac 15 31 06
Data Mask is ff ff 00 00 00 00 00 00 00 00 00 00 00 00 ff ff ff ff ff ff ff ff
Data Not Mask is 0
Pkt status is 0, status mask is 0, not mask is 0
Associated channel 4096 is active, and owned by manager1
Type of channel is acceptFailed, data control is off
Generate event index 0
Event status is eventFired, # of matches is 1482
Turn on event index is 0, turn off event index is 0
Description:
Field
Description
Unique index of the filter, its current state, and the owner,
as defined in the filterTable of RMON.
Data offset is
Data of
FR-790
78-11740-02
RMON Commands
show rmon filter
Table 122
Related Commands
Field
Description
Data Mask is
Pkt status is
status mask is
not mask is
# of matches is
Description:
Command
Description
rmon
rmon alarm
rmon event
Adds or removes an event in the RMON event table that is associated with
an RMON event number.
show rmon
FR-791
RMON Commands
show rmon history
Syntax Description
Command Modes
EXEC
Command History
Release
Modification
11.2
Usage Guidelines
For additional information, refer to the RMON MIB described in RFC 1757.
You must have first enabled RMON on the interface, and configured RMON alarms and events to display
alarm information with the show rmon history command.
This command is available on the Cisco 2500 series and Cisco AS5200 series only.
Examples
The following is sample output from the show rmon history command:
Router# show rmon history
Entry 1 is active, and owned by manager1
Monitors ifEntry.1.1 every 30 seconds
Requested # of time intervals, ie buckets, is 5
Granted # of time intervals, ie buckets, is 5
Sample # 14 began measuring at 00:11:00
Received 38346 octets, 216 packets,
0 broadcast and 80 multicast packets,
0 undersized and 0 oversized packets,
0 fragments and 0 jabbers,
0 CRC alignment errors and 0 collisions.
# of dropped packet events is 0
Network utilization is estimated at 10
Field
Description
Entry 1 is active, and owned by Unique index of the history entry, its current state, and the
manager1
owner as defined in the historyControlTable of RMON.
Monitors ifEntry.1.1
FR-792
78-11740-02
RMON Commands
show rmon history
Table 123
Field
Description
every 30 seconds
Time at the start of the interval over which this sample was
measured.
x packets
x broadcast
x multicast packets
x undersized
x oversized packets
x fragments
FR-793
RMON Commands
show rmon history
Table 123
Related Commands
Field
Description
x jabbers
x collisions
Network utilization is
estimated at
Command
Description
rmon
rmon alarm
rmon event
Adds or removes an event in the RMON event table that is associated with
an RMON event number.
show rmon
FR-794
78-11740-02
RMON Commands
show rmon hosts
Syntax Description
Command Modes
EXEC
Command History
Release
Modification
11.2
Usage Guidelines
You must have first enabled RMON on the interface, and configured RMON alarms and events to display
alarm information with the show rmon hosts command.
This command is available on the Cisco 2500 series and Cisco AS5200 series only.
For additional information, refer to the RMON MIB described in RFC 1757.
Examples
The following is sample output from the show rmon hosts command:
Router# show rmon hosts
Host Control Entry 1 is active, and owned by manager1
Monitors host ifEntry.1.1
Table size is 51, last time an entry was deleted was 00:00:00
Creation Order number is 1
Physical address is 0000.0c02.5808
Packets: rcvd 6963, transmitted 7041
Octets: rcvd 784062, transmitted 858530
# of packets transmitted: broadcast 28, multicast 48
# of bad packets transmitted is 0
Field
Description
Host Control Entry 1 is active, Unique index of the host entry, its current state, and the
and owned by manager1
owner as defined in the hostControlTable of RMON.
Monitors host ifEntry.1.1
This object identifies the source of the data for this instance
of the host function. Equivalent to hostControlDataSource
in RMON.
Table size is
FR-795
RMON Commands
show rmon hosts
Table 124
Field
Description
Time when the last entry was deleted from the hostTable.
Physical address is
Packets: rcvd
transmitted
Octets: rcvd
transmitted
# of packets transmitted:
Related Commands
Command
Description
rmon
rmon alarm
rmon event
Adds or removes an event in the RMON event table that is associated with
an RMON event number.
show rmon
FR-796
78-11740-02
RMON Commands
show rmon matrix
Syntax Description
Command Modes
EXEC
Command History
Release
Modification
11.2
Usage Guidelines
You must have first enabled RMON on the interface, and configured RMON alarms and events to display
alarm information with the show rmon matrix command.
This command is available on the Cisco 2500 series and Cisco AS5200 series only.
For additional information, refer to the RMON MIB described in RFC 1757.
Examples
The following is sample output from the show rmon matrix command:
Router# show rmon matrix
Matrix 1 is active, and owned by manager1
Monitors ifEntry.1.1
Table size is 451, last time an entry was deleted was at 00:00:00
Related Commands
Field
Description
Unique index of the matrix entry, its current state, and the
owner as defined in the matrixControlTable of RMON.
Monitors ifEntry.1.1
This object identifies the source of the data for this instance
of the matrix function. Equivalent to
matrixControlDataSource in RMON.
Size of the matrix table and the time that the last entry was
deleted.
Command
Description
rmon
rmon alarm
FR-797
RMON Commands
show rmon matrix
Command
Description
rmon event
Adds or removes an event in the RMON event table that is associated with
an RMON event number.
show rmon
FR-798
78-11740-02
RMON Commands
show rmon statistics
Syntax Description
Command Modes
EXEC
Command History
Release
Modification
11.2
Usage Guidelines
For additional information, refer to the RMON MIB described in RFC 1757.
You must have first enabled RMON on the interface, and configured RMON alarms and events to display
alarm information with the show rmon statistics command.
This command is available on the Cisco 2500 series and Cisco AS5200 series only.
Examples
The following is sample output from the show rmon statistics command:
Router# show rmon statistics
Interface 1 is active, and owned by config
Monitors ifEntry.1.1 which has
Received 60739740 octets, 201157 packets,
1721 broadcast and 9185 multicast packets,
0 undersized and 0 oversized packets,
0 fragments and 0 jabbers,
0 CRC alignment errors and 32 collisions.
# of dropped packet events (due to lack of resources): 511
# of packets received of length (in octets):
64: 92955, 65-127: 14204, 128-255: 1116,
256-511: 4479, 512-1023: 85856, 1024-1518:2547
Field
Description
Monitors ifEntry.1.1
FR-799
RMON Commands
show rmon statistics
Table 126
Field
Description
x packets
x broadcast
x multicast packets
x undersized
x oversized packets
x fragments
x jabbers
x collisions
FR-800
78-11740-02
RMON Commands
show rmon statistics
Table 126
Field
Description
# of packets received of length Separates the received packets (good and bad) by packet
(in octets):
size in the given ranges (64, 65 to 127,128 to 255, 256 to
511, 512 to 1023, 1024 to 1516).
Related Commands
Command
Description
rmon
rmon alarm
rmon event
Adds or removes an event in the RMON event table that is associated with
an RMON event number.
show rmon
FR-801
RMON Commands
show rmon topn
Syntax Description
Command Modes
EXEC
Command History
Release
Modification
11.2
Usage Guidelines
For additional information, refer to the RMON MIB described in RFC 1757.
You must have first enabled RMON on the interface, and configured RMON events to display alarm
information with the show rmon events command.
This command is available on the Cisco 2500 series and Cisco AS5200 series only.
Examples
The following is sample output from the show rmon topn command:
Router# show rmon topn
Host Entry 1 of report 1 is active, owned by manager1
The rate of change is based on hostTopNInPkts
This report was last started at 00:00:00
Time remaining in this report is 0 out of 0
Hosts physical address is 00ad.beef.002b
Requested # of hosts: 10, # of hosts granted: 10
Report # 1 of Top N hosts entry 1 is recording
Host 0000.0c02.5808 at a rate of 12
Field
Description
The rate of change is based on Variable for each host that the hostTopNRate variable is
hostTopNInPkts
based on.
This report was last started at
FR-802
78-11740-02
RMON Commands
show rmon topn
Table 127
Field
Description
out of
Host address.
Requested # of hosts:
# of hosts granted:
Related Commands
Command
Description
rmon
rmon alarm
rmon event
Adds or removes an event in the RMON event table that is associated with
an RMON event number.
show rmon
FR-803
RMON Commands
show rmon topn
FR-804
78-11740-02
FR-805
buckets-of-history-kept
To set the number of history buckets that are kept during the operation lifetime of the SAA, use the
buckets-of-history-kept SAA RTR configuration command. To return to the default value, use the no
form of this command.
buckets-of-history-kept size
no buckets-of-history-kept
Syntax Description
size
Defaults
50 buckets
Command Modes
Command History
Release
Modification
11.2
Usage Guidelines
Number of history buckets kept during the lifetime of the operation. The
default is 50 buckets.
History collection and statistics capturing is enabled for the following SAA operations: ICMP Echo,
SNA Echo, ICMP PathEcho, UDP Echo, TcpConnect, DNS, and DLSW. History collection is not
supported for HTTP and Jitter (UDP+) operations.
By default, history is not collected. When a problem arises where history is useful (for example, a large
number of timeouts are occurring), you can configure the lives-of-history-kept SAA RTR configuration
command to collect history. You can optionally adjust the buckets-of-history-kept, filter-for-history,
and samples-of-history-kept SAA RTR configuration commands.
When the number of buckets reaches the size specified, no further history for this life is stored.
Note
Collecting history increases the RAM usage. Only collect history when you think there is a problem
in the network. For general network response time information, use the statistics gathering feature of
SAA.
If history is collected, each bucket contains one or more history entries from the operation. When the
operation type is pathEcho, an entry is created for each hop along the path that the operation takes to
reach its destination. The type of entry stored in the history table is controlled by the filter-for-history
SAA RTR configuration command. The total number of entries stored in the history table is controlled
by the combination of samples-of-history-kept, buckets-of-history-kept, and lives-of-history-kept
SAA RTR configuration commands.
FR-806
78-11740-02
Each time the SAA starts an operation, a new bucket is created until the number of history buckets
matches the specified size or the operations lifetime expires. History buckets do not wrap. The
operations lifetime is defined by the rtr schedule global configuration command. The operation starts
an SAA operation based on the seconds specified by the frequency SAA RTR configuration command.
Examples
The following example configures operation 1 to keep 25 history buckets during the lifetime of the
operation lifetime:
Router(config)# rtr
Router(config-rtr)#
Router(config-rtr)#
Router(config-rtr)#
Related Commands
1
type echo protocol ipIcmpEcho 172.16.161.21
buckets-of-history-kept 25
lives-of-history-kept 1
Command
Description
filter-for-history
Defines the type of information kept in the history table for the
SA Agent operation.
lives-of-history-kept
Sets the number of lives maintained in the history table for the SA Agent
operation.
rtr
rtr schedule
samples-of-history-kept
Sets the number of entries kept in the history table per bucket for the
SA Agent operation.
FR-807
data-pattern
To specify the data pattern in an SAA udpEcho operation to test for data corruption, use the data pattern
SAA RTR configuration mode command. To remove the data pattern specification, use the no form of
this command.
data-pattern hex-pattern
no data-pattern hex-pattern
Syntax Description
hex-pattern
Defaults
Command Modes
Command History
Release
Modification
12.1(1)T
Usage Guidelines
The data-pattern command allows users to specify a alphanumeric character string to verify that
operation payload does not get corrupted in either direction (source-to-destination (SD) or
destination-to-source (DS)).
For Cisco IOS Release 12.2, the data-pattern command is applicable to the udpEcho operation only.
This command also applies to the Frame Relay operation in 12.2(1)T and later T releases.
Examples
Related Commands
Command
Description
show rtr collection-statistics Displays statistical errors for all SAA operations or the specified
operation.
FR-808
78-11740-02
distributions-of-statistics-kept
To set the number of statistic distributions kept per hop during the lifetime operation of the SAA, use the
distributions-of-statistics-kept SAA RTR configuration command. To return to the default value, use
the no form of this command.
distributions-of-statistics-kept size
no distributions-of-statistics-kept
Syntax Description
size
Defaults
1 distribution
Command Modes
Command History
Release
Modification
11.2
Usage Guidelines
Note
In most situations, you do not need to change the statistic distribution size for the SAA. Only change the
size when distributions are needed (for example, when performing statistical modeling of your network).
Increasing the distributions also increases the RAM usage. The total number of statistics distributions
captured will be: the value of distributions-of-statistics-kept times the value of
hops-of-statistics-kept times the value of paths-of-statistics-kept times the value of
hours-of-statistics-kept.
When the number of distributions reaches the size specified, no further distribution information is stored.
Examples
The following example sets the distribution to 5 and the distribution interval to 10 ms. This setting means
that the first distribution will contain statistics from 0 to 9 ms, the second distribution will contain
statistics from 10 to 19 ms, the third distribution will contain statistics from 20 to 29 ms, the fourth
distribution will contain statistics from 30 to 39 ms, and the fifth distribution will contain statistics from
40 ms to infinity.
Router(config)# rtr
Router(config-rtr)#
Router(config-rtr)#
Router(config-rtr)#
1
type echo protocol ipIcmpEcho 172.16.161.21
distributions-of-statistics-kept 5
statistics-distribution-interval 10
Related Commands
FR-809
Command
Description
hops-of-statistics-kept
Sets the number of hops for which statistics are maintained per path
for the SAA operation.
hours-of-statistics-kept
Sets the number of hours for which statistics are maintained for the
SAA operation.
paths-of-statistics-kept
Sets the number of paths for which statistics are maintained per hour
for the SAA operation.
rtr
statistics-distribution-interval Sets the time interval for each statistics distribution kept for the
SA Agent.
FR-810
78-11740-02
filter-for-history
To define the type of information kept in the history table for an SAA operation, use the
filter-for-history SAA RTR configuration command. To return to the default value, use the no form of
this command.
filter-for-history {none | all | overThreshold | failures}
no filter-for-history {none | all | overThreshold | failures}
Syntax Description
none
all
overThreshold
Only packets that are over the threshold are kept in the history table.
failures
Only packets that fail for any reason are kept in the history table.
Defaults
Command Modes
Command History
Release
Modification
11.2
Usage Guidelines
Use the filter-for-history command to control what gets stored in the history table for the SAA. To
control how much history gets saved in the history table, use the lives-of-history-kept,
buckets-of-history-kept, and the samples-of-history-kept SAA RTR configuration commands.
An operation can collect history and capture statistics. By default, history is not collected. When a
problem arises where history is useful (for example, a large number of timeouts are occurring), you can
configure the lives-of-history-kept command to collect history.
Note
Examples
Collecting history increases the RAM usage. Only collect history when you think there is a problem.
For general network response time information, use statistics.
In the following example, only operation packets that fail are kept in the history table:
Router(config)# rtr
Router(config-rtr)#
Router(config-rtr)#
Router(config-rtr)#
1
type echo protocol ipIcmpEcho 172.16.161.21
lives-of-history-kept 1
filter-for-history failures
FR-811
Related Commands
Command
Description
buckets-of-history-kept Sets the number of history buckets that are kept during the lifetime of the
SAA.
lives-of-history-kept
Sets the number of lives maintained in the history table for the SAA
operation.
rtr
samples-of-history-kept Sets the number of entries kept in the history table per bucket for the SAA
operation.
FR-812
78-11740-02
frequency
To set the rate at which a specified SAA operation is sent into the network, use the frequency SAA RTR
configuration command. To return to the default value, use the no form of this command.
frequency seconds
no frequency
Syntax Description
seconds
Defaults
60 seconds
Command Modes
Command History
Release
Modification
11.2
Usage Guidelines
Note
If an individual SAA operational probe takes longer to execute than the specified frequency value, a
statistics counter called busy is incremented rather than sending a second probe.
We recommend that you do not set the frequency value to less than 60 seconds for the following
reasons: It is not needed when keeping statistics (the default), and it can slow down the WAN because
of the potential overhead that numerous operations can cause.
The value specified for the frequency command cannot be less than the value specified for the timeout
SAA RTR configuration command.
Examples
The following example configures SAA IP/ICMP Echo operation 1 to send a probe every 90 seconds:
Router(config)# rtr 1
Router(config-rtr)# type echo protocol ipIcmpEcho 172.16.1.176
Router(config-rtr)# frequency 90
Related Commands
Command
Description
rtr
timeout
Sets the amount of time the SAA operation waits for a response from its
request packet.
FR-813
hops-of-statistics-kept
To set the number of hops for which statistics are maintained per path for the SAA operation, use the
hops-of-statistics-kept SAA RTR configuration command. To return to the default value, use the no
form of this command.
hops-of-statistics-kept size
no hops-of-statistics-kept
Syntax Description
size
Defaults
Number of hops for which statistics are maintained per path. The default is
16 hops for type pathEcho and 1 hop for type echo.
Command Modes
Command History
Release
Modification
11.2
Usage Guidelines
One hop is the passage of a timed packet from this router to another network device. The other network
device is assumed to be a device along the path to the destination (including the destination) when the
operation type is pathEcho, or just the destination when the type is echo.
When the number of hops reaches the size specified, no further hop information is stored.
Examples
The following example monitors the statistics of operation 2 for only 10 hops:
Router(config)# rtr 2
Router(config-rtr)# type pathecho protocol ipIcmpEcho 172.16.1.177
Router(config-rtr)# hops-of-statistics-kept 10
Related Commands
Command
Description
distributions-of-statistics-kept
Sets the number of statistic distributions kept per hop during the
lifetime of the SAA.
hours-of-statistics-kept
Sets the number of hours for which statistics are maintained for
the SAA operation.
paths-of-statistics-kept
Sets the number of paths for which statistics are maintained per
hour for the SAA operation.
FR-814
78-11740-02
Command
Description
rtr
statistics-distribution-interval
Sets the time interval for each statistics distribution kept for the
SAA.
FR-815
http-raw-request
To explicitly specify the options for a GET request for an SAA HTTP operation, use the
http-raw-request command in SAA RTR configuration mode.
http-raw-request
Syntax Description
Defaults
None.
Command Modes
Command History
Release
Modification
12.0(5)T
Usage Guidelines
Using the http-raw-request command puts you in HTTP Raw Request configuration mode, indicated
by the (config-rtr-http) router prompt.
The http-raw-request command should follow the type http operation raw command. Use the
raw-request option when you wish to explicitly specify the content of an HTTP request. Use HTTP 1.0
commands in HTTP Raw Request configuration mode.
The SAA will specify the content of an HTTP request for you if you use the type http operation get
command. SA Agent will send the HTTP request, receive the reply, and report RTT statistics (including
the size of the page returned).
Examples
In the following example, SAA operation 6 is created and configured as an HTTP operation. The HTTP
GET command is explicitly specified:
Router(config)# rtr 6
Router(config-rtr)# type http operation raw url http://www.cisco.com
Router(config-rtr)# http-raw-request
Router(config-rtr-http)# GET /index.html HTTP/1.0\r\n
Router(config-rtr-http)# \r\n
Router(config-rtr-http)# exit
Router(config)# rtr schedule 6 start-time now
Related Commands
Command
Description
type http
FR-816
78-11740-02
hours-of-statistics-kept
To set the number of hours for which statistics are maintained for the SAA operation, use the
hours-of-statistics-kept SAA RTR configuration command. To return to the default value, use the no
form of this command.
hours-of-statistics-kept hours
no hours-of-statistics-kept
Syntax Description
hours
Defaults
2 hours
Command Modes
Command History
Release
Modification
11.2
Usage Guidelines
Number of hours that the router maintains statistics. The default is 2 hours.
When the number of hours exceeds the specified value, the statistics table wraps (that is, the oldest
information is replaced by newer information).
This command sets the amount of time statistics are kept for use by the show rtr collection-statistics
command and show rtr distribution command.
Examples
Related Commands
Command
Description
distributions-of-statistics-kept
Sets the number of statistic distributions kept per hop during the
lifetime of the SAA.
hops-of-statistics-kept
Sets the number of hops for which statistics are maintained per
path for the SAA operation.
paths-of-statistics-kept
Sets the number of paths for which statistics are maintained per
hour for the SAA operation.
rtr
statistics-distribution-interval
Sets the time interval for each statistic distribution kept for the
SA Agent.
FR-817
lives-of-history-kept
To set the number of lives maintained in the history table for the SAA operation, use the
lives-of-history-kept SAA RTR configuration command. To return to the default value, use the no form
of this command.
lives-of-history-kept lives
no lives-of-history-kept
Syntax Description
lives
Defaults
0 lives
Command Modes
Command History
Release
Modification
11.2
Usage Guidelines
Number of lives maintained in the history table for the operation. If you
specify 0 lives, history is not collected for the operation.
The number of lives you can specify is dependent on the type of operation you are configuring. Use the
lives-of-history-kept ? command to determine the available options.
The default value of 0 lives means that history is not collected for the operation.
To disable history collection, use no lives-of-history-kept command rather than the filter-for-history
none SAA RTR configuration command. The no lives-of-history-kept command disables history
collection before an operation is attempted, while the filter-for-history command causes the SAA to
check for history inclusion after the operation attempt is made.
When the number of lives exceeds the specified value, the history table wraps (that is, the oldest
information is replaced by newer information).
When an operation makes a transition from pending to active, a life starts. When the life of an operation
ends, the operation makes a transition from active to pending.
Examples
FR-818
78-11740-02
Related Commands
Command
Description
buckets-of-history-kept Sets the number of history buckets that are kept during the lifetime of the
SAA.
filter-for-history
Defines the type of information kept in the history table for the SAA
operation.
rtr
samples-of-history-kept Sets the number of entries kept in the history table per bucket for the
SA Agent operation.
FR-819
lsr-path
To define a loose source routing (LSR) path for a Cisco SAA IP echo operation, use the lsr-path SAA
RTR configuration command. To remove the definition, use the no form of this command.
lsr-path {hostname | ip-address} [{hostname | ip-address} ...]
no lsr-path
Syntax Description
{hostname | ip-address}
Defaults
Command Modes
Command History
Release
Modification
12.0(3)T
Usage Guidelines
The maximum number of hops available is eight when an LSR path is configured.
Examples
In the following example, the LSR path is defined for SAA echo operation 1. The target destination for
the operation is at 172.16.1.176. The first hop on the LSR path is 172.18.4.149. The second hop on the
LSR path is 172.18.16.155.
Router(config)# rtr 1
Router(config-rtr)# type echo protocol ipIcmpEcho 172.16.1.176
Router(config-rtr)# lsr-path 172.18.4.149 172.18.26.155
Related Commands
Command
Description
rtr
FR-820
78-11740-02
owner
To configure the Simple Network Management Protocol (SNMP) owner of an SAA operation, use the
owner SAA RTR configuration command. To return to the default value, use the no form of this
command.
owner text
no owner
Syntax Description
text
Defaults
No owner is specified.
Command Modes
Command History
Release
Modification
11.2
Name of the SNMP owner from 0 to 255 ASCII characters. The default is
none.
Usage Guidelines
The owner name contains one or more of the following: ASCII form of the network management
stations transport address, network management station name (that is, the domain name), and network
management personnels name, location, or phone number. In some cases, the agent itself will be the
owner of the operation. In these cases, the name can begin with agent.
Examples
The following example sets the owner of operation 1 to 172.16.1.189 cwb.cisco.com John Doe RTP
555-1212:
Router(config)# rtr 1
Router(config-rtr)# type echo protocol ipIcmpEcho 172.16.1.176
Router(config-rtr)# owner 172.16.1.189 cwb.cisco.com John Doe RTP 555-1212
Related Commands
Command
Description
rtr
FR-821
paths-of-statistics-kept
To set the number of paths for which statistics are maintained per hour for the SAA operation, use the
paths-of-statistics-kept SAA RTR configuration command. To return to the default value, use the no
form of this command.
paths-of-statistics-kept size
no paths-of-statistics-kept
Syntax Description
size
Defaults
Number of paths for which statistics are maintained per hour. The default is
5 paths for type pathEcho and 1 path for type echo.
Command Modes
Command History
Release
Modification
11.2
Usage Guidelines
A path is the route the request packet of the operation takes through the network to get to its destination.
The operation may take a different path to reach its destination for each SAA operation.
When the number of paths reaches the size specified, no further path information is stored.
Examples
The following example maintains statistics for only 3 paths for operation 2:
Router(config)# rtr 2
Router(config-rtr)# type pathEcho protocol ipIcmpEcho 172.16.1.177
Router(config-rtr)# paths-of-statistics-kept 3
Related Commands
Command
Description
distributions-of-statistics-kept
Sets the number of statistic distributions kept per hop during the
lifetime of the SA.
hops-of-statistics-kept
Sets the number of hops for which statistics are maintained per
path for the SAA operation.
hours-of-statistics-kept
Sets the number of hours for which statistics are maintained for
the SAA operation.
FR-822
78-11740-02
Command
Description
rtr
statistics-distribution-interval
Sets the time interval for each statistics distribution kept for the
SAA.
FR-823
request-data-size
To set the protocol data size in the payload of the SAA operations request packet, use the
request-data-size SAA RTR configuration command. To return to the default value, use the no form of
this command.
request-data-size byte
no request-data-size
Syntax Description
byte
Defaults
1 byte
Command Modes
Command History
Release
Modification
11.2
Size of the protocol data in the payload of the request packet of the
operation. Range is 0 to the maximum of the protocol. The default is 1 byte.
Usage Guidelines
When the protocol name has the suffix appl, the packet uses both a request and respond data size (see
the response-data-size SAA RTR configuration command), and the data size is 12 bytes smaller than
the normal payload size (this 12 bytes is the ARR Header used to control send and data response sizes).
Examples
The following example sets the request packet size to 40 bytes for operation 3:
Router(config)# rtr 3
Router(config-rtr)# type echo protocol snalu0echoappl cwbc0a
Router(config-rtr)# request-data-size 40
Related Commands
Command
Description
response-data-size
Sets the protocol data size in the payload of the SAA operations response
packet.
rtr
FR-824
78-11740-02
response-data-size
To set the protocol data size in the payload of an SAA operations response packet, use the
response-data-size SAA RTR configuration command. To return to the default value, use the no form
of this command.
response-data-size byte
no response-data-size
Syntax Description
byte
Defaults
0 bytes
Command Modes
Command History
Release
Modification
11.2
Usage Guidelines
Size of the protocol data in the payload in the operations response packet.
For appl protocols, the default is 0 bytes. For all others, the default is the
same value as the request-data-size.
Note that these protocols are defined with the type command that end in appl (for example,
snalu0echoappl). When the protocol ends in appl, the response data size is 12 bytes smaller than
normal payload size.
Examples
The following example configures the response packet size of snaLU0 Echo operation 3 to 1440 bytes:
Router(config)# rtr 3
Router(config-rtr)# type echo protocol snalu0echoappl cwbc0a
Router(config-rtr)# response-data-size 1440
Related Commands
Command
Description
request-data-size
Sets the protocol data size in the payload of the SAA operations request
packet.
rtr
FR-825
rtr
To begin configuring an SAA operation by entering SAA RTR configuration mode, use the rtr command
in global configuration mode. To remove all configuration information for an operation, including the
schedule of the operation, reaction configuration, and reaction triggers, use the no form of this
command.
rtr op-number
no rtr op-number
Syntax Description
op-number
Defaults
None
Command Modes
Global configuration
Command History
Release
Usage Guidelines
Operation number used for the identification of the SAA operation you wish
to configure.
Modification
11.2
12.2(11)T
The rtr command is used to configure Cisco Service Assurance Agent (SAA) operations. Use this
command to specify an identification number for the operation you are about to configure. After you
enter this command, you will enter the SAA RTR configuration mode, indicated by the (config-rtr)
router prompt. The Related Commands table lists the commands you can use in SAA RTR
configuration mode.
For detailed information on the configuration of the Cisco SAA feature, see the Network Monitoring
Using Cisco Service Assurance Agent chapter in the Cisco IOS Configuration Fundamentals
Configuration Guide, Release 12.2.
SAA allows a maximum of 500 operations.
Debugging is supported only on the first 32 operation numbers.
After you configure a operation, you must schedule the operation. For information on scheduling a
operation, refer to the rtr schedule global configuration command. You can also optionally set reaction
triggers for the operation. For information on reaction triggers, refer to the rtr reaction-configuration
and rtr reaction-trigger global configuration commands.
Note
After you schedule an operation with the rtr schedule global configuration command, you cannot
modify the configuration of the operation. To modify the configuration of the operation after it is
scheduled, use the no rtr command. You can now reenter the operations configuration with the rtr
command.
FR-826
78-11740-02
To display the current configuration settings of the operation, use the show rtr configuration EXEC
command.
Examples
In the following example, operation 1 is configured to perform end-to-end response time operations
using an SNA LU Type 0 connection with the host name cwbc0a. Only the type SAA RTR configuration
command is required; all others are optional.
Router(config)# rtr
Router(config-rtr)#
Router(config-rtr)#
Router(config-rtr)#
Router(config-rtr)#
Router(config)#
Note
Related Commands
1
type echo protocol snalu0echoappl cwbc0a
request-data-size 40
response-data-size 1440
exit
If operation 1 already existed and it has not been scheduled, you are placed into SAA RTR
configuration command mode. If the operation already exists and has been scheduled, this command
will fail.
Command
Description
buckets-of-history-kept
Sets the number of history buckets that are kept during an SAA
operations lifetime.
distributions-of-statistics-kept
filter-for-history
frequency
hops-of-statistics-kept
Sets the number of hops for which statistics are maintained per
path for the SAA operation.
hours-of-statistics-kept
Sets the number of hours for which statistics are maintained for
SAA operations.
lives-of-history-kept
lsr path
owner
paths-of-statistics-kept
Sets the number of paths for which statistics are maintained per
hour for an SAA operation.
request-data-size
response-data-size
samples-of-history-kept
Sets the number of entries kept in the history table for an SAA
operation.
statistics-distribution-interval
tag
FR-827
Command
Description
threshold
timeout
tos
type dlsw
type tcpConnect
verify-data
FR-828
78-11740-02
rtr key-chain
To enable SAA control message authentication and specify an MD5 key chain, use the rtr key-chain
global configuration command. To remove control message authentication, use the no form of this
command.
rtr key-chain name
no rtr key-chain
Syntax Description
name
Defaults
None
Command Modes
Global configuration
Command History
Release
Modification
12.0(3)T
Usage Guidelines
The authentication configuration on the SAA collector and SAA Responder must be the same. Both sides
must configure the same key chain or both sides must not use authentication.
Examples
In the following example, the SAA control message uses MD5 authentication, and the key chain name
is CSAA:
Router(config)# rtr key-chain csaa
Related Commands
Command
Description
rtr
FR-829
rtr low-memory
To specify how much unused memory must be available to allow SAA configuration, use the
rtr low-memory global configuration command. To remove the type configuration for the operation, use
the no form of this command.
rtr low-memory value
no rtr low-memory
Syntax Description
value
Defaults
Command Modes
Global configuration
Command History
Release
Modification
12.0(5)T
Usage Guidelines
The rtr low-memory command allows the user to specify the amount of memory that the SAA can use.
If the amount of available free memory falls below the value specified in the rtr low-memory command,
then the SAA will not allow new operations to be configured. If this command is not used, the default
low-memory value is 25 percent. This means that if 75 percent of system memory has been utilized you
will not be able to configure any SAA characteristics.
The value of the rtr low-memory command should not exceed the amount of free memory available on
the system. To determine the amount of free memory available on the system, use the show memory
EXEC command.
Examples
In the following example, the router is configured so that no less than 2 MB of memory will be free for
RTR configuration:
Router(config)# rtr low-memory 2000000
Related Commands
Command
Description
rtr
show memory
FR-830
78-11740-02
rtr reaction-configuration
To configure certain actions to occur based on events under the control of the SAA, use the rtr
reaction-configuration global configuration command. To return to the default values of the operation,
use the no form of this command.
rtr reaction-configuration operation-number [verify-error-enable] [connection-loss-enable]
[timeout-enable] [threshold-falling milliseconds] [threshold-type option] [action-type
option]
no rtr reaction-configuration operation-number
Syntax Description
operation-number
verify-error-enable
threshold-falling
milliseconds
threshold-type option
(Optional) Specify the algorithm used by the SAA to calculate over and
falling threshold violations. The value for option can be one of the
following keywords:
FR-831
action-type option
Defaults
Command Modes
Global configuration
FR-832
78-11740-02
Command History
Usage Guidelines
Release
Modification
11.2
12.1(1)T
Triggers are used for diagnostics purposes and are not used in normal operation.
You can use triggers to assist you in determining where delays are happening in the network when
excessive delays are being seen on an end-to-end basis.
The reaction applies only to attempts to the target (that is, attempts to any hops along the path in
pathEcho do not generate reactions).
Note
Examples
Keywords are not case sensitive and are shown in mixed case for readability only.
In the following example, operation 19 sends an SNMP trap when there is an over or falling threshold
violation:
Router(config)# rtr reaction-configuration 19 threshold-type immediate action-type
trapOnly
Figure 2 shows that an alert (rising trap) would be issued immediately when the response time exceeds
the rising threshold and a resolution (falling trap) would be issued immediately when the response time
drops below the falling threshold.
Figure 2
Rising threshold
= Threshold violation
Falling threshold
= Resolution
Time
Related Commands
Command
Description
rtr
rtr reaction-trigger
Defines a second SAA operation to make the transition from a pending state
to an active state when one of the trigger action-type options are defined with
the rtr reaction-configuration global configuration command.
threshold
Sets the rising threshold (hysteresis) that generates a reaction event and
stores history information for the SAA operation.
timeout
Sets the amount of time the SAA operation waits for a response from its
request packet.
S4793
= Alert
FR-833
rtr reaction-trigger
To define a second SAA operation to make the transition from a pending state to an active state when
one of the trigger action-type options are defined with the rtr reaction-configuration global
configuration command, use the rtr reaction-trigger global configuration command. To remove the
trigger combination, use the no form of this command.
rtr reaction-trigger operation-number target-operation
no rtr reaction-trigger operation
Syntax Description
operation-number
Number of the operation in the active state that has the action-type set with
the rtr reaction-configuration global configuration command.
target-operation
Defaults
Command Modes
Global configuration
Command History
Release
Modification
11.2
Usage Guidelines
Triggers are usually used for diagnostics purposes and are not used in normal operation.
Examples
In the following example, the state of operation 1 is changed from pending state to active state when
action-type of operation 2 occurs:
Router(config)# rtr reaction-trigger 2 1
Related Commands
Command
Description
rtr
rtr reaction-configuration
rtr schedule
FR-834
78-11740-02
rtr reset
To perform a shutdown and restart of the SAA, use the rtr reset global configuration command.
rtr reset
Syntax Description
Defaults
Command Modes
Global configuration
Command History
Release
Modification
11.2
Usage Guidelines
Caution
Use the rtr reset command only in extreme situations such as the incorrect configuration of a number
of operations.
The rtr reset command stops all operations, clears SAA RTR configuration information, and returns the
SAA feature to the startup condition. This command does not reread the SAA RTR configuration stored
in startup-config in NVRAM. You must retype the configuration or perform a config memory command.
Examples
Related Commands
Command
Description
rtr
FR-835
rtr responder
To enable the SAA Responder feature, use the rtr responder global configuration command. To disable
the SAA Responder, use the no form of this command.
rtr responder [type {udpEcho | tcpConnect} [ipaddress ipaddr] port port]
no rtr responder [type {udpEcho | tcpConnect} [ipaddress ipaddr] port port]
Syntax Description
type udpEcho
(Optional) Specifies that the responder will accept and return udpEcho
operation packets.
Note
type tcpConnect
(Optional) Specifies that the responder will accept and return tcpConnect
operation packets.
ipaddress ipaddr
(Optional) Specifies the IP address that the operation will be received at.
port port
(Optional) Specifies the port number that the operation will be received on.
Defaults
None
Command Modes
Global configuration
Command History
Release
Modification
12.0(3)T
12.1(1)T
Usage Guidelines
This command is used on the destination device for SAA operations to enable UPD Echo, TCP Connect,
and Jitter (UDP+) operations on non-native interfaces.
The type, ipaddr, and port keywords enable the SAA Responder to respond to probe packets without
receiving Control Protocol packets. The applicable protocols are Jitter, udpEcho, and tcpConnect.
However, note that if you use these keywords, packet loss statistics will not be able to be generated for
the operation, because the Responder will not be able to determine the order of the received packets.
Examples
FR-836
78-11740-02
Related Commands
Command
Description
rtr
FR-837
rtr restart
To restart an SAA operation, use the rtr restart global configuration command.
rtr restart operation-number
Syntax Description
operation-number
Defaults
Command Modes
Global configuration.
Command History
Release
Modification
12.1(1)T
Usage Guidelines
To restart an operation, the operation should be in an active state (as defined in the rtr
reaction-configuration command).
SAA allows a maximum of 500 operations.
This command does not have a no form.
Examples
FR-838
78-11740-02
rtr schedule
To configure the time parameters for an SAA operation, use the rtr schedule global configuration
command. To stop the operation and place it in the default state (pending), use the no form of this
command.
rtr schedule operation-number [life {forever | seconds}] [start-time
{hh:mm[:ss] [month day | day month] | pending | now | after hh:mm::ss}] [ageout seconds]
no rtr schedule operation-number
Syntax Description
operation-number
life seconds
life forever
start-time
start-time
hh:mm[:ss]
(Optional) Specifies an absolute start time using hour, minute, and (optionally)
second. Use the 24-hour clock notation. For example, start-time 01:02 means
start at 1:02 a.m., and start-time 13:01:30 means start at 1:01 p.m. and 30
seconds. The current day is implied unless you specify a month and day.
month
(Optional) Name of the month to start the operation in. If month is not specified,
the current month is used. Use of this argument requires that a day be specified
as well. You can specify the month with the full english name, or using the first
three letters of the month.
day
(Optional) Number of the day (in the range 1 to 31) to start the operation on. If
a day is not specified, the current day is used. Use of this argument requires that
a month be specified as well.
start-time after
hh:mm:ss
(Optional) Indicates that the operation should start hh hours, mm minutes, and
ss seconds after this command was entered.
ageout seconds
Defaults
The operation is placed in a pending state (that is, the operation is enabled but not actively collecting
information).
Command Modes
Global configuration
FR-839
Command History
Usage Guidelines
Release
Modification
11.2
12.1(1)T
After you schedule the operation with the rtr schedule command, you cannot change the configuration
of the operation. To change the configuration of the operation, use the no form of the rtr global
configuration command and reenter the configuration information.
If the operation is in a pending state, you can define the conditions under which the operation makes the
transition from pending to active with the rtr reaction-trigger and rtr reaction-configuration global
configuration commands. When the operation is in an active state, it immediately begins collecting
information.
The following time line shows the age-out process of the operation:
W----------------------X----------------------Y----------------------Z
where:
W is the time the operation was configured with the rtr global configuration command.
X is the start time or start of life of the operation (that is, when the operation became active).
Y is the end of life as configured with the rtr schedule global configuration command (life seconds
have counted down to zero).
Age out starts counting down at W and Y, is suspended between X and Y, and is reset to its configured
size at Y.
It is possible for the operation to age out before it executes (that is, Z can occur before X). To ensure that
this does not happen, the difference between the operations configuration time and start time (X and W)
must be less than the age-out seconds.
Note
Examples
The total RAM required to hold the history and statistics tables is allocated at this time. This is to
prevent router memory problems when the router gets heavily loaded and to lower the amount of
overhead the feature causes on a router when it is active.
In the following example, operation 25 begins actively collecting data at 3:00 p.m. on April 5. This
operation will age out after 12 hours of inactivity, which can be before it starts or after it has finished
with its life. When this operation ages out, all configuration information for the operation is removed
(that is, the configuration information is no longer in the running-config in RAM).
Router(config)# rtr schedule 25 life 43200 start-time 15:00 apr 5 ageout 43200
In the following example, operation 1 begins collecting data after a 5 minute delay:
Router(config)# rtr schedule 1 start after 00:05:00
In the following example, operation 3 begins collecting data immediately and is scheduled to run
indefinitely:
Router(config)# rtr schedule 3 start-time now life forever
FR-840
78-11740-02
Related Commands
Command
Description
rtr
rtr reaction-configuration Configures certain actions to occur based on events under the control of
the SAA.
rtr reaction-trigger
FR-841
samples-of-history-kept
To set the number of entries kept in the history table per bucket for the SAA operation, use the
samples-of-history-kept SAA RTR configuration command. To return to the default value, use the no
form of this command.
samples-of-history-kept samples
no samples-of-history-kept
Syntax Description
samples
Defaults
Number of entries kept in the history table per bucket. The default is
16 entries for type pathEcho and 1 entry for type echo.
Command Modes
Command History
Release
Modification
11.2
Usage Guidelines
Use the samples-of-history-kept command to control how many entries are saved in the history table.
To control the type of information that gets saved in the history table, use the filter-for-history
command. To set how many buckets get created in the history table, use the buckets-of-history-kept
command.
An operation can collect history and capture statistics. By default, history is not collected. When a
problem arises where history is useful (for example, a large number of timeouts are occurring), you can
configure the lives-of-history-kept SAA RTR configuration command to collect history.
Note
Examples
Collecting history increases the usage of RAM. Only collect history when you think there is a
problem. For general network response time information, use statistics.
In the following example, ten entries are kept in the history table for each of the lives of operation 3:
Router(config)# rtr
Router(config-rtr)#
Router(config-rtr)#
Router(config-rtr)#
1
type pathecho protocol ipIcmpEcho 172.16.1.176
lives-of-history-kept 3
samples-of-history-kept 10
FR-842
78-11740-02
Related Commands
Command
Description
buckets-of-history-kept Sets the number of history buckets that are kept during the lifetime of the
SAA.
filter-for-history
Defines the type of information kept in the history table for the SAA
operation.
lives-of-history-kept
Sets the number of lives maintained in the history table for the SAA
operation.
rtr
FR-843
Syntax Description
tabular
full
Defaults
Full format
Command Modes
EXEC
Command History
Release
Modification
11.2
Usage Guidelines
Use the show rtr application command to display information such as supported operation types and
supported protocols.
Examples
The following is sample output from the show rtr application command in full format:
router#show rtr application
Response Time Reporter
Version: 2.2.0 Round Trip Time MIB
Max Packet Data Size (ARR and Data): 16384
Time of Last Change in Whole RTR: 03:34:44.000 UTC Sun Feb 11 2001
System Max Number of Entries: 500
Number of Entries configured:5
Number of active Entries:5
Number of pending Entries:0
Number of inactive Entries:0
Supported Operation Types
Type of Operation to Perform: echo
Type of Operation to Perform: pathEcho
Type of Operation to Perform: udpEcho
Type of Operation to Perform: tcpConnect
Type of Operation to Perform: http
Type of Operation to Perform: dns
Type of Operation to Perform: jitter
Type of Operation to Perform: dlsw
Type of Operation to Perform: dhcp
Type of Operation to Perform: ftp
FR-844
78-11740-02
Protocol
Protocol
Protocol
Protocol
Protocol
Protocol
Protocol
Protocol
Protocol
Protocol
Protocol
Protocol
Supported Protocols
Type: ipIcmpEcho
Type: ipUdpEchoAppl
Type: snaRUEcho
Type: snaLU0EchoAppl
Type: snaLU2EchoAppl
Type: ipTcpConn
Type: httpAppl
Type: dnsAppl
Type: jitterAppl
Type: dlsw
Type: dhcp
Type: ftpAppl
Related Commands
Command
Description
Displays configuration values including all defaults for all SAA operations
or the specified operation.
FR-845
Syntax Description
Command Modes
EXEC
Command History
Release
Modification
12.0(3)T
Usage Guidelines
Use the show rtr authentication command to display information such as supported operation types and
supported protocols.
Examples
The following is sample output from the show rtr application command:
Router# show rtr authentication
RTR control message uses MD5 authentication, key chain name is: rtr
Related Commands
Command
Description
FR-846
78-11740-02
Effective with Cisco IOS Release 12.3(14)T, the show rtr collection-statistics command is replaced by
the show ip sla monitor collection-statistics command. See the show ip sla monitor
collection-statistics command for more information.
To display statistical errors for all Cisco IOS IP Service Level Agreements (IP SLAs) operations or a
specified operation, use the show rtr collection-statistics command in EXEC mode.
show rtr collection-statistics [operation-number]
Syntax Description
operation-number
Defaults
Command Modes
EXEC
Command History
Release
Modification
11.2
12.0(5)T
The output for this command was expanded to show information for Jitter
operations.
Usage Guidelines
12.1
12.1(1)T
The output for this command was expanded to show information for the FTP
operation type and for One Way Delay Jitter operations.
12.2(8)T, 12.2(8)S
12.2(11)T
12.3(4)T
Output (MOS and ICPIF scores) for the Jitter (codec) operation type was
added.
12.3(7)T
12.3(14)T
Use the show rtr collection-statistics command to display information such as the number of failed
operations and the failure reason. You can also use the show rtr distribution-statistics and
show rtr totals-statistics commands to display additional statistical information.
This command shows information collected over the past two hours, unless you specify a different
amount of time using the hours-of-statistics-kept command.
FR-847
For One Way Delay Jitter operations, the clocks on each device must be synchronized using NTP (or
GPS systems). If the clocks are not synchronized, one way measurements are discarded. (If the sum of
the source to destination (SD) and the destination to source (DS) values is not within 10 percent of the
round trip time, the one way measurement values are assumed to be faulty, and are discarded.)
Note
Examples
This command does not support the IP SLAs ICMP path jitter operation.
The following shows sample output from the show rtr collection-statistics command in full format.
Router# show rtr collection-statistics 1
Collected Statistics
Entry Number: 1
Start Time Index: *17:15:41.000
Path Index: 1
Hop in Path Index: 1
Number of Failed Operations due
Number of Failed Operations due
Number of Failed Operations due
Number of Failed Operations due
Number of Failed Operations due
Number of Failed Operations due
Number of Failed Operations due
Target Address: 172.16.1.176
to
to
to
to
to
to
to
a Disconnect: 0
a Timeout: 0
a Busy: 0
a No Connection: 0
an Internal Error: 0
a Sequence Error: 0
a Verify Error: 0
The following example shows output from the show rtr collection-statistics command when the specified
operation is an HTTP operation:
Router# show rtr collection-statistics 2
Collected Statistics
Entry Number:2
HTTP URL:http://172.20.150.200
Start Time:*00:01:16.000 UTC Mon Nov 1 2003
Comps:1
OvrTh:0
DNSTimeOut:0
TCPTimeOut:0
TraTimeOut:0
DNSError:0
HTTPError:0
IntError:0
Busies:0
RTTMin:343
RTTMax:343
RTTSum:343
RTTSum2:117649
DNSRTT:0
TCPConRTT:13
TransRTT:330
MesgSize:1771
The following is sample output from the show rtr collection-statistics command, where operation 2 is
a Jitter operation that includes One Way statistcis:
Router# show rtr collection-statistics
Collected Statistics
Entry Number: 2
FR-848
78-11740-02
41
133
114347
114332
The values shown indicate the aggregated values for the current hour. RTT stands for Round-Trip-Time.
SD stands for Source-to-Destination. DS stands for Destination-to-Source. OW stands for One Way.
Table 128 describes the significant fields shown in this output.
Output for Jitter (codec) Operations
The following is sample output from the show rtr collection-statistics command, where operation 10 is
a Jitter (codec) operation:
Router# show rtr collection-statistics 10
Entry number: 10
Start Time Index: 13:18:49.904 PST Mon Jun 24 2002
Number of successful operations: 2
Number of operations over threshold: 0
Number of failed operations due to a Disconnect: 0
Number of failed operations due to a Timeout: 0
Number of failed operations due to a Busy: 0
Number of failed operations due to a No Connection: 0
Number of failed operations due to an Internal Error: 0
Number of failed operations due to a Sequence Error: 0
Number of failed operations due to a Verify Error: 0
Voice Scores:
MinOfICPIF: 0
MaxOfICPIF: 0
MinOfMOS: 0
MaxOfMOS: 0
RTT Values:
NumOfRTT: 122
RTTAvg: 2
RTTMin: 2
RTTMax: 3
RTTSum: 247
RTTSum2: 503
Packet Loss Values:
PacketLossSD: 0 PacketLossDS: 0
PacketOutOfSequence: 0 PacketMIA: 0
PacketLateArrival: 0
InternalError: 0
Busies: 0
PacketSkipped: 78 <<<<<===========
Jitter Values:
MinOfPositivesSD: 1
MaxOfPositivesSD: 1
NumOfPositivesSD: 9
SumOfPositivesSD: 9
Sum2PositivesSD: 9
MinOfNegativesSD: 1
MaxOfNegativesSD: 1
NumOfNegativesSD: 8
SumOfNegativesSD: 8
Sum2NegativesSD: 8
MinOfPositivesDS: 1
MaxOfPositivesDS: 1
NumOfPositivesDS: 6
SumOfPositivesDS: 6
Sum2PositivesDS: 6
MinOfNegativesDS: 1
MaxOfNegativesDS: 1
NumOfNegativesDS: 7
SumOfNegativesDS: 7
Sum2NegativesDS: 7
Interarrival jitterout: 0
Interarrival jitterin: 0
One Way Values:
FR-849
NumOfOW: 0
OWMinSD: 0
OWMinDS: 0
Table 128
OWMaxSD: 0
OWMaxDS: 0
OWSumSD: 0
OWSumDS: 0
OWSum2SD: 0
OWSum2DS: 0
Field
Description
Voice Scores:
ICPIF
the values for Io, Iq, and Idte are set to zero,
the value Idd is computed based on the measured one way delay,
MinOfICPIF:
MaxOfICPIF:
Mos
MinOfMos:
MaxOfMos:
RTT Values:
NumOfRTT
RTTSum
RTTSum2
PacketLossSD
FR-850
78-11740-02
Table 128
Field
Description
PacketLossDS
PacketOutOfSequence
PacketMIA
PacketLateArrival
PacketSkipped
The number of packets that are not sent during the IP SLAs jitter
operation.
InternalError
Busies
The number of times this operation could not be started because the
previously scheduled run was not finished.
Jitter Values:
NumOfJitterSamples:
MinOfPositivesSD
MaxOfPositivesSD
NumOfPositivesSD
SumOfPositivesSD
Sum2PositivesSD
MinOfNegativesSD
MaxOfNegativesSD
NumOfNegativesSD
SumOfNegativesSD
Sum2NegativesSD
Interarrival jitterout:
Interarrival jitterin:
FR-851
Table 128
Field
Description
NumOfOW
OWMinSD
OWMaxSD
OWSumSD
OWSum2SD
The DS values show the same information as above for Destination-to-Source Jitter values.
Related Commands
Command
Description
FR-852
78-11740-02
Syntax Description
operation
tabular
full
Defaults
Command Modes
EXEC
Command History
Release
Modification
11.2
Examples
The following is sample output from the show rtr configuration command in full format:
Router# show rtr configuration 1
Complete Configuration Table (includes defaults)
Entry Number: 1
Owner: Sample Owner
Tag: Sample Tag Group
Type of Operation to Perform: echo
Reaction and History Threshold (milliseconds): 5000
Operation Frequency (seconds): 60
Operation Timeout (milliseconds): 5000
Verify Data: FALSE
Status of Entry (SNMP RowStatus): active
Protocol Type: ipIcmpEcho
Target Address: 172.16.1.176
Request Size (ARR data portion): 1
Response Size (ARR data portion): 1
Life (seconds): 3600
Next Start Time: Start Time already passed
Entry Ageout (seconds): 3600
Connection Loss Reaction Enabled: FALSE
Timeout Reaction Enabled: FALSE
Threshold Reaction Type: never
Threshold Falling (milliseconds): 3000
Threshold Count: 5
Threshold Count2: 5
Reaction Type: none
Number of Statistic Hours kept: 2
FR-853
Related Commands
FR-854
78-11740-02
Command
Description
FR-855
Syntax Description
operation
tabular
full
Defaults
Command Modes
EXEC
Command History
Release
Modification
11.2
Usage Guidelines
The sum of the completions times squared (used to calculate standard deviation)
You can also use the show rtr collection-statistics and show rtr totals-statistics commands to display
additional statistical information.
Examples
The following is sample output from the show rtr distributions-statistics command in tabular format:
Router# show rtr distributions-statistics
Captured Statistics
Multiple Lines per Entry
Line 1
Entry
StartT
Pth
Hop
Dst
Comps
OvrTh
SumCmp
=
=
=
=
=
=
=
=
Entry Number
Start Time of Entry (hundredths of seconds)
Path Index
Hop in Path Index
Time Distribution Index
Operations Completed
Operations Completed Over Thresholds
Sum of Completion Times (milliseconds)
FR-856
78-11740-02
Line 2
SumCmp2L = Sum of Completion Times
SumCmp2H = Sum of Completion Times
TMax
= Completion Time Maximum
TMin
= Completion Time Minimum
Entry StartT
Pth Hop Dst Comps
SumCmp2L
SumCmp2H
TMax
1
17417068
1
1
1
2
8192
0
64
Related Commands
Command
Description
show rtr collection-statistics Displays statistical errors for all SAA operations or the specified
operation.
show rtr configuration
FR-857
Syntax Description
operation-number
tabular
full
Defaults
Command Modes
EXEC
Command History
Release
Modification
11.2
Usage Guidelines
Table 129 lists the Response Return values used in the output of the show rtr history command. If the
default (tabular) format is used, the Response Return description is displayed as a code in the Sense
column. If the full format is used, the Response Return is displayed as indicated in the Description
column.
Table 129
Code
Description
Okay.
Disconnected.
Over threshold.
Timeout.
Busy.
Not connected.
Dropped.
Sequence error.
Verify error.
10
Application
specific.
FR-858
78-11740-02
Examples
The following is sample output from the show rtr history command in tabular format:
Router# show rtr history
Point by point History
Multiple Lines per Entry
Line 1
Entry
= Entry Number
LifeI
= Life Index
BucketI = Bucket Index
SampleI = Sample Index
SampleT = Sample Start Time
CompT
= Completion Time (milliseconds)
Sense
= Response Return Code
Line 2 has the Target Address
Entry LifeI
BucketI
SampleI
SampleT
2
1
1
1
17436548
AB 45 A0 16
2
1
2
1
17436551
AC 12 7 29
2
1
2
2
17436551
AC 12 5 22
2
1
2
3
17436552
AB 45 A7 22
2
1
2
4
17436552
AB 45 A0 16
Related Commands
CompT
16
Sense
1
Command
Description
Displays configuration values including all defaults for all SAA operations
or the specified operation.
FR-859
Effective with Cisco IOS Release 12.3(14)T, the show rtr operational-state command is replaced by
the show ip sla monitor statistics command. See the show ip sla monitor statistics command for more
information.
To display the operational state of all Cisco IOS IP Service Level Agreements (IP SLAs) operations or
a specified operation, use the show rtr operational-state command in EXEC mode.
show rtr operational-state [operation-number]
Syntax Description
operation-number
Defaults
Command Modes
EXEC
Command History
Release
Modification
11.2
12.0(5)T
12.1
12.2(8)T
12.2(8)S
12.3(4)T
Output (MOS and ICPIF scores) for the Jitter (codec) operation type was added.
12.3(7)T
12.3(14)T
This command was replaced by the show ip sla monitor statistics command.
Usage Guidelines
Use the show rtr operational-state command to display the current state of IP SLAs operations,
including how much life the operation has left, whether the operation is active, and the completion time.
The output will also include the monitoring data returned for the last (most recently completed)
operation.
Examples
The following example shows basic sample output from the show rtr operational-state command:
Router# show rtr operational-state
Current Operational State
Entry Number: 3
Modification Time: *22:15:43.000 UTC Sun Feb 11 2001
Diagnostics Text:
Last Time this Entry was Reset: Never
Number of Octets in use by this Entry: 1332
FR-860
78-11740-02
The following example shows sample output from the show rtr operational-state command when the
specified operation is a Jitter (codec) operation:
Router# show rtr operational-state 1
Entry number: 1
Modification time: 13:18:38.012 PST Mon Jun 24 2002
Number of Octets Used by this Entry: 10392
Number of operations attempted: 2
Number of operations skipped: 0
Current seconds left in Life: Forever
Operational state of entry: Active
Last time this entry was reset: Never
Connection loss occurred: FALSE
Timeout occurred: FALSE
Over thresholds occurred: FALSE
Latest RTT (milliseconds): 2
Latest operation start time: *13:18:42.896 PST Mon Jun 24 2002
Latest operation return code: OK
Voice Scores:
ICPIF Value: 0 MOS score: 0
RTT Values:
NumOfRTT: 61
RTTAvg: 2
RTTMin: 2
RTTMax: 3
RTTSum: 123
RTTSum2: 249
Packet Loss Values:
PacketLossSD: 0 PacketLossDS: 0
PacketOutOfSequence: 0 PacketMIA: 0
PacketLateArrival: 0
InternalError: 0
Busies: 0
PacketSkipped: 39
<<<<<<==========
Jitter Values:
MinOfPositivesSD: 1
MaxOfPositivesSD: 1
NumOfPositivesSD: 1
SumOfPositivesSD: 1
Sum2PositivesSD: 1
MinOfNegativesSD: 1
MaxOfNegativesSD: 1
NumOfNegativesSD: 1
SumOfNegativesSD: 1
Sum2NegativesSD: 1
MinOfPositivesDS: 0
MaxOfPositivesDS: 0
NumOfPositivesDS: 0
SumOfPositivesDS: 0
Sum2PositivesDS: 0
MinOfNegativesDS: 0
MaxOfNegativesDS: 0
NumOfNegativesDS: 0
SumOfNegativesDS: 0
Sum2NegativesDS: 0
Interarrival jitterout: 0
Interarrival jitterin: 0
One Way Values:
NumOfOW: 0
OWMinSD: 0
OWMaxSD: 0
OWSumSD: 0
OWSum2SD: 0
OWMinDS: 0
OWMaxDS: 0
OWSumDS: 0
OWSum2DS: 0
The values shown indicate the values for the last IP SLAs operation. RTT stands for Round-Trip-Time.
SD stands for Source-to-Destination. DS stands for Destination-to-Source. OW stands for One Way. The
* symbol in front of the time stamps indicates the time is synchronized using NTP or SNTP. Table 130
describes the significant fields shown in this output.
FR-861
Table 130
Field
Description
Voice Scores:
ICPIF:
the values for Io, Iq, and Idte are set to zero,
MOS:
RTT Values:
NumOfRTT
RTTSum
RTTSum2
PacketLossSD
PacketLossDS
PacketOutOfSequence
PacketMIA
The number of packets lost where the direction (SD or DS) cannot
be determined (MIA: missing in action).
PacketLateArrival
PacketSkipped
The number of packets that are not sent during the IP SLAs jitter
operation.
FR-862
78-11740-02
Table 130
Field
Description
InternalError
Busies
The number of times this operation could not be started because the
previously scheduled run was not finished.
Jitter Values:
NumOfJitterSamples:
MinOfPositivesSD
MaxOfPositivesSD
NumOfPositivesSD
SumOfPositivesSD
Sum2PositivesSD
MinOfNegativesSD
MaxOfNegativesSD
NumOfNegativesSD
SumOfNegativesSD
Sum2NegativesSD
Interarrival jitterout:
Interarrival jitterin:
NumOfOW
OWMinSD
OWMaxSD
OWSumSD
OWSum2SD
FR-863
Related Commands
Command
Description
FR-864
78-11740-02
Syntax Description
operation-number
tabular
full
Defaults
Command Modes
EXEC
Command History
Release
Modification
11.2
Usage Guidelines
Use the show rtr reaction-trigger command to display the configuration status and operational state of
target operations that will be triggered as defined with the rtr reaction-configuration global command.
Examples
The following is sample output from the show rtr reaction-trigger command in full format:
Router# show rtr reaction-trigger 1
Reaction Table
Entry Number: 1
Target Entry Number: 2
Status of Entry (SNMP RowStatus): active
Operational State: pending
Related Commands
Command
Description
Displays configuration values including all defaults for all SAA operations
or the specified operation.
FR-865
Syntax Description
Command Modes
EXEC
Command History
Release
Modification
12.0(3)T
Usage Guidelines
Use the show rtr responder command to display information about recent sources of SAA control
messages, such as who has sent recent control messages and who has sent invalid control messages.
Examples
The following is sample output from the show rtr responder command:
Router# show rtr responder
RTR Responder is: Enabled
Number of control message received: 19 Number
Recent sources:
4.0.0.1 [19:11:49.035 UTC Sat Dec
4.0.0.1 [19:10:49.023 UTC Sat Dec
4.0.0.1 [19:09:48.707 UTC Sat Dec
4.0.0.1 [19:08:48.687 UTC Sat Dec
4.0.0.1 [19:07:48.671 UTC Sat Dec
of errors: 1
2
2
2
2
2
1995]
1995]
1995]
1995]
1995]
Related Commands
Command
Description
FR-866
78-11740-02
Syntax Description
number
tabular
full
Defaults
Command Modes
EXEC
Command History
Release
Modification
11.2
Usage Guidelines
You can also use the show rtr distributions-statistics and show rtr collection-statistics commands to
display additional statistical information.
Examples
The following is sample output from the show rtr totals-statistics command in full format:
Router# show rtr totals-statistics
Statistic Totals
Entry Number: 1
Start Time Index: *17:15:41.000 UTC Thu May 16 1996
Age of Statistics Entry (hundredths of seconds): 48252
Number of Initiations: 10
FR-867
Related Commands
Command
Description
FR-868
78-11740-02
statistics-distribution-interval
To set the time interval for each statistics distribution kept for the SAA, use the
statistics-distribution-interval SAA RTR configuration command. To return to the default value, use
the no form of this command.
statistics-distribution-interval milliseconds
no statistics-distribution-interval
Syntax Description
milliseconds
Defaults
20 ms
Command Modes
Command History
Release
Modification
11.2
Number of milliseconds (ms) used for each statistics distribution kept. The
default is 20 ms.
Usage Guidelines
In most situations, you do not need to change the statistical distribution interval or size. Only change the
interval or size when distributions are needed, for example, when performing statistical modeling of your
network. To set the statistical distributions size, use the distributions-of-statistics-kept SAA RTR
configuration command.
Examples
In the following example, the distribution is set to five and the distribution interval is set to 10 ms. This
means that the first distribution will contain statistics from 0 to 9 ms, the second distribution will contain
statistics from 10 to 19 ms, the third distribution will contain statistics from 20 to 29 ms, the fourth
distribution will contain statistics from 30 to 39 ms, and the fifth distribution will contain statistics from
40 ms to infinity.
Router(config)# rtr
Router(config-rtr)#
Router(config-rtr)#
Router(config-rtr)#
Related Commands
1
type echo protocol ipIcmpEcho 172.28.161.21
distribution-of-statistics-kept 5
statistics-distribution-interval 10
Command
Description
distributions-of-statistics-kept
Sets the number of statistic distributions kept per hop during the
SAA operations lifetime.
hops-of-statistics-kept
Set the number of hops for which statistics are maintained per
path for the SAA operation.
FR-869
Command
Description
hours-of-statistics-kept
Sets the number of hours for which statistics are maintained for
the SAA operation.
paths-of-statistics-kept
Sets the number of paths for which statistics are maintained per
hour for the SAA operation.
rtr
FR-870
78-11740-02
tag
To create a user-specified identifier for an SAA operation, use the tag SAA RTR configuration
command. To remove a tag from a operation, use the no form of this command.
tag text
no tag
Syntax Description
text
Defaults
Command Modes
Command History
Release
Modification
11.2
Usage Guidelines
Examples
Related Commands
Command
Description
rtr
FR-871
threshold
To set the rising threshold (hysteresis) that generates a reaction event and stores history information for
the SAA operation, use the threshold SAA RTR configuration command. To return to the default value,
use the no form of this command.
threshold milliseconds
no threshold
Syntax Description
milliseconds
Defaults
5000 ms
Command Modes
Command History
Release
Modification
11.2
Usage Guidelines
The value specified for the threshold command must not exceed the value specified for the timeout SAA
RTR configuration command.
The threshold value is used by the rtr reaction-configuration and filter-for-history commands.
Examples
Related Commands
Command
Description
filter-for-history
Defines the type of information kept in the history table for the SAA
operation.
rtr
rtr reaction-configuration Configures certain actions to occur based on events under the control of
the SAA.
FR-872
78-11740-02
timeout
To set the amount of time the SAA operation waits for a response from its request packet, use the timeout
SAA RTR configuration command. To return to the default value, use the no form of this command.
timeout milliseconds
no timeout
Syntax Description
milliseconds
Defaults
The default timeout values vary by operation. Per the RTTMON-MIB, the defaults are:
Command Modes
Command History
Release
Modification
11.2
Usage Guidelines
Use the timeout command to set how long the operation waits to receive a response, and use the
frequency SAA RTR configuration command to set the rate at which the SAA starts an operation.
The value specified for the timeout command cannot be greater than the value specified for the
frequency command.
Examples
In the following example, the timeout for the IP/ICMP Echo operation 1 is set for 2500 ms:
Router(config)# rtr 1
Router(config-rtr)# type echo protocol ipIcmpEcho 172.16.1.176
Router(config-rtr)# timeout 2500
Related Commands
Command
Description
frequency
Sets the rate at which the SAA operation starts a response time operation.
rtr
FR-873
tos
To define a type of service (ToS) byte in the IP header of SAA operations, use the tos SAA RTR
configuration command. To return to the default value, use the no form of this command.
tos number
no tos
Syntax Description
number
Defaults
Command Modes
Command History
Release
Modification
12.0(3)T
Usage Guidelines
Service type byte in the IP header. The range is 0 to 255. The default is 0.
The type-of-service (ToS) value is an 8-bit field in IP headers. This field contains information such as
precedence and TOS. This is useful for policy-routing as well as features like CAR (Committed Access Rate),
where routers examine for TOS values.
When the type-of-service is defined for an operation, the SAA Responder will reflect the ToS value it
recieves.
Examples
In the following example, SAA operation 1 is configured as an echo probe using the IP/ICMP Echo
protocol and the destination IP address 172.16.1.175. The ToS value is set to 0x80.
Router(config)# rtr 1
Router(config-rtr)# type echo protocol ipIcmpEcho 172.16.1.176
Router(config-rtr)# tos 0x80
Related Commands
Command
Description
rtr
FR-874
78-11740-02
type dhcp
To configure a Dynamic Host Configuration Protocol SAA operation, use the type dhcp SAA RTR
configuration command. To disable a DHCP SAA operation, use the no form of this command.
type dhcp [source-ipaddr source-ipaddr] [dest-ipaddr dest-ipaddr] [option decimal-option
[circuit-id circuit-id] [remote-id remote-id] [subnet-mask subnet-mask]]
no type dhcp
Syntax Description
source-ipaddr
source-ipaddr
dest-ipaddr
dest-ipaddr
option decimal-option
(Optional) Option number. The only currently valid value is 82. DHCP
option 82 allows you to specify the circuit-id, remote-id, and/or the
subnet-mask for the destination DHCP server.
circuit-id circuit-id
remote-id remote-id
subnet-mask
subnet-mask
Defaults
Command Modes
Command History
Release
Modification
12.0(5)T
12.1(1)T
Usage Guidelines
source-ipaddr
dest-ipaddr
option 82
You must configure the type of operation before you can configure any of the other characteristics of the
operation.
If the source IP address is configured, then packets will be sent with that source address.
You may configure the ip dhcp-server command to identify the DHCP server that the DHCP operation
will measure.
If the target IP address is configured, then only that device will be measured.
FR-875
If the ip dhcp-server command is not configured and the target IP address is not configured, then DHCP
discover packets will be sent on every available IP interface.
Option 82 is called the Relay Agent Information option and is inserted by the DHCP relay agent when
forwarding client-originated DHCP packets to a DHCP server. Servers recognizing the Relay Agent
Information option may use the information to implement IP address or other parameter assignment
policies. The DHCP Server echoes the option back verbatim to the relay agent in server-to-client replies,
and the relay agent strips the option before forwarding the reply to the client.
The Relay Agent Information option is organized as a single DHCP option that contains one or more
suboptions that convey information known by the relay agent. The initial sub-options are defined for a
relay agent that is co-located in a public circuit access unit. These suboptions are as follows: a circuit-id
for the incoming circuit, a remote-id which provides a trusted identifier for the remote high-speed
modem, and a subnet-mask designation for the logical IP subnet from which the relay agent received
the client DHCP packet.
If an odd number of characters are specified for the circuit-id, a zero will be added to the end of the
string.
Examples
In the following example, SAA operation number 4 is configured as a DHCP operation enabled for
DHCP server 172.16.20.3:
Router(config)# rtr 4
Router(config-rtr)# type dhcp option 82 circuit-id 10005A6F1234
Router(config-rtr)# exit
Router(config)# ip dhcp-server 172.16.20.3
Related Commands
Command
Description
rtr
ip dhcp-server
FR-876
78-11740-02
type dlsw
To configure a data-link switching (DLSw) SAA operation, use the type dlsw SAA RTR configuration
command. To remove the type configuration for the operation, use the no form of this command.
type dlsw peer-ipaddr ipaddr
no type dlsw peer-ipaddr ipaddr
Syntax Description
peer-ipaddr
Peer destination.
ipaddr
IP address.
Defaults
None.
Command Modes
Command History
Release
Modification
12.0(5)T
Usage Guidelines
In order to configure a DLSw operation, the DLSw feature must be configured on the local and target
routers.
You must configure the type of operation before you can configure any of the other characteristics of the
operation.
The default for the optional characteristic request-data-size for a DLSw SAA operation is 0 bytes.
The default for the optional characteristic timeout for a DLSw SAA operation is 30 seconds.
Examples
In the following example, SAA operation number 4 is configured as a DLSw operation enabled for
remote peer IP address 172.21.27.11. The data size is 15 bytes.
Router(config)# rtr 4
Router(config-rtr)# type dlsw peer-ipaddr 172.21.27.11
Router(config-rtr)# request-data-size 15
FR-877
Related Commands
Command
Description
rtr
request-data-size
Sets the protocol data size in the payload of the SAA operations request
packet.
FR-878
78-11740-02
type dns
To configure a Domain Name System (DNS) SAA operation, use the type dns SAA RTR configuration
command. To remove the type configuration for the operation, use the no form of this command.
type dns target-addr {ip-address | hostname} name-server ip-address
no type dns target-addr {ip-address | hostname} name-server ip-address
Syntax Description
target-addr
{ip-address | hostname}
name-server ip-address
Defaults
Command Modes
Command History
Release
Modification
12.0(5)T
Usage Guidelines
You must configure the type of operation before you can configure any of the other characteristics of the
operation.
Examples
In the following example, SAA operation 7 is created and configured as a DNS operation using the target
IP address 172.20.2.132:
Router(config)# rtr 7
Router(config-rtr)# type dns target-addr lethe name-server 172.20.2.132
Related Commands
Command
Description
rtr
FR-879
type echo
To configure an SAA end-to-end echo response time probe operation, use the type echo SAA RTR
configuration command. To remove the operation from the configuration, use the no form of this
command.
type echo protocol protocol-type target [source-ipaddr ip-address]
no type echo protocol protocol-type target [source-ipaddr ip-address]
Syntax Description
protocol protocol-type
target
source-ipaddr ipaddr
Defaults
The default SNA host sna-application name for a SNA LU type echo is NSPEcho.
The default data size for a IP/ICMP echo operation is 28 bytes.
Command Modes
Command History
Release
Modification
11.2
12.0(5)T
Usage Guidelines
Support of echo to a protocol and pathEcho to a protocol is dependent on the protocol type and
implementation. In general most protocols support echo and few protocols support pathEcho.
FR-880
78-11740-02
Note
Keywords are not case sensitive and are shown in mixed case for readability only.
Prior to sending a operation packet to the responder, the SAA sends a control message to the Responder
to enable the destination port.
The default for the optional characteristic request-data-size for a ipIcmpEcho operation is 28 bytes.
This is the payload portion of the Icmp packet, which makes a 64 byte IP packet.
Examples
In the following example, operation 10 is created and configured as an echo probe using the IP/ICMP
Echo protocol and the destination IP address 172.16.1.175:
Router(config)# rtr 10
Router(config-rtr)# type echo protocol ipIcmpEcho 172.16.1.175
Related Commands
Command
Description
rtr
FR-881
type ftp
To configure an FTP operation, use the type ftp SAA RTR configuration command. To remove the type
configuration for the operation, use the no form of this command.
type ftp operation get url url [source-ipaddr source-ipaddr] [mode {passive | active}]
no type ftp operation get url url [source-ipaddr source-ipaddr] [mode {passive | active}]
Syntax Description
operation get
Specifies an FTP GET operation. (Support for other FTP operation types
may be added in future releases.)
url url
source-ipaddr
source-ipaddr
mode
passive
active
Defaults
Command Modes
Command History
Release
Modification
12.1(1)T
Usage Guidelines
GET is the only valid operation value. The URL must be in one of the following formats:
ftp://user:password@host/filename
ftp://host/filename
If the user and password keywords are not specified, the defaults are anonymous and test, respectively.
Examples
In the following example, an FTP operation is configured. Joe is the user and Young is the password. zxq
is the host and test is the file name.
Router(config)# rtr 3
Router(config-rtr)# type ftp operation get ftp://joe:young@zxq/test
FR-882
78-11740-02
Related Commands
Command
Description
show rtr collection-statistics Displays statistical errors for all SAA operations or the specified
operation.
show rtr operational-state
FR-883
type http
To configure a Hypertext Transfer Protocol (HTTP) SAA operation, use the type http SAA RTR
configuration command. To remove the type configuration for the operation, use the no form of this
command.
type http operation {get | raw} url url [name-server ipaddress] [version version number]
[source-ipaddr {name | ipaddr}] [source-port port number] [cache {enable | disable}]
[proxy proxy-url]
no type http operation {get | raw} url url [name-server ipaddress] [version version number]
[source-ipaddr {name | ipaddr}] [source-port port number] [cache {enable | disable}]
[proxy proxy-url]
Syntax Description
operation get
operation raw
url url
name-server
ipaddress
version
version number
source-ipaddr
name
Source name.
ipaddr
Source IP address.
source-port
port number
cache
enable
disable
proxy
proxy-url
Defaults
Command Modes
Command History
Release
Modification
12.0(5)T
FR-884
78-11740-02
Usage Guidelines
You must configure the type of operation before you can configure any of the other characteristics of the
operation.
Examples
In this example operation 5 is created and configured as an HTTP GET operation. The destination URL
is http://www.cisco.com.
Router(config)# rtr
Router(config-rtr)#
Router(config-rtr)#
Router(config)# rtr
5
type http operation get url http://www.cisco.com
exit
schedule 5 start-time now
In this example operation 6 is created and configured as an HTTP RAW operation. To use the raw request
commands, HTTP-RAW submode is entered using the http-raw-request command. The RTR
HTTP-RAWsubmode is indicated by the (config-rtr-http) router prompt.
Router(config)# rtr 6
Router(config-rtr)# type http operation raw url http://www.cisco.com
Router(config-rtr)# http-raw-request
Router(config-rtr-http)# GET /index.html HTTP/1.0\r\n
Router(config-rtr-http)# \r\n
Router(config-rtr-http)# exit
Router(config)# rtr schedule 6 start-time now
Related Commands
Command
Description
rtr
FR-885
type jitter
To configure a jitter SAA operation, use the type jitter SAA RTR configuration command. To disable a
jitter operation, use the no form of this command.
type jitter dest-ipaddr {name | ipaddr} dest-port port-number [source-ipaddr {name | ipaddr}]
[source-port port-number] [control {enable | disable}] [num-packets number-of-packets]
[interval inter-packet-interval]
no type jitter dest-ipaddr {name | ipaddr} dest-port port-number [source-ipaddr {name |
ipaddr}] [source-port port-number] [control {enable | disable}] [num-packets
number-of-packets] [interval inter-packet-interval]
Syntax Description
dest-ipaddr
name
ipaddr
Destination IP address.
dest-port
Destination port.
port-number
source-ipaddr
name
IP host name.
ipaddr
IP address.
source-port
port-number
control
enable
Enables the SAA to send a control message to the destination port prior
to sending a probe packet. This is the default value.
disable
num-packets
number-of-packets
interval
inter-packet-interval
Defaults
The default for the optional characteristic request-data-size for a SAA Jitter operation is 32 bytes of
UDP data.
Command Modes
Command History
Release
Modification
12.0(5)T
FR-886
78-11740-02
Usage Guidelines
The type jitter command configures a UDP Plus SAA operation. The UDP Plus operation is a superset
of the UDP echo operation. In addition to measuring UDP round trip time, the UDP Plus operation
measures per-direction packet-loss and Jitter. Jitter is inter-packet delay variance. Packet loss is a critical
element in SLAs, and Jitter statistics are useful for analyzing traffic in a VoIP network.
You must enable the SAA Responder on the target router before you can configure a Jitter operation.
Prior to sending a operation packet to the responder, the SAA sends a control message to the SA Agent
Responder to enable the destination port.
You must configure the type of operation before you can configure any of the other characteristics of the
operation.
Examples
In the following example, operation 6 is created and configured as a UDP+ Jitter operation using the
destination IP address 172.30.125.15, the destination port number 2000, 20 packets, and an interval of
20:
Router(config)# rtr 6
Router(config-rtr)# type jitter dest-ip 172.30.125.15 dest-port 2000 num-packets 20
interval 20
Related Commands
Command
Description
rtr
request-data-size
FR-887
type pathEcho
To configure an IP/ICMP Path Echo SAA operation, use the type pathEcho SAA RTR configuration
command. To remove the operation from the configuration, use the no form of this command.
type pathEcho protocol ipIcmpEcho {ip-address | ip-hostname}
no type pathEcho protocol ipIcmpEcho {ip-address | ip-hostname}
Syntax Description
protocol ipIcmpEcho
ip-address
ip-hostname
Defaults
None
Command Modes
Command History
Release
Modification
11.2
Usage Guidelines
Keywords are not case sensitive and are shown in mixed case for readability only.
Examples
In the following example, SAA operation 10 is created and configured as pathEcho probe using the
IP/ICMP Echo protocol and the destination IP address 172.16.1.175:
Router(config)# rtr 10
Router(config-rtr)# type pathEcho protocol ipIcmpEcho 172.16.1.175
Related Commands
Command
Description
rtr
FR-888
78-11740-02
type tcpConnect
To define a tcpConnect probe, use the type tcpConnect SAA RTR configuration command. To remove
the type configuration for the probe, use the no form of this command.
type tcpConnect dest-ipaddr {name | ipaddr} dest-port port-number [source-ipaddr {name |
ipaddr} source-port port-number] [control {enable | disable}]
no type tcpConnect dest-ipaddr {name | ipaddr} dest-port port-number
Syntax Description
dest-port port-number
control
enable
disable
Disables the SAA from sending a control message to the target prior
to sending a probe packet.
Defaults
Command Modes
Command History
Release
Modification
12.0(3)T
Usage Guidelines
You must configure an SAA operation type before you can configure any of the other characteristics of
the operation.
FR-889
The Transmission Control Protocol (TCP) Connection operation is used to discover the time it takes to
connect to the target device. This operation can be used to test virtual circuit availability or application
availability. If the target is a Cisco router, then SA Agent makes a TCP connection to any port number
specified by the user. If the destination is a non-Cisco IP host, then the user must specify a known target
port number (for example, 21 for FTP, 23 for Telnet, or 80 for HTTP Server). This operation is useful in
testing Telnet or HTTP connection times.
Examples
In the following example, SAA operation 11 is created and configured as a tcpConnect probe using the
destination IP address 172.16.1.175, and the destination port 2400:
Router(config)# rtr 11
Router(config-rtr)# type tcpConnect dest-ipaddr 172.16.1.175 dest-port 2400
Related Commands
Command
Description
rtr
FR-890
78-11740-02
type udpEcho
To define a udpEcho probe, use the type udpEcho SAA RTR configuration command. To remove the
type configuration for the probe, use the no form of this command.
type udpEcho dest-ipaddr {name | ipaddr} dest-port port-number [source-ipaddr {name |
ipaddr} source-port port-number] [control {enable | disable}]
no type udpEcho dest-ipaddr {name | ipaddr} dest-port port-number
Syntax Description
dest-port port-number
control
enable
disable
Defaults
The control protocol is enabled. Prior to sending a probe packet to the Responder, the SAA collector
sends a control message to the Responder to enable the destination port.
Command Modes
Command History
Release
Modification
12.0(3)T
Usage Guidelines
You must configure an operation type before you can configure any of the other characteristics of the
operation.
The source IP address and port number are optional. If they are not specified, SAA selects the IP address
nearest to the target and an available UDP port.
FR-891
Examples
In the following example, SAA operation 12 is created and configured as udpEcho probe using the
destination IP address 172.16.1.175 and destination port 2400:
Router# configure terminal
Router(config)# rtr 12
Router(config-rtr)# type udpEcho dest-ipaddr 172.16.1.175 dest-port 2400
Related Commands
Command
Description
rtr
FR-892
78-11740-02
verify-data
To cause the SAA operation to check each response for corruption, use the verify-data SAA RTR
configuration command. To return to the default value, use the no form of this command.
verify-data
no verify-data
Syntax Description
Defaults
Disabled
Command Modes
Command History
Release
Modification
11.2
Usage Guidelines
Caution
Examples
Do not enable this feature during normal operation because it causes unnecessary overhead.
In the following example, operation 5 is configured to verify the data for each response:
Router(config)# rtr
Router(config-rtr)#
Router(config-rtr)#
Router(config-rtr)#
Related Commands
5
type echo protocol ipIcmpEcho 172.16.1.174
response-data-size 2
verify-data
Command
Description
rtr
FR-893
FR-894
78-11740-02
WCCP Commands
This chapter provides detailed descriptions of the commands used to configure Web Cache
Communication Protocol Version 1 (WCCPv1) and Version 2 (WCCPv2) on your routing device.
For configuration tasks and examples, refer to the Network Management Using WCCP chapter in the
Release 12.2 Cisco IOS Configuration Fundamentals Configuration Guide.
Table 131 lists those commands that have been replaced since Cisco IOS Release 12.0.
Table 131
ip wccp enable
ip wccp
ip wccp redirect-list
ip wccp
ip web-cache redirect
Note
Cisco IOS Release 12.2 allows you to enable either WCCPv1 functionality or WCCPv2 functionality
on your router using the ip wccp version command. However, you must use the commands
introduced with WCCPv2 to configure WCCPv1. The original WCCPv1 configuration commands
that have been replaced (see Table 131) will no longer function.
FR-895
WCCP Commands
clear ip wccp
clear ip wccp
To remove Web Cache Communication Protocol (WCCP) statistics (counts) maintained on the router for
a particular service, use the clear ip wccp EXEC command.
clear ip wccp {web-cache | service-number}
Syntax Description
web-cache
Directs the router to remove statistics for the web cache service.
service-number
Defaults
Command Modes
EXEC
Command History
Release
Modification
11.1 CA
This command was introduced for Cisco 7200 and 7500 platforms.
11.2 P
12.0(3)T
Usage Guidelines
Use the show ip wccp and show ip wccp detail commands to display WCCP statistics. If Cisco
Cache Engines are used in your service group, the reverse proxy service is indicated by a value of 99.
Examples
In the following example, all statistics associated with the web cache service are removed:
Router# clear ip wccp web-cache
Related Commands
Command
Description
ip wccp
Directs a router to enable or disable the support for a cache engine service group.
show ip wccp
FR-896
78-11740-02
WCCP Commands
ip wccp
ip wccp
To direct a router to enable or disable the support for a cache engine service group, use the ip wccp
global configuration command. To remove the ability of a router to control support for a service group,
use the no form of this command.
ip wccp {web-cache | service-number} [group-address multicast-address] [redirect-list
access-list] [group-list access-list] [password password [0 | 7]]
no ip wccp {web-cache | service-number} [group-address multicast-address] [redirect-list
access-list] [group-list access-list] [password password [0 | 7]]
Syntax Description
web-cache
service-number
group-address
multicast-address
redirect-list access-list
group-list access-list
(Optional) Directs the router to use an access list to determine which cache
engines are allowed to participate in the service group. The access-list
argument should consist of a string of no more than 64 characters (name
or number) that specifies the access list.
password password
0|7
(Optional) Indicates the HMAC MD5 algorithm that is used to encrypt the
password. The value is generated when an encrypted password is created
for a cache engine.
Defaults
Command Modes
Global configuration
Command History
Release
Modification
12.0(3)T
FR-897
WCCP Commands
ip wccp
Usage Guidelines
This configuration command instructs a router to enable or disable the support for the Service Group
specified by the service name given. A service name may be either one of the provided standard keyword
definitions or a number representing a cache engine dynamically defined definition. Once the service is
enabled, the router can participate in the establishment of a Service Group.
Currently the only provided keyword definition to be used as a service name is web-cache. This keyword
is used to describe the existing WCCP version 1 functionality.
When the ip wccp global configuration command is issued, it instructs the router to allocate space and
enable support of the specified WCCP service for participation in a Service Group.
When the no ip wccp global configuration command is issued, it instructs the router to terminate
participation in the Service Group, deallocate space if none of the interfaces still have the service
configured, and terminate the WCCP task if no other services are configured.
Note
The ip wccp command has replaced the ip wccp enable, ip wccp redirect-list, and ip wccp
group-list commands from the version 1 implementation of WCCP.
The keywords following the service name are optional and may be specified in any order, but only may
be specified once. The following sections outline the specific usage of each of the optional forms of this
command.
ip wccp {web-cache | service-number} group-address multicast-address
A WCCP group address can be configured to set up a multicast address that cooperating routers and web
caches can use to exchange WCCP protocol messages. If such an address is used, ip multicast routing
must be enabled so that the messages using the configured group (multicast) addresses are received
correctly. To enable ip multicast routing, use the ip multicast-routing command.
This option instructs the router to use the specified multicast IP address to coalesce the I See You
responses for the Here I Am messages that it has received on this group address. The response is sent to
the group address as well. The default is for no group address to be configured, in which case all Here I
Am messages are responded to with a unicast reply.
ip wccp {web-cache | service-number} redirect-list access-list
The option instructs the router to use an access list to control the traffic that is redirected to the cache
engines of the Service Group specified by the service name given. The access-list-name argument
specifies either a number from 1 to 99 to represent a standard or extended access list number, or a name
to represent a named standard or extended access list. The access list itself specifies which traffic is
permitted to be redirected. The default is for no redirect list to be configured (all traffic is redirected).
WCCP requires that the following protocol and ports are not filtered by any access lists:
User Datagram Protocol (UDP) (protocol type 17) port 2048. This port is used for control signalling.
Blocking this type of traffic will prevent WCCP from establishing a connection between the router
and cache engines.
Generic routing encapsulation (GRE) encapsulated (protocol type 47) frames. Blocking this type of
traffic will prevent the cache engines from ever seeing the packets intercepted.
The option instructs the router to use an access list to control the cache engines allowed to participate in
the specified Service Group. The access-list parameter specifies either a number from 1 to 99 to
represent a standard access list number, or a name to represent a named standard access list. The access
list itself specifies which cache engines are permitted to participate in the Service Group. The default is
for no group list to be configured, in which case all cache engines may participate in the Service Group.
FR-898
78-11740-02
WCCP Commands
ip wccp
Note
The ip wccp {web-cache | service-number} group-list command syntax resembles the ip wccp
{web-cache | service-number} group-listen command, but these are entirely different commands.
Note that the ip wccp group-listen command is an interface configuration command, used to
configure an interface to listen for multicast notifications from a cache cluster. See the description of
the ip wccp <service> group-listen command in this chapter for more information.
ip wccp {web-cache | service-number} password password
The option instructs the router to use MD5 authentication on the messages received from the Service
Group specified by the service name given. Use this form of the command to set the password on the
router. You must also configure the same password separately on each cache engine. The password can
be up to a maximum of seven characters. Messages that do not authenticate when authentication is
enabled on the Router are discarded. The default is for no authentication password to be configured and
authentication to be disabled.
Examples
In the following example, a user configures a router to run WCCP reverse proxy service, using the
multicast address of 224.1.1.1:
Router# configure terminal
Router(config)# ip wccp 99 group-address 224.1.1.1
Router(config)# interface ethernet 0
Router(config-if)# ip wccp web-cache group-list
In the following example, a user configures a router to redirect web-related packets without a destination
of 192.168.196.51 to the cache engine:
Router# configure terminal
Router(config)# access-list 100 deny ip any host 192.168.196.51
Router(config)# access-list 100 permit ip any any
Router(config)# ip wccp redirect-list 100
Router(config)# interface Ethernet 0
Router(config-if)# ip web-cache redirect-list
Router(config-if)# end
Router#
Related Commands
Command
Description
ip wccp version
FR-899
WCCP Commands
ip wccp enable
ip wccp enable
The ip wccp enable has been replaced by the ip wccp command. See the description of the ip wccp
command in this chapter for more information.
FR-900
78-11740-02
WCCP Commands
ip wccp <service> group-listen
Syntax Description
web-cache
service-number
Defaults
Command Modes
Interface configuration
Command History
Release
Modification
12.0(3)T
Usage Guidelines
Examples
On routers that are to be members of a Service Group when IP multicast is used, the following
configuration is required:
The IP multicast address for use by the WCCP Service Group must be configured.
The interfaces on which the router wishes to receive the IP multicast address to be configured with
the ip wccp {web-cache | service-number} group-listen interface configuration command.
In the following example, a user enables the multicast packets for a web cache with a multicast address
of 224.1.1.100.
router# configure terminal
router(config)# ip wccp web-cache group-address 244.1.1.100
router(config)# interface ethernet 0
router(config-if)# ip wccp web-cache group listen
FR-901
WCCP Commands
ip wccp <service> group-listen
Related Commands
Command
Description
ip wccp
Directs a router to enable or disable the support for a WCCP cache engine
service group.
ip wccp <service>
redirect
FR-902
78-11740-02
WCCP Commands
ip wccp redirect exclude in
Syntax Description
Defaults
Command Modes
Interface configuration
Command History
Release
Modification
12.0(3)T
Usage Guidelines
This configuration command instructs the interface to exclude inbound packets from any redirection
check that may occur at the outbound interface. Note that the command is global to all the services and
should be applied to any inbound interface that you wish to exclude from redirection.
This command is intended to be used to accelerate the flow of packets from a cache engine to the internet as
well as allow for the use of the WCCPv2 Packet Return feature.
Examples
In the following example, packets arriving on Ethernet interface 0 are excluded from all WCCP
redirection checks:
Router(config)# interface ethernet 0
Router(config-if)# ip wccp redirect exclude in
Related Commands
Command
Description
ip wccp
Directs a router to enable or disable the support for a cache engine service
group.
FR-903
WCCP Commands
ip wccp redirect-list
ip wccp redirect-list
This command is now documented as part of the ip wccp {web-cache | service-number} command. See
the description of the ip wccp command in this chapter for more information.
FR-904
78-11740-02
WCCP Commands
ip wccp <service> redirect
Syntax Description
service
Specifies the service group. You can specify the web-cache keyword, or
you can specify the identification number(from 0 to 99) of the service.
redirect
out
in
Defaults
Command Modes
Interface configuration
Command History
Release
Modification
12.0(3) T
12.0(11)S
12.1(3)T
Usage Guidelines
The ip wccp service redirect in command allows you to configure WCCP redirection on an interface
receiving inbound network traffic. When the command is applied to an interface, all packets arriving at
that interface will be compared against the criteria defined by the specified WCCP service. If the packets
match the criteria, they will be redirected.
Likewise, the ip wccp service redirect out command allows you to configure the WCCP redirection
check at an outbound interface.
Tips
Be careful not to confuse the ip wccp service redirect {out | in} interface configuration command
with the ip wccp redirect exclude in interface configuration command.
Note
This command has the potential to effect the ip wccp redirect exclude in command. (These
commands have opposite functions.) If you have ip wccp redirect exclude in set on an interface and
you subsequently configure the ip wccp service redirect in command, the exclude in command
will be overridden. The opposite is also true: configuring the exclude in command will override the
redirect in command.
FR-905
WCCP Commands
ip wccp <service> redirect
Examples
In the following example, the user configures a session in which reverse proxy packets on Ethernet
interface 0 are being checked for redirection and redirected to a Cisco Cache Engine:
Router# configure terminal
Router(config)# ip wccp 99
Router(config)# interface ethernet 0
Router(config-if)# ip wccp 99 redirect ?
in
Redirect to a Cache Engine appropriate inbound packets
out Redirect to a Cache Engine appropriate outbound packets
Router(config-if)# ip wccp 99 redirect out
In the following example, the user configures a session in which HTTP traffic arriving on Ethernet
interface 0/1 will be redirected to a Cisco Cache Engine:
Router# configure terminal
Router(config)# ip wccp web-cache
Router(config)# interface ethernet 0/1
Router(config-if)# ip wccp web-cache redirect in
Related Commands
Command
Description
FR-906
78-11740-02
WCCP Commands
ip wccp version
ip wccp version
To specify which version of Web Cache Communication Protocol (WCCP) you wish to configure on
your router, use the ip wccp version global configuration command.
ip wccp version {1 | 2}
Syntax Description
Defaults
WCCPv2
Command Modes
Global configuration
Command History
Release
Modification
12.0(5)T
Examples
In the following example, the user changes the WCCP version from the default of WCCPv2 to WCCPv1,
starting in privileged EXEC mode:
router# show ip wccp
% WCCP version 2 is not enabled
router# configure terminal
router(config)# ip wccp version 1
router(config)# end
router# show ip wccp
% WCCP version 1 is not enabled
FR-907
WCCP Commands
ip web-cache redirect
ip web-cache redirect
The ip web-cache redirect interface configuration command has been replaced by the ip wccp
<service> redirect interface configuration command. The ip web-cache redirect command is no longer
supported. See the description of the ip wccp <service> redirect command in this chapter for more
information.
FR-908
78-11740-02
WCCP Commands
show ip wccp
show ip wccp
To display global statistics related to Web Cache Communication Protocol (WCCP), use the show ip
wccp command in privileged EXEC mode.
show ip wccp [service-number | web-cache] [detail | view]
Syntax Description
service-number
web-cache
detail
view
(Optional) Other members of a particular service group have or have not been
detected.
Command Modes
Privileged EXEC
Command History
Release
Modification
11.1CA
This command was introduced for Cisco 7200 and 7500 platforms.
11.2P
Usage Guidelines
12.0(3)T
12.3(7)T
The output was enhanced to display the bypass counters (process, fast, and
Cisco Express Forwarding) when WCCP is enabled.
12.2(14)SX
Support for this command was introduced on the Supervisor Engine 720.
12.2(17d)SXB
Support for this command on the Supervisor Engine 2 was extended to Cisco IOS
Release 12.2(17d)SXB.
12.2(25)S
12.3(14)T
The output was enhanced to display the maximum number of service groups.
12.2(27)SBC
12.2(33)SRA
Use the clear ip wccp command to reset the counter for the Packets Redirected information.
Use the show ip wccp service-number command to provide the Total Packets Redirected count. The
Total Packets Redirected count is the number of flows, or sessions, that are redirected.
Use the show ip wccp service-number detail command to provide the Packets Redirected count. The
Packets Redirected count is the number of flows, or sessions, that are redirected.
Use the show ip wccp web-cache detail command to provide an indication of how many flows, rather
than packets, are using Layer 2 redirection.
For cache-engine clusters using Cisco cache engines, the reverse proxy service-number is indicated by
a value of 99.
FR-909
WCCP Commands
show ip wccp
For additional information on the IP WCCP commands, refer to the Configuring Web Cache Services
Using WCCP section in the Cisco IOS Configuration Fundamentals Configuration Guide.
Examples
This section contains examples and field descriptions for the following forms of this command:
The following is sample output from the show ip wccp web-cache command:
Router# show ip wccp web-cache
Global WCCP Information:
Service Name: web-cache:
Number of Cache Engines:
1
Number of Routers:
1
Total Packets Redirected:
213
Redirect access-list:
no_linux
Total Packets Denied Redirect:
88
Total Packets Unassigned:
-noneGroup access-list:
0
Total Messages Denied to Group:
0
Total Authentication failures:
0
Field
Description
Service Name
Number of Routers
Redirect access-list
Total number of packets that were not redirected because they did
not match the access list.
Number of packets that were not redirected because they were not
assigned to any cache engine. Packets may not be assigned during
initial discovery of cache engines or when a cache is dropped
from a cluster.
Group access-list
FR-910
78-11740-02
WCCP Commands
show ip wccp
Table 132
Field
Description
The following is sample output from the show ip wccp 1 view command:
Router# show ip wccp 1 view
WCCP Router Informed of:
10.168.88.10
10.168.88.20
WCCP Cache Engines Visible
10.168.88.11
10.168.88.12
WCCP Cache Engines Not Visible:
-none-
Note
Field
Description
A list of clients that are visible to the router and other clients in
the service group.
A list of clients in the service group that are not visible to the
router and other clients in the service group.
The following example displays WCCP client information and WCCP router statistics that include the
type of services:
Router# show ip wccp 91 detail
WCCP Client information:
WCCP Client ID: 10.1.1.14
Protocol Version: 2.0
State: Usable
Redirection: GRE
Packet Return: GRE
Assignment: HASH
Initial Hash Info: 0000000000000000000000000000000000000000000000000000000000000000
Assigned Hash Info: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
Hash Allotment: 256 (100.00%)
FR-911
WCCP Commands
show ip wccp
Packets Redirected: 0
Connect Time: 00:01:56
Bypassed Packets
Process: 0
CEF: 0
The following example displays web-cache engine information and WCCP router statistics for a
particular service group:
Router# show ip wccp web-cache detail
WCCP Router information:
IP Address
Protocol Version:
WCCP Client Information
IP Address:
Protocol Version:
State:
Initial Hash Info:
Assigned Hash Info:
Hash Allotment:
Packets Redirected:
Connect Time:
10.168.88.10
2.0
10.168.88.11
2.0
Usable
AAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAA
FFFFFFFFFFFFFFFFFFFFFFFFFF
FFFFFFFFFFFFFFFFFFFFFFFFFF
256 (100.00%)
21345
00:13:46
Field
Description
The header for the area that contains fields for the IP address and
version of WCCP associated with the router connected to the
cache engine in the service group.
IP Address
Protocol Version
The header for the area that contains fields for information on
clients.
IP Address
Protocol Version
State
The initial state of the hash bucket assignment. The values show
the state of each of the 256 hash buckets. Hexadecimal digits are
used as shorthand for binary numbers with F representing 1111,
four bits set to one. If a set of four bits is F, then that hash bucket
is allocated to the client with the displayed ID. If a set of bits is 0,
then it is not allocated to the client with the displayed ID.
FR-912
78-11740-02
WCCP Commands
show ip wccp
Table 134
Field
Description
The current state of the hash bucket assignment. The values show
the state of each of the 256 hash buckets. If F is displayed, then
that hash bucket is allocated to the client with the displayed ID. If
a bit is 0 then it is not allocated to the client with the displayed
ID. In this output all the bits in the assigned field are F, indicating
that all traffic goes to that client. All 1s in the assigned field
indicates there is only one client in the service group. If there
were two clients in the group, half of the bits would have a value
of F and the other half would have a value of 0 for each client,
indicating that redirected traffic is divided equally between the
two clients.
Hash Allotment
Packets Redirected
Connect Time
The amount of time the cache engine has been connected to the
router.
The following example displays web-cache engine information and WCCP router statistics that include
the bypass counters:
Router# show ip wccp web-cache detail
WCCP Router information:
IP Address:10.168.88.10
Protocol Version:2.0
WCCP Client Information
IP Address:10.168.88.11
Protocol Version:2.0
State:Usable
Initial Hash Info:AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
Assigned Hash Info:FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
Hash Allotment:256 (100.00%)
Packets Redirected:21345
Connect Time:00:13:46
Bypassed Packets
Process:
0
Fast:
0
CEF:
250
FR-913
WCCP Commands
show ip wccp
Table 135
Related Commands
Field
Description
The header for the area that contains fields for the IP address and
the version of WCCP associated with the router connected to the
cache engine in the service group.
IP Address
Protocol Version
The header for the area that contains fields for information on
clients.
IP Address
Protocol Version
State
Hash Allotment
Packets Redirected
Connect Time
The amount of time the cache engine has been connected to the
router.
Bypassed Packets
The number of packets that have been bypassed. Process, fast, and
Cisco Express Forwarding (CEF) are switching paths within
Cisco IOS software.
Command
Description
clear ip wccp
ip wccp
ip wccp redirect
ip wccp web-cache
accelerated
show ip interface
FR-914
78-11740-02
WCCP Commands
show ip wccp web-caches
Command History
Release
Modification
11.2P, 11.1CA,
12.0
12.1
FR-915
WCCP Commands
show ip wccp web-caches
FR-916
78-11740-02
Appendixes
Numeric Values
Decimal
Hex
ASCII
Character
Meaning
Keyboard Entry
00
NUL
Null
Ctrl-@
01
SOH
Start of heading
Ctrl-A
02
STX
Start of text
Ctrl-B
03
ETX
Break/end of text
Ctrl-C
04
EOT
End of transmission
Ctrl-D
05
ENQ
Enquiry
Ctrl-E
06
ACK
Positive acknowledgment
Ctrl-F
07
BEL
Bell
Ctrl-G
08
BS
Backspace
Ctrl-H
09
HT
Horizontal tab
Ctrl-I
10
0A
LF
Line feed
Ctrl-J
11
0B
VT
Vertical tab
Ctrl-K
12
0C
FF
Form feed
Ctrl-L
13
0D
CR
Ctrl-M
Carriage return
(Equivilant to the Enter or
Return key)
14
0E
SO
Shift out
Ctrl-N
15
0F
SI
Ctrl-O
16
10
DLE
Ctrl-P
FR-919
Table 136
Numeric Values
Decimal
Hex
ASCII
Character
Meaning
17
11
DC1
18
12
DC2
19
13
DC3
20
14
DC4
21
15
NAK
22
16
SYN
Synchronous idle
23
17
ETB
24
18
CAN
Cancel
Ctrl-X
25
19
EM
End of medium
Ctrl-Y
26
1A
SUB
Substitute/end of file
Ctrl-Z
27
1B
ESC
Escape
Ctrl-[
28
1C
FS
File separator
Ctrl-\
29
1D
GS
Group separator
Ctrl-]
30
1E
RS
Record separator
Ctrl-^
31
1F
US
Unit separator
Ctrl-_
32
20
SP
Space
Space
33
21
34
22
"
"
"
35
23
36
24
37
25
38
26
&
&
&
39
27
40
28
41
29
42
2A
43
2B
44
2C
45
2D
46
2E
47
2F
48
30
Zero
49
31
One
50
32
Two
51
33
Three
Keyboard Entry
Ctrl-V
FR-920
78-11740-02
Table 136
Numeric Values
Decimal
Hex
ASCII
Character
Meaning
Keyboard Entry
52
34
Four
53
35
Five
54
36
Six
55
37
Seven
56
38
Eight
57
39
Nine
58
3A
59
3B
60
3C
<
<
<
61
3D
62
3E
>
>
>
63
3F
64
40
65
41
66
42
67
43
68
44
69
45
70
46
71
47
72
48
73
49
74
4A
75
4B
76
4C
77
4D
78
4E
79
4F
80
50
81
51
82
52
83
53
84
54
85
55
86
56
FR-921
Table 136
Numeric Values
Decimal
Hex
ASCII
Character
Meaning
Keyboard Entry
87
57
88
58
89
59
90
5A
91
5B
92
5C
93
5D
94
5E
95
5F
96
60
97
61
98
62
99
63
100
64
101
65
102
66
103
67
104
68
105
69
106
6A
107
6B
108
6C
109
6D
110
6E
111
6F
112
70
113
71
114
72
115
73
116
74
117
75
118
76
119
77
120
78
121
79
FR-922
78-11740-02
Table 136
Numeric Values
Decimal
Hex
ASCII
Character
Meaning
Keyboard Entry
122
7A
123
7B
124
7C
125
7D
126
7E
Tilde
127
7F
DEL
Delete
Del
FR-923
FR-924
78-11740-02
FR-925
service single-slot-reload-enable
To enable single line card reloading for all line cards in a Cisco 7500 series router, use the service
single-slot-reload-enable global configuration command. To disable single line card reloading for the
line cards, use the no form of this command.
service single-slot-reload-enable
no service single-slot-reload-enable
Syntax Description
Defaults
Command Modes
Command History
Release
Modification
12.0(13)S
12.1(5)T
Usage Guidelines
Before the introduction of this command, the only method of correcting a line card hardware failure or
a severe software error for one line card on a Cisco 7500 series router required the execution of a Cbus
Complex, a process that reloaded every line card on the network backplane. The time taken to complete
the Cbus Complex was often inconvenient, and no network traffic could be routed or switched during the
Cbus Complex process.
The service single-slot-reload-enable command allows users to correct a line card failure on a
Cisco 7500 series router by reloading the failed line card without reloading any other line cards on the
network backplane. During the single line card reload process, all physical lines and routing protocols
on the other line cards of the network backplane remain active. A single line card reload is also
substantially faster than the Cbus Complex process
Examples
In the following example, single line card reloading is enabled for all lines cards on a Cisco 7513 router:
c7513(config)# service single-slot-reload-enable
Related Commands
Command
Description
show diag
show running-config
FR-926
78-11740-02
Syntax Description
Defaults
Enabled
Command Modes
Global configuration
Command History
Release
Modification
11.1
Usage Guidelines
Use this command for a Cisco 7507 or Cisco 7513 router that is configured for dual RSP cards. On the
Cisco 7507 and Cisco 7513 router, you can install two RSP cards in a single router to improve system
availability. Dual RSP Cards is a High System Availability (HSA) feature.
In automatic synchronization mode, when you issue a copy EXEC command that specifies the masters
startup configuration (nvram:startup-config) as the target, the master also copies the same file to the
slaves startup configuration (slavenvram:startup-config). Use this command when implementing
HSA for simple hardware backup or for software error protection to ensure that the master and slave RSP
contain the same configuration files.
Examples
The following example turns on automatic configuration file synchronization. When the copy
system:running-config nvram:startup-config command is entered, the running configuration is saved
to the startup configurations of both the master RSP and the slave RSP.
Router(config)# slave auto-sync config
Router(config)# end
Router# copy system:running-config nvram:startup-config
Related Commands
Command
Description
show stacks
Displays the stack trace and version information of the master and slave RSP
cards.
FR-927
Command
Description
show version
Displays the software version running on the master and slave RSP cards.
Manually synchronizes configuration files on the master and slave RSP cards
of a Cisco 7507 or Cisco 7513 router.
FR-928
78-11740-02
slave default-slot
To specify the default slave Route Switch Processor (RSP) card on a Cisco 7507 or Cisco 7513 router,
use the slave default-slot global configuration command.
slave default-slot processor-slot-number
Syntax Description
processor-slot-number
Defaults
The default slave is the RSP card located in the higher number processor slot. On the Cisco 7507 router,
processor slot 3 contains the default slave RSP. On the Cisco 7513 router, processor slot 7 contains the
default slave RSP.
Command Modes
Global configuration
Command History
Release
Modification
11.1
Usage Guidelines
Number of a processor slot that contains the default slave RSP. On the
Cisco 7507 router, valid values are 2 or 3. On the Cisco 7513 router,
valid values are 6 or 7. The default is the higher number processor
slot.
Use this command for a Cisco 7507 or Cisco 7513 router that is configured for Dual RSP Cards. On the
Cisco 7507 and Cisco 7513 router, you can install two RSP cards in a single router to improve system
availability. Dual RSP Cards is a High System Availability (HSA) feature.
The router uses the default slave information when booting as follows:
Examples
If a system boot is due to powering up the router or using the reload EXEC command, then the
specified default slave will be the slave RSP.
If a system boot is due to a system crash or hardware failure, then the system ignores the default
slave designation, and makes the crashed or faulty RSP card the slave RSP.
In the following example, the user sets the default slave RSP to processor slot 2 on a Cisco 7507 router:
c7507(config)# slave default-slot 2
Related Commands
Command
Description
reload
show stacks
Displays the stack trace and version information of the master and slave RSP
cards.
show version
Displays the software version running on the master and slave RSP cards.
FR-929
slave image
To specify the image that the slave Route Switch Processor (RSP) runs on a Cisco 7507 or Cisco 7513
router, use the slave image global configuration command.
slave image {system | file-url}
Syntax Description
system
Loads the slave image that is bundled with the master system image.
This is the default.
file-url
Loads the slave image from the specified file in a Flash file system.
If you do not specify a filename, the first file on the specified Flash
file system is the default file.
Defaults
Command Modes
Global configuration
Command History
Release
Modification
11.1
Usage Guidelines
Use this command for a Cisco 7507 or Cisco 7513 router that is configured for Dual RSP Cards. On the
Cisco 7507 and Cisco 7513 router, you can install two RSP cards in a single router to improve system
availability. Dual RSP Cards is a High System Availability (HSA) feature.
Use the slave image command to override the slave image that is bundled with the master image.
When using HSA for simple hardware backup, ensure that the slave image is in the same location on the
master and the slave RSP card. Thus, if the slave RSP card becomes the master, it will be able to find the
slave image and download it to the new slave.
Examples
In the following example, the slave RSP is specified to run the rsp-dw-mz.ucode.111-3.2 image from slot
0:
c7507(config)# slave image slot0:rsp-dw-mz.ucode.111-3.2
Related Commands
Command
Description
show stacks
Displays the stack trace and version information of the master and slave RSP
cards.
show version
Displays the software version running on the master and slave RSP cards.
slave reload
Forces a reload of the image that the slave RSP card is running on a
Cisco 7507 or Cisco 7513 router.
FR-930
78-11740-02
slave reload
To force a reload of the image that the slave Route Switch Processor (RSP) card is running on a Cisco
7507 or Cisco 7513 router, use the slave reload global configuration command.
slave reload
Syntax Description
Defaults
Command Modes
Global configuration
Command History
Release
Modification
11.1
Usage Guidelines
Use this command for a Cisco 7507 or Cisco 7513 router that is configured for Dual RSP Cards. On the
Cisco 7507 and Cisco 7513 router, you can install two RSP cards in a single router to improve system
availability. Dual RSP Cards is a High System Availability (HSA) feature.
After using the slave image global configuration command to specify the image that the slave RSP runs
on a Cisco 7507 or Cisco 7513 router, use the slave reload command to reload the slave with the new
image. The slave reload command can also be used to force the slave to reboot its existing image.
Examples
In the following example, an inactive slave RSP card is reloaded. If the slave reloads, it will return to
an active slave state. If the master RSP fails, the slave RSP will become the master.
c7507(config)# slave reload
Related Commands
Command
Description
show stacks
Displays the stack trace and version information of the master and slave RSP
cards.
show version
Displays the software version running on the master and slave RSP cards.
slave image
Specifies the image that the slave RSP runs on a Cisco 7507 or Cisco 7513
router.
FR-931
Syntax Description
Defaults
Command Modes
Privileged EXEC
Command History
Release
Modification
11.1
Usage Guidelines
Use this command for a Cisco 7507 or Cisco 7513 router that is configured for Dual RSP Cards. On the
Cisco 7507 and Cisco 7513 router, you can install two RSP cards in a single router to improve system
availability. Dual RSP Cards is a High System Availability (HSA) feature.
This command allows you to synchronize the configuration files of the master and slave RSP cards on a
case-by-case basis when you do not have automatic synchronization turned on. This command copies
the masters configuration file to the slave RSP card.
Note
Examples
You must use this command when you insert a new slave RSP card into a Cisco 7507 or Cisco 7513
router for the first time to ensure that the new slave is configured consistently with the master.
In the following example, the configuration files on the master and slave RSP card are synchronized:
c7507(config)# slave sync config
Related Commands
Command
Description
show stacks
Displays the stack trace and version information of the master and slave RSP
cards.
show version
Displays the software version running on the master and slave RSP cards.
slave auto-sync config Turns on automatic synchronization of configuration files for a Cisco 7507
or Cisco 7513 router that is configured for HSA.
FR-932
78-11740-02
slave terminal
To enable access to the slave Route Switch Processor (RSP) console, use the slave terminal global
configuration command. To disable access to the slave RSP console, use the no form of this command.
slave terminal
no slave terminal
Syntax Description
Defaults
Enabled
Command Modes
Global configuration
Command History
Release
Modification
11.1
Usage Guidelines
The slave console does not have enable password protection. Thus, an individual connected to the slave
console port can enter privileged EXEC mode and view or erase the configuration of the router. Use the
no slave terminal command to disable slave console access and prevent security problems. When the
slave console is disabled, users cannot enter commands.
If slave console access is disabled, the following message appears periodically on the slave console:
%%Slave terminal access is disabled. Use "slave terminal" command in master RSP
configuration mode to enable it.
Examples
In the following example, the user disables console access to the slave RSP:
c7507(config)# no slave terminal
Related Commands
Command
Description
show stacks
Displays the stack trace and version information of the master and slave RSP
cards.
show version
Displays the software version running on the master and slave RSP cards.
slave auto-sync config Turns on automatic synchronization of configuration files for a Cisco 7507
or Cisco 7513 router that is configured for Dual RSP Cards.
FR-933
FR-934
78-11740-02
Index
Index
I N D E X
Symbols
! character
absolute command
absolute-timeout command
FR-532
FR-9
IP, time-based
FR-532
/etc/printcap file
FR-80
FR-478
FR-54, FR-545
activation-character command
xv
? command
FR-376, FR-440
FR-76
access lists
<cr>
FR-376
alias command
FR-313
FR-378
aliases
xiv
Numerics
FR-378
FR-457
ASCII
character set (table)
FR-919
FR-106
disconnect character
FR-106
dispatch character
escape character
FR-59
hold character
line, configuring on a
FR-69
padding
FR-94
hardware databits
line, configuring for a
FR-57
FR-88
FR-84, FR-106
FR-61
FR-62, FR-90
FR-67, FR-93
FR-71
FR-78, FR-102
start character
FR-109
stop character
FR-111
async-bootp command
attach command
FR-344
FR-482
autobaud command
FR-54, FR-545
FR-55
FR-58
FR-89
FR-60
line, configuring on a
FR-84
FR-106
FR-124
FR-126
FR-128
IN-937
Index
secondary
FR-130
banners
FR-318
FR-320
EXEC, displaying
FR-124
Break key
incoming message
FR-126
buckets-of-history-kept command
line
buffer-length command
disabling on a
enabling on a
line number
login
FR-323
command history
line, configuring for a
FR-162
FR-130
FR-40, FR-42
FR-383
size, setting
baud rates
buffers command
FR-105
FR-382
FR-318
FR-234
FR-312
FR-323
ASCII value
FR-320, FR-323
cd command
FR-325, FR-327
FR-697
xv
FR-919
boot fields
default values, changing
FR-385
FR-384
FR-316
FR-458
specifying
FR-383
FR-382, FR-384
statistics, displaying
FR-382, FR-384
FR-130
FR-17, FR-19
FR-126
boot command
FR-56
buffers
FR-128
MOTD
FR-806
FR-181
FR-312
FR-237
FR-755
booting
FR-759
neighbor
from Flash
FR-320
FR-312
information, displaying
FR-312
table, clearing
(example)
FR-314
FR-325, FR-327
FR-316
FR-240
FR-325, FR-327
bootstrap image
backing up on a server
FR-761
FR-754
routing device
FR-757
disabling
FR-749
enabling
FR-749
FR-753
FR-764
FR-746
FR-751
IN-938
78-11740-02
Index
Version-2, enabling
CLI prompts
FR-744
customizing
FR-744
FR-745
FR-747
FR-751
FR-389
FR-391
FR-395
command alias
FR-58
See aliases
FR-89
command history
character padding
line, configuring for a
buffer size
FR-78
FR-102
character set
FR-17, FR-19
7-bit
FR-40, FR-42
commands
displaying previous
8-bit
recalling
exiting
EXEC process
FR-33
FR-11, FR-12
global configuration
FR-33
command modes
character width
privileged EXEC
FR-59
FR-244
FR-8
FR-69
xiii to xiv
commands
FR-94
special characters
default, defining the
FR-60
xvii
FR-106
checksums
system images, verifying
no form, using
FR-188
conventions
xviii
help
FR-484
xv
FR-15
SNMP, setting
FR-682
FR-323
FR-243
config-register command
FR-134
ix
community string
FR-754
FR-896
xvii
displaying (example)
FR-708
FR-753
FR-232, FR-268
command syntax
FR-691
xiv, FR-3
history
FR-84
FR-387
FR-388
FR-749
FR-386
FR-746
FR-444
FR-8
FR-235
FR-325
configuration files
Cisco IOS Configuration Fundamentals Command Reference
78-11740-02
IN-939
Index
active, displaying
compressing
copy
FR-261
FR-249
copy command
FR-194
FR-183
default filename
FR-251
FR-251
FR-237
FR-258
FR-193
FR-191
network
default filename
FR-251
FR-251
FR-189
storing in
FR-211
FR-183
FR-183
FR-271
FR-237, FR-240
FR-189
FR-237
FR-10
xviii
FR-273
FR-274
FR-10
microcode image
FR-244
loading
FR-245
FR-182
FR-272
confreg command
FR-191
FR-189
configure command
FR-194
(example)
displaying file
FR-194
NVRAM
reloading
FR-278
FR-283
CSAA
FR-247
See SA Agent
FR-244
FR-327
connections
full duplex, refusing
FR-113
incoming, definition
FR-126
naming
FR-226
data bits
character, changing for a
FR-158
open, displaying
databits command
consoles
FR-89
FR-58
FR-57
data-character-bits command
FR-509
FR-100
FR-684
FR-329
FR-58
FR-95
FR-808
FR-100
FR-561
IN-940
78-11740-02
Index
FR-59
editing command
FR-198
FR-5
editors
FR-485
enhanced mode
FR-200
directory
print working
remove
FR-60
FR-213
FR-215
disable command
FR-5
FR-37
FR-5
FR-4
disconnect-character command
diskless boot, configuring
enable command
FR-61
FR-8
FR-61
end command
FR-351
dispatch-character command
FR-37
FR-8
FR-10
FR-62
dispatch characters
line, configuring for a
FR-62
FR-587
FR-64
dispatch-timeout command
environmental conditions
at last shutdown
FR-90
dispatch-machine command
FR-65
distributions-of-statistics-kept command
FR-809
FR-587
FR-320
rcp, enabling on
FR-352
BOOTLDR, specifying
rsh, enabling on
FR-352
CONFIG_FILE, specifying
erase command
xi
online, accessing
FR-275
xi
Documentation CD-ROM
error messages
viii
downward-compatible-config command
FR-396
redirecting
FR-521
escape-character command
Dual RSPs
reload slave RSP card
FR-67
FR-931
FR-930
FR-67
escape characters
FR-931
slave image
specifying
FR-202
v to vii
reloading
FR-235
ix
feedback, providing
ordering
FR-316
documentation
modules
FR-590
environment variables
BOOT, specifying
conventions
FR-116
FR-932
FR-93
FR-669
FR-489
FR-491
IN-941
Index
FR-493
format
FR-495
make directory
FR-497
exception region-size
FR-207
FR-210
remove directory
FR-499
FR-501
EXEC
rename file
FR-215
FR-214
verifying files
FR-224
FR-226
FR-378
process
FR-286
Flash memory
delaying startup of
FR-449
booting automatically
disabling on a line
FR-136
FR-188, FR-226
end transmission
FR-69
FR-111
exec-timeout command
exit command
FR-297
flow control
FR-136
execute-on command
FR-198
FR-206
verifying checksum
FR-139
FR-124, FR-128
exec-character-bits command
formatting
partitioning
FR-136
exec command
FR-124
FR-320
FR-139
FR-501, FR-503
start character
FR-109
stop character
FR-111
format command
FR-11, FR-12
FR-95
FR-206
FR-813
FR-209
full-help command
FR-13
Feature Navigator
See platforms, supported
file compression
FR-249
get command
FR-205
files
contents, displaying
download mode
FR-211
entering
FR-92
file systems
default, setting
erase
list
FR-244
FR-181
FR-202
FR-200
filter-for-history command
FR-811
xviii
FR-399
FR-112
FR-95
hardware platforms
See platforms, supported
xiv
FR-209
FR-13
FR-221
IN-942
78-11740-02
Index
help command
xiv, FR-15
history command
FR-17
FR-349
FR-19
hold character
FR-348
FR-169
FR-71
FR-170
FR-172
FR-96
FR-173
hold-character command
FR-71
ip rarp-server command
FR-350
hops-of-statistics-kept command
FR-814
FR-251
FR-237, FR-251
FR-397
FR-355
FR-194
default filename
FR-354, FR-360
FR-188
FR-352
hours-of-statistics-kept command
FR-361
FR-401
ip wccp command
FR-817
FR-360
FR-397
FR-402
FR-897
FR-885
FR-816
FR-126
FR-687
insecure command
FR-72
FR-897, FR-899
FR-905
xiv
FR-907
FR-106
FR-905
international command
FR-903
FR-897
FR-905
FR-908
FR-478
FR-304
IP
FR-376, FR-440
FR-676
FR-398
ip finger command
FR-901
viii
informs, enabling
supporting
FR-164
FR-897
FR-897
FR-358
FR-537, FR-538
FR-98
FR-399
FR-346
FR-347
Cisco IOS Configuration Fundamentals Command Reference
78-11740-02
IN-943
Index
lsr-path command
length command
FR-820
FR-73
FR-482
lines
messages, sending
FR-160
MAC addresses
line speeds
mapping to IP address
FR-105
FR-818
FR-21
FR-507
FR-145
FR-147
FR-148
FR-509
FR-151
FR-511
FR-153
FR-511
FR-513
FR-516
FR-517
logging on command
FR-521
FR-516
FR-519
FR-521
FR-506
FR-526
FR-729
messages
FR-525
FR-528
buffering
busy
FR-507
FR-159
debug, displaying
FR-76
FR-20
logout-warning command
FR-513
logout command
enabling
monitor
FR-519
FR-150
FR-509
FR-149
message logging
console
logging messages
logging monitor command
FR-146
FR-506
FR-142
FR-144
FR-295
FR-143
FR-75
FR-140
logging command
FR-294
resume
FR-724
FR-312
menu command
FR-74
lockable command
from ROM
FR-403
FR-312
FR-403
from Flash
lives-of-history-kept command
location command
FR-118
FR-733
load-interval command
FR-350
manual booting
FR-108
FR-741
linkUp/linkDown traps
lock command
FR-80
FR-76
FR-100
FR-124
FR-159
FR-160
IN-944
78-11740-02
Index
FR-521
FR-164
name-connection command
FR-158
FR-237, FR-240
FR-826
(example)
FR-768, FR-778
changing
microcode
loading Cisco IOS image
no menu command
FR-278
modes
monitors, message logging to
FR-420
FR-426
FR-430
FR-432
FR-434
FR-25
FR-436
FR-286
FR-27
running-config command
FR-438
FR-78, FR-102
more system
FR-424
FR-428
FR-364
FR-211
FR-419
FR-363
FR-23
FR-417
FR-364
FR-415
FR-320
FR-249
FR-262, FR-266
FR-413
FR-519
FR-409
FR-411
FR-407
FR-283
FR-210
FR-405
FR-282
FR-249
FR-668
FR-284
FR-537, FR-538
FR-155
no snmp-server command
FR-276
FR-251
FR-280
more command
FR-240
FR-276
FR-284
mkdir command
FR-251
FR-280
FR-194
default filename
viii
FR-188
FR-156
FR-130
O
operating system, reloading
FR-330
output notifications
line, setting for a
FR-77
IN-945
Index
FR-101
privilege levels
FR-821
FR-8
FR-8
probes
See also SA Agent operation
process-max-time command
prompt command
customizing
FR-90
system
packets
maximum size, establishing
SNMP, filtering
FR-444
xiv
pwd command
FR-728
FR-213
FR-728
padding
line, configuring for a
padding command
FR-78
FR-102
xiv
queues
FR-78
parity
line, setting for a
parity command
FR-103
FR-79
FR-248
FR-297
FR-297
paths-of-statistics-kept command
periodic command
FR-822
configuring
FR-532
FR-440
FR-355, FR-359
copying files
FR-354
FR-350
remote username
FR-534
FR-352
FR-323
refuse-message command
ping command
FR-159
release notes
FR-531, FR-534
FR-530, FR-534
FR-80
private command
FR-82
FR-330
remote shell
platforms, supported
xix
xix
FR-104
summary of
FR-729
FR-79
entering
FR-440, FR-444
prompts
FR-62
session, changing
FR-443
FR-323
FR-323
FR-214
request-data-size command
response-data-size command
FR-824
FR-825
xiv
IN-946
78-11740-02
Index
resume command
rsh server
FR-144
(example)
FR-104
RFC
access, granting
FR-344
FR-345
FR-344
FR-830
FR-397
FR-826
FR-829
FR-344
FR-771
FR-768, FR-778
FR-831
FR-834
FR-835
FR-836
FR-839
FR-215
FR-781
FR-770
FR-780
FR-778
interface, enabling
FR-770
FR-772
FR-773
FR-775
FR-776
FR-777
FR-853
history
collection
FR-806
FR-811
FR-818
FR-842
operations
FR-320
FR-846
FR-826
samples kept
FR-780
FR-366
configuring
lives kept
FR-778
filters
FR-768
FR-844
rmon command
FR-858
rsh command
FR-826
event table
FR-352
FR-344
FR-351
rmdir command
FR-360, FR-366
FR-399
FR-355
commands, executing
viii
enabling
FR-366
xiv
FR-164
setting frequency of
operations, configuring
FR-813
FR-875 to FR-892
probe
owner
FR-821
scheduling
FR-840
IN-947
Index
reaction trigger
configuring
displaying
resetting
FR-833, FR-834
FR-824
FR-866
statistics
displaying
FR-814
setup command
paths kept
FR-822
FR-455
FR-456
FR-46
configuration (examples)
FR-48 to FR-49
FR-872
configuration (example)
FR-873
verify data
FR-454
asynchronous interfaces
FR-817
FR-871
timeout
FR-538
FR-856, FR-869
hops kept
threshold
FR-537
FR-825
FR-48 to FR-49
FR-47 to FR-52
FR-893
samples-of-history-kept command
FR-842
FR-446
scheduler-interval command
FR-447
FR-926
FR-536
FR-835
tags
FR-453
FR-865
FR-452
FR-49
FR-52
screen
length
FR-73
sample configuration
FR-99
FR-47
FR-47 to FR-52
FR-71
(example)
width
FR-47
FR-122
FR-249
FR-251
FR-29
FR-332
FR-448
FR-449
FR-450
FR-368
FR-300
FR-333
FR-382
FR-541
FR-544
FR-299
FR-457
FR-160
location, setting
FR-47
security levels
FR-47
FR-462
FR-755
FR-162
IN-948
78-11740-02
Index
FR-759
FR-757
FR-761
FR-608
FR-612
FR-764
FR-289
FR-545
FR-216, FR-253
FR-547
FR-551
FR-553
FR-558
FR-559
FR-469
FR-254
FR-471
FR-580, FR-583
FR-217
FR-218
FR-790
FR-299
FR-306
FR-792
FR-795
FR-797
FR-799
FR-802
FR-844
FR-288
FR-846
FR-600
FR-788
FR-299
FR-785
FR-781
FR-219
FR-299
FR-783
FR-257
FR-335
FR-31
FR-629
FR-631
FR-626
FR-562
FR-621
FR-623
FR-586
FR-258
FR-619
FR-561
FR-466
FR-549
FR-614
FR-463
FR-669
FR-601
FR-853
FR-33
FR-465
FR-35
FR-909
FR-915
FR-606
FR-860
FR-865
FR-866
FR-909
FR-909
FR-867
FR-261
FR-856
FR-858
FR-847
FR-264
IN-949
Index
FR-671
SNMP server
FR-674
FR-675
FR-676
trap operation
FR-677
recipient
FR-266
FR-642
FR-682
FR-684
FR-685
FR-649
FR-686
FR-644
FR-650
FR-680
FR-681
FR-717
FR-640
FR-717
FR-679
FR-472
FR-668
FR-693
FR-695
FR-650
FR-651
FR-691
FR-687
FR-652
FR-697
FR-699
FR-336
FR-83
shutdown
FR-730
FR-930
FR-931
FR-932
FR-933
FR-682
FR-603
FR-684
FR-724
FR-668, FR-730
FR-717
FR-722
FR-724
FR-725
source, setting
FR-735
FR-736
FR-687
FR-729
FR-730
FR-731
FR-732
FR-733
FR-726
FR-728
trap message
traps, enabling
FR-714
FR-728
FR-705
FR-712
FR-687
FR-708
FR-927
FR-929
timeout
FR-703
FR-701
FR-735
FR-736
FR-737
IN-950
78-11740-02
Index
FR-739
FR-741
FR-474
FR-111
strings
system contact, setting
FR-684
FR-476
FR-325, FR-327
FR-717, FR-724
See buffers
FR-95
FR-109
FR-46
FR-84
FR-684
special-character-bits command
special characters
activation character
FR-430
FR-521
FR-54, FR-545
character width
default, defining the
checksum, verifying
FR-84
system images
FR-60
compressing
FR-106
FR-62
escape character
line, configuring for a
FR-323
FR-291
FR-291
default filename
FR-67
FR-226
FR-61
invalidated
FR-93
hold character
FR-304
FR-724
FR-71
FR-323
FR-322
FR-191
FR-668, FR-730
system software
FR-96
booting
FR-90
speeds
FR-320, FR-322
displaying version of
FR-336
FR-221
start characters
flow control, changing
FR-109
FR-109
tag command
FR-195
TCP
state-machine command
FR-85
statistics-distribution-interval command
stop bits
line, configuring for a
session, changing for a
stopbits command
FR-87
FR-110
FR-87
FR-134
FR-538
FR-64
FR-652
Telnet
stop characters
flow control, changing
FR-871
connections, clearing
FR-869
xiv
addresses, suppressing
FR-111
FR-451
FR-116
IN-951
Index
locking
FR-113
FR-113
FR-75
parity bit
FR-88
FR-103
FR-89
FR-90
port queue
FR-91
FR-93
FR-94
FR-95
receive speed
FR-105
FR-122
FR-96
start character
FR-109
FR-175
FR-98
type
FR-100
FR-101
FR-104
FR-104
FR-117
FR-11, FR-12
FR-103
terminal-queue command
FR-119
FR-102
FR-111
FR-99
FR-120
FR-82
FR-99
screen width
settings, saving
FR-40
FR-73
FR-38
FR-104
FR-37
FR-71
screen length
FR-92
FR-90
FR-105, FR-118
terminals
FR-108
FR-109
FR-110
FR-111
FR-54, FR-545
character padding
FR-78
FR-100
FR-116
escape character
line, defining for a
FR-93
FR-92
FR-108, FR-118
location, recording
lock access
FR-108
FR-74
FR-140
FR-115
FR-116
FR-117
FR-118
FR-119
FR-120
FR-656
FR-95
terminal-type command
FR-113
FR-114
FR-112
FR-106
FR-657
FR-658
FR-320
IN-952
78-11740-02
Index
FR-369
timeout interval
FR-888
FR-872
FR-873
FR-889
FR-891
FR-91
FR-139
FR-65
FR-736
time-range command
U
undelete command
FR-478
FR-224
compress command
FR-874
FR-874
FR-323
trace
FR-506
FR-323
common problems
terminating
FR-663
help command
FR-663
tracing IP routes
FR-659
FR-663
trace command
vacant-message command
common problems
extended test
FR-659
verify command
FR-659
FR-164
FR-226
verify-data command
FR-660
FR-893
privileged, overview
FR-739
FR-659
FR-659
user, overview
FR-663
traps
host, setting message queue length
message
FR-729
where command
FR-121
width command
FR-122
establishing timeout
source interface
FR-736
FR-735
recipient, specifying
traps, enabling
xiv
FR-664
terminating
FR-69
IP routes
FR-886
tos command
FR-884
FR-882
FR-369
threshold command
FR-687
FR-875
FR-877
FR-717
FR-15
FR-430
FR-309
FR-310
FR-879
FR-880
Cisco IOS Configuration Fundamentals Command Reference
78-11740-02
IN-953
Index
X
xmodem command
FR-291
IN-954
78-11740-02