-
Cisco IOS Configuration Fundamentals Command Reference, Release 12.2T
-
About the Cisco IOS Release 12.2 T Documentation Set
-
Basic Command-Line Interface Commands
-
The Setup Command
-
Terminal Operating Characteristics Commands
-
Connection, Menu, and System Banner Commands
-
Cisco IOS Web Browser User Interface Commands
-
Cisco IOS File System Commands
-
Configuration File Management Commands
-
System Image and Microcode Commands
-
Router Memory Commands
-
Booting Commands
-
Basic File Transfer Services Commands
-
Basic System Management Commands
-
Troubleshooting and Fault Management Commands
-
SNMP Commands
-
CDP Commands
-
RMON Commands
-
Cisco Service Assurance Agent Commands
-
WCCP Commands
-
CNS Commands
-
Distributed Director Commands
-
XSM Commands for VPN Device Manager (VDM)
-
Appendix: ASCII Character Set and Hex Values
-
Index: Cisco IOS Configuration Fundamentals Command Reference, Release 12.2 T
-
Table Of Contents
Troubleshooting and Fault Management Commands
exception crashinfo buffersize
show controllers (line card image)
Troubleshooting and Fault Management Commands
Note
This document applies to specifically to Cisco IOS Release 12.2T, up to and including 12.2(15)T.
For command reference documentation updates, please see the Cisco IOS Release 12.3 (mainline) Command Reference documents. Cisco IOS Release 12.3 contains all of the changes to commands implemented in the Cisco IOS Release 12.2T train.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 or the Cisco IOS Configuration Fundamentals Configuration Guide, Release 12.2.
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 command in privileged EXEC mode. 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
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
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
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 9Entering Console for 4 Port Packet Over SONET OC-3c/STM-1 in Slot: 9Type exit to end this sessionPress RETURN to get started!LC-Slot9# show ?cef Cisco Express Forwardingclock Display the system clockcontext Show context information about recent crash(s)history Display the session command historyhosts IP domain-name, lookup style, nameservers, and host tableipc Interprocess communications commandslocation Display the system locationsessions Information about Telnet connectionsterminal Display terminal configuration parametersusers Display information about terminal linesversion System hardware and software statusLC-Slot9# exitDisconnecting from slot 9.Connection Duration: 00:01:04Router#
Note
Related Commands
clear logging
To clear messages from the logging buffer, use the clear logging command in privileged EXEC mode.
clear logging
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Examples
In the following example, the logging buffer is cleared:
Router# clear loggingClear logging buffer [confirm]Router#Related Commands
logging buffered
Logs messages to an internal buffer.
show logging
Displays the state of logging (syslog).
clear logging xml
To clear the contents of the XML system message logging (syslog) buffer, use the clear logging xml command in EXEC mode.
clear logging xml
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
User EXEC
Privileged EXEC
Command History
Usage Guidelines
This command clears the contents of the XML-formatted logging buffer, but does not clear the contents of the standard logging buffer. The system will prompt you to confirm the action before clearing the buffer.
Examples
In the following example, the XML-specific buffer is cleared:
Router# clear logging xmlClear XML logging buffer [confirm]?yRelated Commands
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 command in privileged EXEC mode. 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
Defaults
No field diagnostics tests are performed on the line card.
Command Modes
Privileged EXEC
Command History
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 router's 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
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
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 3Running Diags will halt ALL activity on the requested slot. [confirm]Router#Launching a Field Diagnostic for slot 3Running DIAG config checkRUNNING 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 3Field Diag eeprom values: run 159 fial mode 0 (PASS) slot 3last test failed was 0, error code 0sending SHUTDOWN FDIAG_QUIT to fdiag in slot 3Board 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 verboseRunning Diags will halt ALL activity on the requested slot. [confirm]Router#Launching a Field Diagnostic for slot 3Running DIAG config checkRUNNING 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 CacheFDIAG_STAT_PASS test_num 1FDIAG_STAT_IN_PROGRESS: test #2 Sunblock OrderingFDIAG_STAT_PASS test_num 2FDIAG_STAT_IN_PROGRESS: test #3 Dram DatapinsFDIAG_STAT_PASS test_num 3...Field Diags: FDIAG_STAT_DONEField Diagnostic ****PASSED**** for slot 3Field Diag eeprom values: run 159 fial mode 0 (PASS) slot 3last test failed was 0, error code 0sending SHUTDOWN FDIAG_QUIT to fdiag in slot 3Board will reload...Router#Related Commands
exception core-file
To specify the name of the core dump file, use the exception core-file command in global configuration mode. 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
Defaults
The core file is named hostname-core, where hostname is the name of the router.
Command Modes
Global configuration
Command History
Usage Guidelines
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 router's 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.
Caution
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 redip ftp password blueexception protocol ftpexception dump 172.17.92.2exception core-file dumpfileRelated Commands
exception crashinfo file
To enable the creation of a diagnostic file at the time of unexpected system shutdowns, use the exception crashinfo file command in global configuration mode. To disable the creation of crashinfo files, use the no form of this command.
exception crashinfo file device:filename
no exception crashinfo file device:filename
Syntax Description
device:filename
Specifies the flash device and file name to be used for storing the diagnostic information. The colon is required.
Defaults
Enabled.
Command Modes
Global configuration
Command History
12.2(4)T, 12.2(11)
This command was introduced for the Cisco 3600 series only.
12.2(13)T
This command was implemented in 6400-NSP images.
Usage Guidelines
The "crashinfo" file saves information that helps Cisco technical support representatives to debug problems that caused the Cisco IOS image to fail (crash). The switch writes the crash information to the console at the time of the failure, and the file is created the next time you boot the IOS image after the failure (instead of while the system is failing). The file name will be filename_yyyymmdd-hhmmss, where y is year, m is month, d is date, h is hour, and s is seconds.
Examples
In the following example, a crashinfo file called "crashdata" will be created in the default flash memory device if a system crash occurs:
Router(config)# exception crashinfo file flash:crashinfoRelated Commands
exception crashinfo buffersize
To change the size of the buffer used for crashinfo files, use the exception crashinfo buffersize command in global configuration mode. To revert to the default buffersize, use the no form of this command.
exception crashinfo buffersize kilobytes
no exception crashinfo buffersize kilobytes
Syntax Description
kilobytes
Sets the size of the buffersize to the specified value within the range of 32 to 100 kilobytes. The default is 32Kb.
Defaults
Crashinfo buffer is 32Kb.
Command Modes
Global configuration
Command History
12.2(4)T, 12.2(11)
This command was introduced for the Cisco 3600 series only.
12.2(13)T
This command was implemented in 6400-NSP images.
Usage Guidelines
The crashinfo file saves information that helps Cisco technical support representatives to debug problems that caused the Cisco IOS image to fail (crash). The switch writes the crash information to the console at the time of the failure, and the file is created the next time you boot the IOS image after the failure (instead of while the system is failing).
Examples
In the following example, a the crashinfo buffer is set to 100Kb:
Router(config)# exception crashinfo buffersize 100Related Commands
exception crashinfo file
Enables the creation of a diagnostic file at the time of unexpected system shutdowns.
exception dump
To configure the router to dump a core file to a particular server when the router crashes, use the exception dump command in global configuration mode. To disable core dumps, use the no form of this command.
exception dump ip-address
no exception dump
Syntax Description
Defaults
Disabled
Command Modes
Global configuration
Command History
Usage Guidelines
Caution
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 router's 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 redip ftp password blueexception protocol ftpexception dump 172.17.92.2Related Commands
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 command in global configuration mode. 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
Defaults
No crash information is stored for the line card.
If enabled with no options, the default is to store 256 MB of main memory.
Command Modes
Global configuration
Command History
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
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.
exception linecard slot 8endexception memory
To cause the router to create a core dump and reboot when certain memory size parameters are violated, use the exception memory command in global configuration mode. 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
The minimum contiguous block of memory in the free pool, in bytes.
minimum size
The minimum size of the free memory pool, in bytes.
Defaults
Disabled
Command Modes
Global configuration
Command History
Usage Guidelines
Caution
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.2exception core-file memory.overrunexception memory minimum 250000Related Commands
exception protocol
To configure the protocol used for core dumps, use the exception protocol command in global configuration mode. 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
Uses File Transfer Protocol (FTP) for core dumps.
rcp
Uses remote copy protocol (rcp) for core dumps.
tftp
Uses TFTP for core dumps. This is the default.
Defaults
TFTP
Command Modes
Global configuration
Command History
Usage Guidelines
Caution
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 router's 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 redip ftp password blueexception protocol ftpexception dump 172.17.92.2Related Commands
exception region-size
To specify the size of the region for the exception-time memory pool, use the exception region-size command in global configuration mode. To use the default region size, use the no form of this command.
exception region-size size
no exception region-size
Syntax Description
Defaults
16,384 bytes
Command Modes
Global configuration
Command History
Usage Guidelines
Caution
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
In the following example, the region size is set at 1024:
Router# exception region-size 1024Related Commands
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 in global configuration mode. 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
(Optional) A number from 1 to 4294967295 that indicates the maximum number of spurious interrupts to include in the core dump before reloading.
Defaults
Disabled
Command Modes
Global configuration
Command History
Usage Guidelines
Caution
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 router's 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 2Related Commands
execute-on
To execute commands on a line card, use the execute-on command in privileged EXEC mode.
execute-on {slot slot-number | all | master} command
Syntax Description
Command Modes
Privileged EXEC
Command History
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
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.
Timesaver
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
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 pingThe 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 reloadYou can use the execute-on command to enable remote execution of the commands included in the following partial list:
•
•
•
•
•
•
•
•
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 POS0Hardware is BFLC POSlcpos_instance struct 6033A6E0RX POS ASIC addr space 12000000TX POS ASIC addr space 12000100SUNI framer addr space 12000400SUNI rsop intr status 00CRC16 enabled, HDLC enc, int clockno loopInterface POS1Hardware is BFLC POSlcpos_instance struct 6033CEC0RX POS ASIC addr space 12000000TX POS ASIC addr space 12000100SUNI framer addr space 12000600SUNI rsop intr status 00CRC32 enabled, HDLC enc, int clockno loopInterface POS2Hardware is BFLC POSlcpos_instance struct 6033F6A0RX POS ASIC addr space 12000000TX POS ASIC addr space 12000100SUNI framer addr space 12000800SUNI rsop intr status 00CRC32 enabled, HDLC enc, int clockno loopInterface POS3Hardware is BFLC POSlcpos_instance struct 60341E80RX POS ASIC addr space 12000000TX POS ASIC addr space 12000100SUNI framer addr space 12000A00SUNI rsop intr status 00CRC32 enabled, HDLC enc, ext clockno loopRouter#Related Commands
attach
Connects you to a specific line card for the purpose of executing commands using the Cisco IOS software image on that line card.
logging buffered
To enable system message logging to a local buffer and limit messages logged to the buffer based on severity, use the logging buffered command in global configuration mode. 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 acceptable level name or level number keywords. The default logging level varies by platform, but is generally 7, meaning that messages at all levels (0-7) are logged to the buffer.
Defaults
Varies by platform. For most platforms, logging to the buffer is disabled by default. When enabled, the default logging level is 7 (debugging).
Command Modes
Global configuration
Command History
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 command. The first message displayed is the oldest message in the buffer.
The show logging command displays the addresses and levels associated with the current logging setup, and any other logging statistics.
Examples
In the following example, the user enables standard system logging to the local syslog buffer:
Router(config)# logging bufferedRelated Commands
logging buffered xml
To enable system message logging (syslog) and send XML-formatted logging messages to the XML-specific system buffer, use the logging buffered xml command in global configuration mode. To disable the XML syslog buffer and return the size of the buffer to the default, use the no form of this command.
logging buffered xml [xml-buffer-size]
no logging buffered xml [xml-buffer-size]
Syntax Description
Defaults
XML formatting of system logging messages is disabled.
The default XML syslog buffer size is the same size as the standard syslog buffer.
Command Modes
Global configuration
Command History
Usage Guidelines
Standard logging is enabled by default, but XML-formatted system message logging is disabled by default. If standard logging has been disabled on your system (using the no logging on command), standard logging must be reenabled using the logging on command before using the logging buffered xml command.
The logging buffered xml command copies logging messages to an internal XML buffer. The XML syslog buffer is separate from the standard syslog buffer (created using the logging buffered command).
The buffer is circular, so newer messages overwrite older messages as the buffer is filled.
The severity level for logged messages is determined by the setting of the logging buffered command. If the logging buffered command has not been used, the default severity level for that command is used. The default severity level varies by platform, but is generally level 7 ("debugging") , meaning that messages at all severity levels (0 through 7) are logged. For more information on severity levels, see the documentation of the logging buffered command.
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 value is the maximum available and should not be approached.
To return the size of the XML logging buffer to the default, enter the logging buffered xml command again without a buffer size value.
To display the messages that are logged in the buffer, use the show logging xml command in EXEC mode. The first message displayed is the oldest message in the buffer.
Examples
In the following example, the user enables logging to the XML syslog buffer and sets the XML syslog buffer size to 14 kilobytes:
Router(config)# logging buffered xml 14336Related Commands
logging console
To send system logging (syslog) messages to all available TTY lines and limit messages based on severity, use the logging console command in global configuration mode. To disable logging to the console terminal, use the no form of this command.
logging console [severity-level]
no logging console [severity-level]
Syntax Description
severity-level
Limits the logging of messages displayed on the console terminal to the specified level and (numerically) lower levels. You can enter the level number or level name. See Table 56 for a list of the level arguments.
Defaults
In general, the default is to log messages from level 0 (emergencies) to level 7 (debugging). However, the default level varies by platform.
Command Modes
Global configuration
Command History
Usage Guidelines
The console keyword indicates all available TTY lines. This can mean a console terminal attached to the router's TTY line, a dial-up modem connection, or a printer.
Specifying a level causes messages at that level and numerically lower levels to be sent to the console (TTY lines).
The show logging EXEC command displays the addresses and levels associated with the current logging setup, and any other logging statistics. See Table 56.
Note
Examples
In the following example, the user changes the level of messages sent to the console terminal (TTY lines) to alerts, which means messages at levels 0 and 1 are sent:
Router(config)# logging console alertsRelated Commands
access-list (extended)
Defines an extended XNS access list.
logging facility
Configures the syslog facility in which error messages are sent.
logging console xml
To enable XML-formatted system message logging to the console connections, use the logging console xml command in global configuration mode. To disable all logging to the console connections, use the no form of this command.
logging console xml [severity-level]
no logging console xml
Syntax Description
Defaults
Logging to the console is enabled.
XML-formatted logging to the console is disabled.
The default severity level varies by platform, but is generally level 7 (messages at levels 0 through 7 are logged).
Command Modes
Global configuration
Command History
Usage Guidelines
To return system logging messages to standard text (without XML formatting), issue the standard logging console command (without the xml keyword extension).
Examples
In the following example, the user enables XML-formatted system message logging to the console for messages at levels 0 through 4:
Router(config)# logging console xml 4Related Commands
show logging xml
Displays the state of XML-formatted system message logging, followed by the contents of the XML syslog buffer.
logging count
To enable the error log count capability, use the logging count command in global configuration mode. To disable the error log count capability, use the no form of this command.
logging count
no logging count
Syntax Description
This command has no arguments or keywords.
Defaults
This command is disabled.
Command Modes
Global configuration
Command History
Usage Guidelines
The logging count command counts every syslog message and time-stamps the occurrence of each message.
Examples
In the following example, syslog messages are logged to the system buffer and the logging count capability is enabled:
Router(config)# logging buffered notificationsRouter(config)# logging countRouter(config)# endRouter# show logging countFacility Message Name Sev Occur Last Time=============================================================================SYS BOOTTIME 6 1 00:00:12SYS RESTART 5 1 00:00:11SYS CONFIG_I 5 3 1d00h------------- ------------------------------- -----------------------------SYS TOTAL 5LINEPROTO UPDOWN 5 13 00:00:19------------- ------------------------------- -----------------------------LINEPROTO TOTAL 13LINK UPDOWN 3 1 00:00:18LINK CHANGED 5 12 00:00:09------------- ------------------------------- -----------------------------LINK TOTAL 13SNMP COLDSTART 5 1 00:00:11------------- ------------------------------- -----------------------------SNMP TOTALRelated Commands
logging facility
To configure the syslog facility in which error messages are sent, use the logging facility command in global configuration mode. 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
Syslog facility. See the Usage Guidelines section of this command reference entry for descriptions of acceptable keywords.
Defaults
local7
Command Modes
Global configuration
Command History
Usage Guidelines
Table 57 describes the acceptable keywords for the facility-type argument.
Examples
In the following example, the user configures the syslog facility to the kernel facility type:
logging facility kernRelated Commands
logging history
To limit syslog messages sent to the router's history table and to an SNMP network management station based on severity, use the logging history command in global configuration mode. 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
Defaults
Logging of error messages of severity levels 0 through 4 (emergency, alert, critical, error, and warning levels); in other words, "saving level warnings or higher"
Command Modes
Global configuration
Command History
Usage Guidelines
The sending of syslog messages to an SNMP network management station (NMS) occurs when you enable syslog traps with the snmp-server enable traps syslog global configuration mode command.
Because SNMP traps are potentially unreliable, 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 global configuration mode 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 router's 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) levels to be saved to the logging history table.
Table 58 provides a description of logging severity levels, listed from highest severity to lowest severity, and the arguments used in the logging history command syntax. Note that you can use the level name or the level number as the level argument in this command.
Examples
In the following example, the system is initially configured to the default of saving severity level 4 or higher. The logging history 1 command is used to configure the system to save only level 1 (alert) and level 0 (emergency) messages to the logging history table, and, by extension, to send only these levels in the SNMP notifications. The configuration is then confirmed using the show logging history command.
Router#show logging historySyslog 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 higher23 messages ignored, 0 dropped, 0 recursion drops1 table entries flushedSNMP notifications not enabledentry number 2 : LINK-3-UPDOWNInterface FastEthernet0, changed state to uptimestamp: 2766Router#configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)#logging history 1Router(config)#snmp-server enable traps syslogRouter(config)#endRouter#4w0d: %SYS-5-CONFIG_I: Configured from console by consoleRouter#show logging historySyslog History Table:1 maximum table entries,! The following line indicates that `logging history level 1' (alerts) is configured.saving level alerts or higher18 messages ignored, 0 dropped, 0 recursion drops1 table entries flushedSNMP notifications enabled, 0 notifications sententry number 2 : LINK-3-UPDOWNInterface FastEthernet0, changed state to uptimestamp: 2766Router#Related Commands
logging history size
To change the number of syslog messages stored in the router's history table, use the logging history size command in global configuration mode. To return the number of messages to the default value, use the no form of this command.
logging history size number
no logging history size
Syntax Description
number
Number from 1 to 500 that indicates the maximum number of messages stored in the history table.
Defaults
One message
Command Modes
Global configuration
Command History
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 20Related Commands
logging host
To log system messages and debug output to a remote host, use the logging host command in global configuration mode. To remove a specified logging host from the configuration, use the no form of this command.
logging host {ip-address | host-name} [xml]
no logging host {ip-address | host-name} [xml]
Syntax Description
Defaults
System logging messages are not sent to any remote host.
If this command is entered without the xml keyword, messages are sent in the standard format.
Command Modes
Global configuration
Command History
10.0
The logging command was introduced.
12.0(14)S, 12.0(14)ST, 12.2(15)T
The logging host command replaced the logging command.
12.2(15)T
The xml keyword was added.
Usage Guidelines
System logging messages are also called system error messages.
Standard system message logging (syslog) is enabled by default. If logging has been disabled on your system (using the no logging on command), logging must be reenabled using the logging on command before using the logging host command.
The logging host command identifies a remote host (syslog server) to receive logging messages. By issuing this command more than once, you build a list of syslog servers that receive logging messages.
To specify the severity level for logging to all hosts, use the logging trap command.
You can specify that standard syslog messages are to be sent to one or more hosts while XML-formatted messages are to be sent to another host (or hosts) by repeating this command with the appropriate syntax.
If you enter the logging host {ip-address | host-name} command after entering the logging host {ip-address | host-name} xml command and you use the same IP address or host name in both commands, XML formatting is disabled for that host, and messages will be sent in the standard format. In other words, a standard logging host command will replace an XML logging host command, and vice versa, if the same host is specified.
Note
Examples
In the following example, messages at severity levels 0 (emergencies) through 5 (notifications) are logged to a host at 209.165.202.169:
Router(config)# logging host 209.165.202.169Router(config)# logging trap 5Related Commands
logging linecard
To log messages to an internal buffer on a line card, use the logging linecard command in global configuration mode. 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
Defaults
The Cisco IOS software logs messages to the internal buffer on the GRP card.
Command Modes
Global configuration
Command History
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.
Table 59 Message Levels
emergencies
0
alerts
1
critical
2
errors
3
warnings
4
notifications
5
informational
6
debugging
7
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:
logging linecard warningsendRelated Commands
Clears messages from the logging buffer.
Displays the state of logging (syslog).
logging monitor
To enable system message logging to the terminal lines (monitor connections) and limit these messages based on severity, use the logging monitor command in global configuration mode. 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
Defaults
debugging (severity-level 7)
Command Modes
Global configuration
Command History
Usage Guidelines
Specifying a severity-level causes messages only at that level and numerically lower levels to be displayed to the monitor (terminal lines).
Examples
In the following example, the user specifies that only messages of the levels errors, critical, alerts, and emergencies be logged to monitor connections:
Router(config)# logging monitor 3Related Commands
logging monitor xml
To enable XML-formatted system message logging to monitor connections, use the logging console xml command in global configuration mode. To disable all logging to the monitor connections, use the no form of this command.
logging monitor xml [severity-level]
no logging monitor xml
Syntax Description
Defaults
Logging to monitor connections is enabled.
XML-formatted logging to monitor connections is disabled.
The default severity level varies by platform, but is generally level 7 (messages at levels 0 through 7 are logged).
Command Modes
Global configuration
Command History
Usage Guidelines
The monitor keyword specifies the TTY (TeleTYpe) line connections at all line ports. TTY lines (also called ports) communicate with peripheral devices such as terminals, modems, and serial printers. An example of a TTY connection is a PC with a terminal emulation program connected to the device using a dial-up modem, or a Telnet connection.
To return system logging messages to standard text (without XML formatting), issue the standard logging monitor command (without the xml keyword extension).
Examples
In the following example, the user enables XML-formatted system message logging to the console for messages at levels 0 through 4 and XML-formatted system message logging to TTY line connections at the default severity level:
Router(config)# logging console xml 4Router(config)# logging monitor xmlRelated Commands
logging on
To enable logging of system messages, use the logging on command in global configuration mode. This command sends debug or error 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
This command has no arguments or keywords.
Defaults
The Cisco IOS software sends messages to the asynchronous logging process.
Command Modes
Global configuration
Command History
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. System logging messages are also known as system error messages. 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
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 onRouter(config)# endRouter#%SYS-5-CONFIG_I: Configured from console by consoleRouter# ping dirtType escape sequence 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 = 4/5/8 msRouter#IP: s=172.21.96.41 (local), d=172.16.1.129 (Ethernet1/0), len 100, sendingIP: s=171.69.1.129 (Ethernet1/0), d=172.21.96.41, len 114, rcvd 1IP: s=172.21.96.41 (local), d=172.16.1.129 (Ethernet1/0), len 100, sendingIP: s=171.69.1.129 (Ethernet1/0), d=172.21.96.41, len 114, rcvd 1IP: s=172.21.96.41 (local), d=172.16.1.129 (Ethernet1/0), len 100, sendingIP: s=171.69.1.129 (Ethernet1/0), d=172.21.96.41, len 114, rcvd 1IP: s=172.21.96.41 (local), d=172.16.1.129 (Ethernet1/0), len 100, sendingIP: s=171.69.1.129 (Ethernet1/0), d=172.21.96.41, len 114, rcvd 1IP: s=172.21.96.41 (local), d=172.16.1.129 (Ethernet1/0), len 100, sendingIP: s=171.69.1.129 (Ethernet1/0), d=172.21.96.41, len 114, rcvd 1In 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 onRouter(config)# end%SYS-5-CONFIG_I: Configured from console by consoleRouter#Router# ping dirtIP: s=172.21.96.41 (local), d=172.16.1.129 (Ethernet1/0), len 100, sendingTypIP: s=171.69.1.129 (Ethernet1/0), d=172.21.96.41, len 114, rcvd 1eIP: s=172.21.96.41 (local), d=172.16.1.129 (Ethernet1/0), len 100, sending escIP: s=171.69.1.129 (Ethernet1/0), d=172.21.96.41, len 114, rcvd 1IP: s=172.21.96.41 (local), d=172.16.1.129 (Ethernet1/0), len 100, sendingapeIP: s=171.69.1.129 (Ethernet1/0), d=172.21.96.41, len 114, rcvd 1IP: s=172.21.96.41 (local), d=172.16.1.129 (Ethernet1/0), len 100, sendingseIP: s=171.69.1.129 (Ethernet1/0), d=172.21.96.41, len 114, rcvd 1IP: s=172.21.96.41 (local), d=172.16.1.129 (Ethernet1/0), len 100, sendingquenIP: 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 msRouter#Related Commands
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 | console} [except severity]
no logging rate-limit
Syntax Description
Defaults
No default behavior or values.
Command Modes
Global configuration
Command History
Usage Guidelines
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.
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 (higher than 2) to only 10 per second.
Table 60 compares the error message logging numeric severity level with its equivalent word description.
For additional details about error message logging, see the "Troubleshooting the Router" chapter in the Cisco IOS Configuration Fundamentals Configuration Guide, Release 12.2 .
Examples
In the following example, the logging rate-limit configuration mode command limits message output to 200 per second:
Router(config)# logging rate-limit 200Related Commands
Synchronizes unsolicited messages and debug output with solicited Cisco IOS software output and prompts for a specific console port line, auxiliary port line, or vty.
logging source-interface
To specify the source IP address of syslog packets, use the logging source-interface command in global configuration mode. 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
Defaults
No interface is specified.
Command Modes
Global configuration
Command History
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 0The 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/1Related Commands
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 command in line configuration mode. 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
This feature is turned off by default.
If you do not specify a severity level, the default value of 2 is assumed.
If you do not specify the maximum number of buffers to be queued, the default value of 20 is assumed.
Command Modes
Line configuration
Command History
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.
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
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 4logging synchronous level 6line 2logging synchronous level 7 limit 70000Related Commands
logging trap
To limit messages logged to the syslog servers based on severity, use the logging trap command in global configuration mode. The command limits the logging of error 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
Defaults
informational (level 6)
Command Modes
Global configuration
Command History
Usage Guidelines
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.
Examples
In the following example, the messages to a host named john is logged:
logging john logging trap notificationsRelated Commands
ping
To diagnose basic network connectivity on AppleTalk, ATM, Connectionless Network Service (CLNS), DECnet, IP, Novell IPX, or source-route bridging (SRB) networks, use the ping command in user EXEC mode or privileged EXEC mode.
ping [[protocol | tag | vrf] {host-name | system-address}]
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
The ping command sends an echo request packet to an address, and 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. For example, the ping clns command sends International Organization for Standardization (ISO) CLNS echo packets to test the reachability of a remote router over a connectionless Open System Interconnection (OSI) network.
If you enter the ping command without any other syntax (ping<cr>), the CLI will display a system dialog that prompts you for the additional syntax appropriate to the protocol you specify (See the "Examples" section).
To abnormally terminate a ping session, type the escape sequence—by default, Ctrl-^ 6X. You type the default by simultaneously pressing and releasing the Ctrl, Shift, and 6 keys and then pressing the X key.
Table 62 describes the test characters sent by the ping facility.
Note
The availability of protocol keywords depends on what protocols are enabled on your system.
Issuing the ping command in User EXEC mode will generally offer fewer syntax options than issuing the ping command in Privileged EXEC mode.
Examples
After you enter the ping command in privileged EXEC mode, the system prompts for one of the following keywords: atm, clns, decnet, ip, ipv6, ipx, or srb. 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.
The following example is sample dialog from the ping command using default values. The specific dialog varies somewhat from protocol to protocol.
Router# pingProtocol [ip]:Target IP address: 192.168.7.27Repeat 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 msTable 63 describes the relevant fields shown in the display.
Table 63 ping Field Descriptions for IP
Protocol [ip]:
Prompts for a supported protocol. Enter atm, clns, decnet, ip, ipv6, ipx, or srb. Default: 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. Default: none.
Repeat count [5]:
Number of ping packets that will be sent to the destination address. Default: 5.
Datagram size [100]:
Size of the ping packet (in bytes). Default: 100 bytes.
Timeout in seconds [2]:
Timeout interval. Default: 2 (seconds).
Extended commands [n]:
Specifies whether a series of additional commands appears.
Sweep range of sizes [n]:
Allows you to vary the sizes of the echo packets being sent. This capability is useful for determining the minimum sizes of the MTUs1 configured on the nodes along the path to the destination address. Packet fragmentation contributing to performance problems can then be reduced.
!!!!!
Each exclamation point (!) indicates receipt of a reply. A period (.) indicates that the network server timed out while waiting for a reply. Other characters may appear in the ping output display, depending on the protocol type.
Success rate is 100 percent
Percentage of packets successfully echoed back to the router. Anything less than 80 percent is usually considered problematic.
round-trip min/avg/max = 1/2/4 ms
Round-trip travel time intervals for the protocol echo packets, including minimum/average/maximum (in milliseconds).
1 MTU = maximum transmission unit
The following example verifies connectivity to the neighboring ATM device for the ATM PVC with the virtual path identifier (VPI)/virtual channel identifier (VCI) value 0/16:
Router# pingProtocol [ip]:atmATM Interface:atm1/0VPI value [0]:VCI value [1]:16Loopback - End(0), Segment(1) [0]:1Repeat Count [5]:Timeout [2]:Type escape sequence to abort.Sending 5, 53-byte segment OAM echoes, timeout is 2 seconds:!!!!!Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 msTable 64 describes the default ping fields shown in the display.
Related Commands
ping ip
To test network connectivity on IP networks, use the ping ip command in privileged EXEC mode.
ping ip {host-name | system-address} [data [hex-data-pattern] | df-bit | repeat [repeat-count] | size [datagram-size] [source {source-address | source-interface} ] [timeout seconds] [validate]
Syntax Description
Command Modes
Privileged EXEC
Command History
10.0
This command was introduced.
12.0
The data, df-bit, repeat, size, source, timeout, and validate keywords were added.
Usage Guidelines
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 sequence—by 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.
Note
Examples
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.
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# pingProtocol [ip]:Target IP address: 192.168.7.27Repeat 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 msTable 66 describes the default ping fields shown in the display.
Related Commands
service sequence-numbers
To enable visible sequence numbering of system logging messages, use the service sequence-numbers command in global configuration mode. To disable visible sequence numbering of logging messages, use the no form of this command.
service sequence-numbers
no service sequence-numbers
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled.
Command Modes
Global configuration
Command History
Usage Guidelines
Each system status messages logged in the system logging process have a sequence reference number applied. This command makes that number visible by displaying it with the message. The sequence number is displayed as the first part of the system status message. See the description of the logging commands for information on displaying logging messages.
Examples
In the following example logging message sequence numbers are enabled:
.Mar 22 15:28:02 PST: %SYS-5-CONFIG_I: Configured from console by consoleRouter# config terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# service sequence-numbersRouter(config)# endRouter#000066: .Mar 22 15:35:57 PST: %SYS-5-CONFIG_I: Configured from console by consoleRelated Commands
logging on
Enables system logging globally.
service timestamps
Enables time-stamping of system logging messages or debugging messages.
service slave-log
To allow slave Versatile Interface Processor (VIP) cards to log important error messages to the console, use the service slave-log command in global configuration mode. To disable slave logging, use the no form of this command.
service slave-log
no service slave-log
Syntax Description
This command has no arguments or keywords.
Defaults
This command is enabled by default.
Command Modes
Global configuration
Command History
Usage Guidelines
This command allows slave slots to log error messages of level 2 or higher (critical, alerts, and emergencies).
Examples
In the following example, important messages from the slave cards to the console are logged:
service slave-logIn 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 initializationThe first line indicates which slot sent the message. The second line contains the error message.
service tcp-keepalives-in
To generate keepalive packets on idle incoming network connections (initiated by the remote host), use the service tcp-keepalives-in command in global configuration mode. To disable the keepalives, use the no form of this command.
service tcp-keepalives-in
no service tcp-keepalives-in
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Global configuration
Command History
Examples
In the following example, keepalives on incoming TCP connections are generated:
service tcp-keepalives-inRelated Commands
service tcp-keepalives-out
Generates keepalive packets on idle outgoing network connections (initiated by a user).
service tcp-keepalives-out
To generate keepalive packets on idle outgoing network connections (initiated by a user), use the service tcp-keepalives-out command in global configuration mode. To disable the keepalives, use the no form of this command.
service tcp-keepalives-out
no service tcp-keepalives-out
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Global configuration
Command History
Examples
In the following example, keepalives on outgoing TCP connections are generated:
service tcp-keepalives-outRelated Commands
service tcp-keepalives-in
Generates keepalive packets on idle incoming network connections (initiated by the remote host).
service timestamps
To configure the system to time-stamp debugging or system logging messages, use one of the service timestamps commands in global configuration mode. To disable this service, use the no form of this command.
service timestamps {debug | log} uptime
service timestamps {debug | log} datetime [msec] [localtime] [show-timezone] [year]
no service timestamps [debug | log]
Syntax Description
Defaults
No time-stamping.
If the service timestamps command is specified with no arguments or keywords, the default is service timestamps debug uptime.
The default for the service timestamps type datetime command is to format the time in Coordinated Universal Time (UTC), with no milliseconds and no time zone name.
The no service timestamps command by itself disables time stamps for both debug and log messages.
To set the local timezone, use the clock timezone zone hours-offset command in global configuration mode.
Command Modes
Global configuration
Command History
Usage Guidelines
Time stamps can be added to either debugging or logging messages independently. The uptime form of the command adds time stamps in the format HHHH:MM:SS, indicating the time since the system was rebooted. The datetime form of the command adds time stamps in the format MMM DD HH:MM:SS, indicating the date and time according to the system clock.
The timestamp will be preceded by an asterisk or period if the time is potentially inaccurate. Table 67 describes the symbols that proceed the timestamp.
Examples
In the following example, the user enables time stamps on debugging messages, showing the time since reboot:
service timestamps debug uptimeIn 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:
Router(config)#! The following line shows timestamp with uptime.1w0d: %SYS-5-CONFIG_I: Configured from console by consoleRouter(config)# service timestamps log datetime localtime show-timezoneRouter(config)# endRouter#! The following line shows timestamp with datetime..Mar 22 23:13:25 UTC: %SYS-5-CONFIG_I: Configured from console by consoleThe following example shows the change from UTC to local time:
Router#.Mar 22 23:23:10 UTC: %SYS-5-CONFIG_I: Configured from console by consoleRouter# config terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# clock timezone PST -8Router(config)# endRouter#.Mar 22 15:28:02 PST: %SYS-5-CONFIG_I: Configured from console by consoleRelated Commands
clock set
Manually sets the system clock.
ntp
Controls access to the system's NTP services.
service sequence-numbers
Stamps system logging messages with a sequence number.
show c2600 (2600)
To display information for troubleshooting the Cisco 2600 series router, use the show c2600 command in EXEC mode.
show c2600
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Usage Guidelines
The show c2600 command provides complex troubleshooting information that pertains to the platform's shared references rather than to a specific interface.
Examples
In the following example, sample output is shown for the show c2600 EXEC command. See Table 68 for a description of the output display fields.
router# show c2600C2600 Platform Information:Interrupts:Assigned Handlers...Vect Handler # of Ints Name00 801F224C 00000000 Xilinx bridge error interrupt01 801DE768 0D3EE155 MPC860 TIMER INTERRUPT02 801E94E0 0000119E 16552 Con/Aux Interrupt04 801F0D94 00000000 PA Network Management Int Handler05 801E6C34 00000000 Timebase Reference Interrupt06 801F0DE4 00002C1A PA Network IO Int Handler07 801F0EA0 0000015D MPC860 CPM INTERRUPT14 801F224C 00000000 Xilinx bridge error interruptIOS 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 ]SIU_IRQ_MASK = FFFFFFFF SIEN = EF02xxxx Current Level = 00Spurious IRQs = 00000000 SIPEND = 0000xxxxInterrupt Throttling:Throttle Count = 00000000 Timer Count = 00000000Netint usec = 00000000 Netint Mask usec = 000003E8Active = 0 Configured = 0Longest IRQ = 00000000IDMA Status:Requests = 00000349 Drops = 00000000Complete = 00000349 Post Coalesce Frames = 00000349Giant = 00000000Available Blocks = 256/256ISP Status:Version string burned in chip: "A986122997"New version after next program operation: "B018020998"ISP family type: "2096"ISP chip ID: 0x0013Device is programmable
Related Commands
show c7200 (7200)
To display information about the CPU and midplane for Cisco 7200 series routers, use the show c7200 command in EXEC mode.
show c7200
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Usage Guidelines
You can use the output of this command to determine whether the hardware version level and upgrade is current. The information is generally useful for diagnostic tasks performed by technical support only.
Examples
The following is sample output from the show c7200 command:
Router# show c7200C7200 Network IO Interrupt Throttling:throttle count=0, timer count=0active=0, configured=0netint usec=3999, netint mask usec=200C7200 Midplane EEPROM:Hardware revision 1.2 Board revision A0Serial number 2863311530 Part number 170-43690-170Test history 0xAA RMA number 170-170-170MAC=0060.3e28.ee00, MAC Size=1024EEPROM format version 1, Model=0x6EEPROM contents (hex):0x20: 01 06 01 02 AA AA AA AA AA AA AA AA 00 60 3E 280x30: EE 00 04 00 AA AA AA AA AA AA AA 50 AA AA AA AAC7200 CPU EEPROM:Hardware revision 2.0 Board revision A0Serial number 3509953 Part number 73-1536-02Test history 0x0 RMA number 00-00-00EEPROM format version 1EEPROM contents (hex):0x20: 01 15 02 00 00 35 8E C1 49 06 00 02 00 00 00 000x30: 50 00 00 00 FF FF FF FF FF FF FF FF FF FF FF FFshow cls
To display the current status of all Cisco link services (CLS) sessions on the router, use the show cls command in EXEC mode.
show cls [brief]
Syntax Description
Defaults
Without the brief argument, displays complete output.
Command Modes
EXEC
Command History
Usage Guidelines
The Cisco link service (CLS) is used as the interface between data link users (DLUs), such as DLSw, LAN Network Manager (LNM), downstream physical unit (DSPU), and SNASw, and their corresponding data link circuits (DLCs) such as Logic Link Control (LLC), VDLC, and Qualified Logic Link Control (QLLC). Each DLU registers a particular service access point (SAP) with CLS, and establishes circuits through CLS over the DLC.
The show cls command displays the SAP values associated with the DLU and the circuits established through CLS.
For further information about CLS, use the Release 12.2 Cisco IOS Bridging and IBM Networking Configuration Guide.
Examples
The following is sample output from the show cls command:
IBD-4500B# show clsDLU user:SNASWSSap:0x04 VDLC VDLC650DTE:1234.4000.0001 1234.4000.0002 04 04T1 timer:0 T2 timer:0 Inact timer:0max out:0 max in:0 retry count:10XID retry:10 XID timer:5000 I-Frame:0flow:0 DataIndQ:0 DataReqQ:0DLU user:DLSWDLUPEERDLU user:DLSWDLUBridging VDLC VDLC1000Bridging VDLC VDLC650The following is sample output from the show cls brief command:
IBD-4500B# show cls briefDLU user:SNASWSSap:0x04 VDLC VDLC650DTE:1234.4000.0001 1234.4000.0002 04 04DLU user:DLSWDLUPEERDLU user:DLSWDLUBridging VDLC VDLC1000Bridging VDLC VDLC650
The examples show two DLUs—SNASw and DLSw—active in the router. SNASw uses a SAP value of 0x04, and the associated DLC port is VDLC650. SNASw has a circuit established between MAC addresses 1234.4000.0001 and 1234.4000.0002 using source and destination SAPs 04 and 04. DLSw is a bridging protocol and uses VDLC1000 and VDLC650 ports. There are no circuits in place at this time.
In the output from the show cls command (without the brief argument), the values of timers and counters applicable to this circuit are displayed.
Related Commands
stun peer-name
Enables STUN for an IP address and uses Cisco Link Services (CLS) to access the Frame Relay network.
show context
To display information stored in NVRAM when an unexpected system reload (system exception) occurs, use the show context command in EXEC mode.
show context [summary | all | slot slot-number [crash-index] [all] [debug]]
Syntax Description
Command Modes
User EXEC
Privileged EXEC
Command History
10.3
This command was introduced.
11.2 GS
The slot slot-number [crash-index] [all] [debug] syntax was added for Cisco 12000 series routers.
Usage Guidelines
The display from the show context command includes the following information:
•
•
•
•
•
Note
Output for this command will vary by platform. Context information is specific to processors and architectures. For example, context information for the Cisco 2600 series router differs from that for other router types because the Cisco 2600 runs with an M860 processor.
Examples
The following is sample output from the show context command following a system failure:
Router> show contextSystem was restarted by error - a Software forced crash, PC 0x60189354GS Software (RSP-PV-M), Experimental Version 11.1(2033) [ganesh 111]Compiled Mon 31-Mar-97 13:21 by ganeshImage text-base: 0x60010900, data-base: 0x6073E000Stack trace from system failure:FP: 0x60AEA798, RA: 0x60189354FP: 0x60AEA798, RA: 0x601853CCFP: 0x60AEA7C0, RA: 0x6015E98CFP: 0x60AEA7F8, RA: 0x6011AB3CFP: 0x60AEA828, RA: 0x601706CCFP: 0x60AEA878, RA: 0x60116340FP: 0x60AEA890, RA: 0x6011632CFault History Buffer:GS Software (RSP-PV-M), Experimental Version 11.1(2033) [ganesh 111]Compiled Mon 31-Mar-97 13:21 by ganeshSignal = 23, Code = 0x24, Uptime 00:04:19$0 : 00000000, AT : 60930120, v0 : 00000032, v1 : 00000120a0 : 60170110, a1 : 6097F22C, a2 : 00000000, a3 : 00000000t0 : 60AE02A0, t1 : 8000FD80, t2 : 34008F00, t3 : FFFF00FFt4 : 00000083, t5 : 3E840024, t6 : 00000000, t7 : 11010132s0 : 00000006, s1 : 607A25F8, s2 : 00000001, s3 : 00000000s4 : 00000000, s5 : 00000000, s6 : 00000000, s7 : 6097F755t8 : 600FABBC, t9 : 00000000, k0 : 30408401, k1 : 30410000gp : 608B9860, sp : 60AEA798, s8 : 00000000, ra : 601853CCEPC : 60189354, SREG : 3400EF03, Cause : 00000024Router>The following is sample output from the show context summary command on a Cisco 12012 router. The show context summary command displays a summary of all the crashes recorded for each slot (line card).
Router# show context summaryCRASH INFO SUMMARYSlot 0 : 0 crashesSlot 1 : 0 crashesSlot 2 : 0 crashesSlot 3 : 0 crashesSlot 4 : 0 crashesSlot 5 : 0 crashesSlot 6 : 0 crashesSlot 7 : 2 crashes1 - crash at 18:06:41 UTC Tue Nov 5 19962 - crash at 12:14:55 UTC Mon Nov 4 1996Slot 8 : 0 crashesSlot 9 : 0 crashesSlot 10: 0 crashesSlot 11: 0 crashesRouter#The following is sample output from the show context command following an unexpected system reload on a Cisco 2600 series router. See Table 69 for a description of the fields in this output.
router# show contextS/W Version: Cisco Internetwork Operating System SoftwareIOS (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 mmagnoException occurred at: 00:02:26 UTC Mon Mar 1 1993Exception type: Data TLB Miss (0x1200)CPU Register Context:PC = 0x80109964 MSR = 0x00009030 CR = 0x55FFFD35 LR = 0x80109958CTR = 0x800154E4 XER = 0xC000BB6F DAR = 0x00000088 DSISR = 0x00000249DEC = 0x7FFFDFCA TBU = 0x00000000 TBL = 0x15433FCF IMMR = 0x68010020R0 = 0x80000000 R1 = 0x80E80BD0 R2 = 0x80000000 R3 = 0x00000000R4 = 0x80E80BC0 R5 = 0x40800000 R6 = 0x00000001 R7 = 0x68010000R8 = 0x00000000 R9 = 0x00000060 R10 = 0x00001030 R11 = 0xFFFFFFFFR12 = 0x00007CE6 R13 = 0xFFF379E8 R14 = 0x80D50000 R15 = 0x00000000R16 = 0x00000000 R17 = 0x00000000 R18 = 0x00000000 R19 = 0x00000000R20 = 0x00000000 R21 = 0x00000001 R22 = 0x00000010 R23 = 0x00000000R24 = 0x00000000 R25 = 0x80E91348 R26 = 0x01936010 R27 = 0x80E92A80R28 = 0x00000001 R29 = 0x019BA920 R30 = 0x00000000 R31 = 0x00000018Stack trace:Frame 00: SP = 0x80E80BD0 PC = 0x80109958Frame 01: SP = 0x80E80C28 PC = 0x8010A720Frame 02: SP = 0x80E80C40 PC = 0x80271010Frame 03: SP = 0x80E80C50 PC = 0x8025EE64Frame 04: SP = 0x80DEE548 PC = 0x8026702CFrame 05: SP = 0x80DEE558 PC = 0x8026702C
Related Commands
show processes
Displays information about the active processes.
show stacks
Monitors the stack usage of processes and interrupt routines.
show controllers (GRP image)
To display information that is specific to the hardware, use the show controllers command in privileged EXEC mode.
show controllers [atm slot-number | clock | csar [register] | csc-fpga | dp83800 | fab-clk | fia [register] | pos [slot-number] [details] | queues [slot-number] | sca | xbar]
Syntax Description
Command Modes
Privileged EXEC
Command History
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/0POS7/0SECTIONLOF = 2 LOS = 0 BIP(B1) = 5889Active Alarms: NoneLINEAIS = 2 RDI = 2 FEBE = 146 BIP(B2) = 2106453Active Alarms: NonePATHAIS = 2 RDI = 4 FEBE = 63 BIP(B3) = 3216LOP = 0 PSE = 8 NSE = 3 NEWPTR = 2Active Alarms: NoneAPSCOAPS = 3 PSBF = 2State: PSBF_state = FalseRx(K1/K2): F0/15 Tx(K1/K2): 00/00S1S0 = 00, C2 = 64PATH TRACE BUFFER : STABLERemote hostname : GSR-CRemote interface: POS10/0Remote IP addr : 10.201.101.2Remote Rx(K1/K2): F0/15 Tx(K1/K2): 00/00Router#Related Commands
clear controllers
Resets the T1 or E1 controller.
show controllers (line card image)
Displays information that is specific to the hardware on a line card.
show controllers (line card image)
To display information that is specific to the hardware on a line card, use the attach command in privileged EXEC mode to connect to the line card and then use the show controllers command in privileged EXEC mode or the execute-on command in privileged EXEC mode.
show controllers atm [[port-number] [all | sar | summary]]
show controllers fia [register]
show controllers {frfab | tofab} {bma {microcode | ms-inst | register} | qelem start-queue-element [end-queue-element] | qnum start-queue-number [end-queue-number] | queues | statistics}
show controllers io
show controllers l3
show controllers pos {framers | queues | registers | rxsram port-number queue-start-address [queue-length] | txsram port-number queue-start-address [queue-length]}
Syntax Description
Command Modes
Privileged EXEC
Command History
11.2 GS
This command was added to support the Cisco 12000 series Gigabit Switch Routers.
Usage Guidelines
This information displayed by this command is of use only to technical support representatives in analyzing unexpected system failures in the field. It is documented here in case you need to provide the displayed statistics to an technical support engineer.
Examples
Because you are executing this command on the line card, you must use the execute-on command to use the show command, or you must connect to the card using the attach command. All examples in this section use the execute-on command
The following is partial sample output from the show controllers atm command:
Router# execute-on slot 4 show controllers atm 0TX SAR (Beta 1.0.0) is Operational;RX SAR (Beta 1.0.0) is Operational;Interface Configuration Mode:STS-12cActive Maker Channels: total # 6VCID ChnnlID Type OutputInfo InPkts InOAMs MacString1 0888 UBR 0C010010 0 0 08882000AAAA0300000008002 0988 VBR 04010020 0 0 098820003 8BC8 UBR 0C010030 0 0 8BC82000AAAA0300000008004 0E08 UBR 0C010040 0 0 0E082000AAAA03000000080010 1288 VBR 040100A0 0 0 1288200011 8BE8 VBR 0C0100B0 0 0 8BE82000AAAA030000000800SAR Total Counters:total_tx_idle_cells 215267 total_tx_paks 0 total_tx_abort_paks 0total_rx_paks 0 total_rx_drop_paks 0 total_rx_discard_cells 15Switching Code Counters:total_rx_crc_err_paks 0 total_rx_giant_paks 0total_rx_abort_paks 0 total_rx_crc10_cells 0total_rx_tmout_paks 0 total_rx_unknown_paks 0total_rx_out_buf_paks 0 total_rx_unknown_vc_paks 0BATMAN Asic Register Values:hi_addr_reg 0x8000, lo_addr_reg 0x000C, boot_msk_addr 0x0780,rmcell_msk_addr 0x0724, rmcnt__msk_addr 0x07C2, txbuf_msk_addr 0x070C,...CM622 SAR Boot Configuration:txind_q_addr 0x14000 txcmd_q_addr 0x20000...SUNI-622 Framer Register Values:Master Rst and Ident/Load Meters Reg (#0x0): 0x10Master Configuration Reg (#0x1): 0x1FMaster Interrupt Status Reg (#0x2): 0x00PISO Interrupt Reg (#0x3): 0x04Master Auto Alarm Reg (#0x4): 0x03Master Auto Alarm Reg (#0x5): 0x07Parallel Output Port Reg (#0x6): 0x02...BERM Line BIP Threshold LSB Reg (#0x74): 0x00BERM Line BIP Threshold MSB Reg (#0x75): 0x00Router#The following is partial sample output from the show controllers command:
Router# execute-on slot 6 show controllersInterface POS0Hardware is BFLC POSlcpos_instance struct 60311B40RX POS ASIC addr space 12000000TX POS ASIC addr space 12000100SUNI framer addr space 12000400SUNI rsop intr status 00CRC32 enabled, HDLC enc, int clockno loopInterface POS1Hardware is BFLC POSlcpos_instance struct 603142E0RX POS ASIC addr space 12000000TX POS ASIC addr space 12000100SUNI framer addr space 12000600SUNI rsop intr status 00CRC32 enabled, HDLC enc, int clockno loop...Router#The following is partial sample output from the show controllers pos framers command:
Router# execute-on slot 6 show controllers pos framersFramer 0, addr=0x12000400:master reset C0master config 1F rrate sts3c trate sts3c fixptrmaster control 00clock rcv cntrl D0RACP control 84RACP gfc control 0FTACP control status 04 hcsaddRACP intr enable 04RSOP cntrl intr enable 00RSOP intr status 00TPOP path sig lbl (c2) 13SPTB control 04 tnullSPTB status 00Framer 1, addr=0x12000600:master reset C0master config 1F rrate sts3c trate sts3c fixptrmaster control 00clock rcv cntrl D0RACP control 84RACP gfc control 0FTACP control status 04 hcsaddRACP intr enable 04RSOP cntrl intr enable 00RSOP intr status 00TPOP path sig lbl (c2) 13SPTB control 04 tnullSPTB status 00Framer 2, addr=0x12000800:master reset C0master config 1F rrate sts3c trate sts3c fixptrmaster control 00clock rcv cntrl D0RACP control 84RACP gfc control 0FTACP control status 04 hcsaddRACP intr enable 04RSOP cntrl intr enable 00RSOP intr status 00TPOP path sig lbl (c2) 13SPTB control 04 tnullSPTB status 00...Router#The following is partial sample output from the show controllers fia command:
Router# execute-on slot 7 show controllers fia========= Line Card (Slot 7) =======Fabric configuration: Full bandwidth redundantMaster Scheduler: Slot 17From Fabric FIA Errors-----------------------redund fifo parity 0 redund overflow 0 cell drops 0crc32 lkup parity 0 cell parity 0 crc32 00 1 2 3 4-------- -------- -------- -------- --------los 0 0 0 0 0crc16 0 0 0 0 0To Fabric FIA Errors-----------------------sca not pres 0 req error 0 uni fifo overflow 0grant parity 0 multi req 0 uni fifo undrflow 0cntrl parity 0 uni req 0 crc32 lkup parity 0multi fifo 0 empty dst req 0 handshake error 0Related Commands
show controllers logging
To display logging information about a Versatile Interface Processor (VIP) card, use the show controllers logging command in privileged EXEC mode.
show controllers vip slot-number logging
Syntax Description
Command Modes
Privileged EXEC
Command History
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 loggingSyslog logging: enabledConsole logging: disabledMonitor logging: level debugging, 266 messages logged.Trap logging: level informational, 266 messages logged.Logging to 192.180.2.238Table 70 describes the significant fields shown in the display.
Related Commands
show controllers tech-support
To display general information about a Versatile Interface Processor (VIP) card when reporting a problem, use the show controllers tech-support command in privileged EXEC mode.
show controllers vip slot-number tech-support
Syntax Description
Command Modes
Privileged EXEC
Command History
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:
•
•
•
•
•
•
•
•
For a sample display of the show controllers tech-support command output, refer to these show commands.
Related Commands
show debugging
To display information about the types of debugging that are enabled for your router, use the show debugging command in privileged EXEC mode.
show debugging
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the show debugging command. In this example, three types of CDP debugging are enabled.
Router# show debuggingCDP:CDP packet info debugging is onCDP events debugging is onCDP neighbor info debugging is onRelated Commands
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 command in privileged EXEC mode.
show environment [alarms | all | fans | hardware | last | leds | power-supply | table | temperatures | voltages]
Syntax Description
Defaults
If no options are specified, the default is all.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The availability of keywords will depend on your system.
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
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.
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 environmentEnvironmental StatisticsEnvironmental status as of 13:17:39 UTC Thu Jun 6 1996Data is 7 second(s) old, refresh in 53 second(s)All Environmental Measurements are within specificationsTable 71 describes the significant fields shown in the display.
Cisco 7000 Series Routers
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 problemIn 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 allEnvironmental StatisticsEnvironmental status as of 23:19:47 UTC Wed Jun 12 1996Data is 6 second(s) old, refresh in 54 second(s)WARNING: Lower Power Supply is NON-OPERATIONALLower Power Supply:700W, OFF Upper Power Supply: 700W, ONIntermittent Powerfail(s): 2 Last on 23:07:05 UTC Mon Jun 10 1996+12 volts measured at 12.05(V)+5 volts measured at 4.96(V)-12 volts measured at -12.05(V)+24 volts measured at 23.80(V)Airflow temperature measured at 38(C)Inlet temperature measured at 25(C)Table 72 describes the significant fields shown in the display.
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 lastEnvironmental StatisticsEnvironmental status as of 14:47:00 UTC Sun May 21 1995Data is 6 second(s) old, refresh in 54 second(s)WARNING: Upper Power Supply is NON-OPERATIONALLAST Environmental StatisticsEnvironmental status as of 12:40:00 UTC Fri May 19 1995Lower Power Supply: 700W, ON Upper Power Supply: 700W, OFFNo Intermittent Powerfails+12 volts measured at 12.05(V)+5 volts measured at 4.98(V)-12 volts measured at -12.00(V)+24 volts measured at 23.80(V)Airflow temperature measured at 30(C)Inlet temperature measured at 23(C)Table 73 describes the significant fields shown in the display.
In the following example, shows sample output for the current environmental status in tables that list voltage and temperature parameters. There are three warning messages: one each about the lower power supply, the airflow temperature, and the inlet temperature. In this example, voltage parameters are shown to be in the normal range, airflow temperature is at a critical level, and inlet temperature is at the warning level.
Router> show environment tableEnvironmental StatisticsEnvironmental status as of Mon 11-2-1992 17:43:36Data is 52 second(s) old, refresh in 8 second(s)WARNING: Lower Power Supply is NON-OPERATIONALWARNING: Airflow temperature has reached CRITICAL level at 73(C)WARNING: Inlet temperature has reached WARNING level at 41(C)Voltage Parameters:SENSE CRITICAL NORMAL CRITICAL-------|--------------------|------------------------|--------------------+12(V) 10.20 12.05(V) 13.80+5(V) 4.74 4.98(V) 5.26-12(V) -10.20 -12.05(V) -13.80+24(V) 20.00 24.00(V) 28.00Temperature Parameters:SENSE WARNING NORMAL WARNING CRITICAL SHUTDOWN-------|-------------|------------|-------------|--------------|-----------Airflow 10 60 70 73(C) 88Inlet 10 39 41(C) 46 64Table 74 describes the significant fields shown in the display.
Cisco 7200 Series Routers
The system displays the following message if the voltage or temperature enters the "Warning" range:
%ENVM-4-ENVWARN: Chassis outlet 3 measured at 55C/131FThe system displays the following message if the voltage or temperature enters the "Critical" range:
%ENVM-2-ENVCRIT: +3.45 V measured at +3.65 VThe system displays the following message if the voltage or temperature exceeds the maximum margins:
%ENVM-0-SHUTDOWN: Environmental Monitor initiated shutdownThe 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 removedThe 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 shutdownThe 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 allPower Supplies:Power supply 1 is unknown. Unit is off.Power supply 2 is Zytek AC Power Supply. Unit is on.Temperature readings:chassis inlet measured at 25C/77Fchassis outlet 1 measured at 29C/84Fchassis outlet 2 measured at 36C/96Fchassis outlet 3 measured at 44C/111FVoltage readings:+3.45 V measured at +3.83 V:Voltage in Warning range!+5.15 V measured at +5.09 V+12.15 measured at +12.42 V-11.95 measured at -12.10 VTable 75 describes the significant fields shown in the display.
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 lastchassis inlet previously measured at 27C/80Fchassis outlet 1 previously measured at 31C/87Fchassis outlet 2 previously measured at 37C/98Fchassis outlet 3 previously measured at 45C/113F+3.3 V previously measured at 4.02+5.0 V previously measured at 4.92+12.0 V previously measured at 12.65-12.0 V previously measured at 11.71last shutdown reason - power supply shutdownTable 76 describes the significant fields shown in the display.
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 tableSample Point LowCritical LowWarning HighWarning HighCriticalchassis inlet 40C/104F 50C/122Fchassis outlet 1 43C/109F 53C/127Fchassis outlet 2 75C/167F 75C/167Fchassis outlet 3 55C/131F 65C/149F+3.45 V +2.76 +3.10 +3.80 +4.14+5.15 V +4.10 +4.61 +5.67 +6.17+12.15 V +9.72 +10.91 +13.37 +14.60-11.95 V -8.37 -9.57 -14.34 -15.53Shutdown system at 70C/158FTable 77 describes the significant fields shown in the display.
Cisco 7500 Series Router
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 allArbiter 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: noneFan transfer point: 100%Active trip points: Restart_Inhibit15 of 15 soft shutdowns remaining before hard shutdown10123456789012Dbus slots: X XX Xcard inlet hotpoint exhaustRSP(6) 35C/95F 47C/116F 40C/104FRSP(7) 35C/95F 43C/109F 39C/102FShutdown temperature source is `hotpoint' on RSP(6), requested RSP(6)+12V measured at 12.31+5V measured at 5.21-12V measured at -12.07+24V measured at 22.08+2.5 reference is 2.49PS1 +5V Current measured at 59.61 A (capacity 200 A)PS1 +12V Current measured at 5.08 A (capacity 35 A)PS1 -12V Current measured at 0.42 A (capacity 3 A)PS1 output is 378 WTable 78 describes the significant fields shown in the display.
The following example is for the Cisco 7500 series router. This example shows the measurements immediately before the last shutdown.
7500# show environment lastRSP(4) Inlet previously measured at 37C/98FRSP(4) Hotpoint previously measured at 46C/114FRSP(4) Exhaust previously measured at 52C/125F+12 Voltage previously measured at 12.26+5 Voltage previously measured at 5.17-12 Voltage previously measured at -12.03+24 Voltage previously measured at 23.78Table 79 describes the significant fields shown in the display.
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 error messages occur. There are two level of messages: warning and critical.
7500# show environment tableSample Point LowCritical LowWarning HighWarning HighCriticalRSP(4) Inlet 44C/111F 50C/122FRSP(4) Hotpoint 54C/129F 60C/140FRSP(4) Exhaust+12 Voltage 10.90 11.61 12.82 13.38+5 Voltage 4.61 4.94 5.46 5.70-12 Voltage -10.15 -10.76 -13.25 -13.86+24 Voltage 20.38 21.51 26.42 27.652.5 Reference 2.43 2.51Shutdown boards at 70C/158FShutdown power supplies at 76C/168FRestart after shutdown below 40C/104FTable 80 describes the significant fields shown in the display.
Cisco AS5300 Series Access Servers
In the following example, how keywords and options are limited according to the physical characteristics of the system is shown:
as5300# show environment ?all All environmental monitor parameterslast Last environmental monitor parameterstable Temperature and voltage ranges| Output modifiers<cr>as5300# show environment table%This option not available on this platformCisco 12000 Series GSR
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 environmentSlot # 3V 5V MBUS 5V Hot Sensor Inlet Sensor(mv) (mv) (mv) (deg C) (deg C)0 3300 4992 5040 42.0 37.02 3296 4976 5136 40.0 33.04 3280 4992 5120 38.5 31.57 3280 4984 5136 42.0 32.09 3292 4968 5160 39.5 31.511 3288 4992 5152 40.0 30.516 3308 NA 5056 42.5 38.017 3292 NA 5056 40.5 36.518 3304 NA 5176 36.5 35.019 3300 NA 5184 37.5 33.520 3304 NA 5168 36.5 34.024 NA 5536 5120 NA 31.526 NA 5544 5128 NA 31.528 NA NA 5128 NA NA29 NA NA 5104 NA NASlot # 48V AMP_48(Volt) (Amp)24 46 1226 46 19Slot # Fan 0 Fan 1 Fan 2(RPM) (RPM) (RPM)28 2160 2190 216029 2130 2190 2070Router#Table 81 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.
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 allSlot # Hot Sensor Inlet Sensor(deg C) (deg C)2 31.0 22.05 33.5 26.516 25.5 21.518 22.0 21.019 22.5 21.024 NA 29.526 NA 24.5Slot # 3V 5V MBUS 5V(mv) (mv) (mv)2 3292 5008 51365 3292 5000 512816 3272 NA 512818 3300 NA 512819 3316 NA 5128Slot # 5V MBUS 5V 48V AMP_48(mv) (mv) (Volt) (Amp)24 0 5096 3 026 5544 5144 47 3Slot # Fan Information16 Voltage 16V Speed slow: Main Fans Ok Power Supply fans OkAlarm IndicatorsNo alarmsSlot # Card Specific Leds16 Mbus OK SFCs Failed18 Mbus OK19 Mbus OK24 Input Failed26 Input OkThe 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 tableHot Sensor Temperature Limits (deg C):Warning Critical ShutdownGRP/GLC (Slots 0-15) 40 46 57CSC (Slots 16-17) 46 51 65SFC (Slots 18-20) 41 46 60Inlet Sensor Temperature Limits (deg C):Warning Critical ShutdownGRP/GLC (Slots 0-15) 35 40 52CSC (Slots 16-17) 40 45 59SFC (Slots 18-20) 37 42 543V Ranges (mv):Warning Critical ShutdownBelow Above Below Above Below AboveGRP/GLC (Slots 0-15) 3200 3400 3100 3500 3050 3550CSC (Slots 16-17) 3200 3400 3100 3500 3050 3550SFC (Slots 18-20) 3200 3400 3100 3500 3050 35505V Ranges (mv):Warning Critical ShutdownBelow Above Below Above Below AboveGRP/GLC (Slots 0-15) 4850 5150 4750 5250 4680 5320MBUS_5V Ranges (mv):Warning Critical ShutdownBelow Above Below Above Below AboveGRP/GLC (Slots 0-15) 5000 5250 4900 5350 4750 5450CSC (Slots 16-17) 4820 5150 4720 5250 4750 5450SFC (Slots 17-20) 5000 5250 4900 5350 4750 5450
Blower Operational Range (RPM):Top Blower:Warning CriticalBelow BelowFan 0 1000 750Fan 1 1000 750Fan 2 1000 750Bottom Blower:Warning CriticalBelow BelowFan 0 1000 750Fan 1 1000 750Fan 2 1000 750The 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 leds16 leds Mbus OK18 leds Mbus OK19 leds Mbus OK20 leds Mbus OKRelated Commands
show gsr
To display hardware information on the Cisco 12000 series Gigabit Switch Routers (GSRs), use the show gsr command in EXEC mode.
show gsr [chassis-info [details]]
Syntax Description
chassis-info
(Optional) Displays backplane NVRAM information.
details
(Optional) In addition to the information displayed, this option includes hexadecimal output of the backplane NVRAM information.
Command Modes
EXEC
Command History
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 gsrSlot 0 type = Route Processorstate = IOS Running MASTERSlot 7 type = 1 Port Packet Over SONET OC-12c/STM-4cstate = Card PoweredSlot 16 type = Clock Scheduler Cardstate = Card Powered PRIMARY CLOCKThe following is sample output from the show gsr chassis-info command for a Cisco 12012 router:
Router# show gsr chassis-infoBackplane NVRAM [version 0x20] Contents -Chassis: type 12012 Fab Ver: 1Chassis S/N: ZQ24CS3WT86MGVHLPCA: 800-3015-1 rev: A0 dev: 257 HW ver: 1.0Backplane S/N: A109EXPR75FUNYJKMAC Addr: base 0000.EAB2.34FF block size: 1024RMA Number: 0x5F-0x2D-0x44 code: 0x01 hist: 0x1Ashow gt64010 (7200)
To display all GT64010 internal registers and interrupt status on the Cisco 7200 series routers, use the show gt64010 command in EXEC mode.
show gt64010
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
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 gt64010GT64010 Channel 0 DMA:dma_list=0x6088C3EC, dma_ring=0x4B018480, dma_entries=256dma_free=0x6088CECC, dma_reqt=0x6088CECC, dma_done=0x6088CECCthread=0x6088CEAC, thread_end=0x6088CEACbackup_thread=0x0, backup_thread_end=0x0dma_working=0, dma_complete=6231, post_coalesce_frames=6231exhausted_dma_entries=0, post_coalesce_callback=6231GT64010 Register Dump: Registers at 0xB4000000CPU Interface:cpu_interface_conf : 0x80030000 (b/s 0x00000380)addr_decode_err : 0xFFFFFFFF (b/s 0xFFFFFFFF)Processor Address Space :ras10_low : 0x00000000 (b/s 0x00000000)ras10_high : 0x07000000 (b/s 0x00000007)ras32_low : 0x08000000 (b/s 0x00000008)ras32_high : 0x0F000000 (b/s 0x0000000F)cs20_low : 0xD0000000 (b/s 0x000000D0)cs20_high : 0x74000000 (b/s 0x00000074)cs3_boot_low : 0xF8000000 (b/s 0x000000F8)cs3_boot_high : 0x7E000000 (b/s 0x0000007E)pci_io_low : 0x00080000 (b/s 0x00000800)pci_io_high : 0x00000000 (b/s 0x00000000)pci_mem_low : 0x00020000 (b/s 0x00000200)pci_mem_high : 0x7F000000 (b/s 0x0000007F)internal_spc_decode : 0xA0000000 (b/s 0x000000A0)bus_err_low : 0x00000000 (b/s 0x00000000)bus_err_high : 0x00000000 (b/s 0x00000000)...show logging
To display the state of system logging (syslog) and the contents of the standard syslog (system error message) buffer , use the show logging command in privileged EXEC mode.
show logging [slot slot-number | summary]
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
This command displays the state of syslog error and event logging, including host addresses, and which logging destinations (console, monitor, buffer, or host) logging is enabled. This command also displays Simple Network Management Protocol (SNMP) logging configuration parameters and protocol activity.
This command will also display the contents of the standard system logging buffer, if logging to the buffer is enabled. Logging to the buffer is enabled or disabled using the [no] logging buffered command. The number of system error and debugging messages in the system logging buffer is determined by the configured size of the syslog buffer. This size of the syslog buffer is also set using the logging buffered command.
To enable and set the format for syslog message timestamping, use the service timestamps log command.
If debugging is enabled (using any debug command), and the logging buffer is configured to include level 7 (debugging) messages, debug output will be included in the system log. Debugging output is not formatted like system error messages, and will not be preceded by the percent symbol (%).
Examples
The following is sample output from the show logging command. In this example, buffer logging is disabled, so no syslog messages are displayed with this command.
Router# show loggingSyslog logging: enabled (0 messages dropped, 1 messages rate-limited, 0 flushes)Console logging: level debugging, 31 messages logged, xml disabled
Monitor logging: level debugging, 0 messages logged, xml disabled
Buffer logging: disabled, xml disabled
Logging Exception size (4096 bytes)
Count and timestamp logging messages: enabled
Trap logging: level informational, 35 message lines logged
Table 82 describes the significant fields shown in the display.
The following example includes syslog messages from the system buffer, with timestamping :
Router> show logggingSyslog logging:enabled (2 messages dropped, 0 flushes, 0 overruns)Console logging:disabledMonitor logging:level debugging, 0 messages loggedBuffer logging:level debugging, 4104 messages loggedTrap logging:level debugging, 4119 message lines loggedLogging to 216.231.111.14, 4119 message lines loggedLog Buffer (262144 bytes):Jul 11 12:17:49 EDT:%BGP-4-MAXPFX:No. of prefix received from 209.165.200.225 (afi 0) reaches 24, max 24! THE FOLLOWING LINE IS A DEBUG MESSAGE FROM NTP.! NOTE THAT IT IS NOT PRECEEDED BY THE % SYMBOL.Jul 11 12:17:48 EDT: NTP: Maxslew = 213866
Jul 11 15:15:41 EDT:%SYS-5-CONFIG:Configured from tftp://host.com/addc5505-rsm.nyiix.Jul 11 15:30:28 EDT:%BGP-5-ADJCHANGE:neighbor 209.165.200.226 Up.Jul 11 15:31:34 EDT:%BGP-3-MAXPFXEXCEED:No. of prefix received from209.165.200.226 (afi 0):16444 exceed limit 375.Jul 11 15:31:34 EDT:%BGP-5-ADJCHANGE:neighbor 209.165.200.226 Down BGPNotification sent.Jul 11 15:31:34 EDT:%BGP-3-NOTIFICATION:sent to neighbor 209.165.200.226 3/1 (update malformed) 0 bytes. . .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.
Table 83 describes the symbols that proceed the timestamp.
The following is sample output from the show logging summary command for a 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 error message, 4 warning messages, and 47 notification messages.
Note
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#Table 84 describes the logging level fields shown in the display.
Related Commands
show logging count
To display a summary of the number of times certain system error messages are occurring, use the show logging command in privileged EXEC mode.
show logging count
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
To enable the error log count capability (syslog counting feature), use the logging count command in global configuration mode.
This feature works independently of the various settings of the other logging commands (such as [no] logging on, [no] logging buffered, and so on). In other words, turning off logging by other means does not stop the counting and timestamping from occurring.
This command displays information such as the number of times a particular system error message occurs and the time stamp of the last occurrence of the specified message. System error messages are grouped into logical units called "Facilities" based on Cisco IOS software components.
To determine if system error message counting is enabled, use the show logging command.
The service timestamps command configuration determines the timestamp format (shown in the "Last Time" column) of show logging count command output. There is not quite enough space for all options of the possible options (datetime, milliseconds, and timezone) of the service timestamps datetime command to be displayed at the same time. As a result, if msec is selected, timezone will not be displayed. If show-timezone is selected but not msec, then the time zone will be displayed.
Occasionally, the length of the message name plus the facility name contains too many characters to be printed on one line. The CLI attempts to keep the name and facility name on one line but, if necessary, the line will be wrapped, so that the first line contains the facility name and the second line contains the message name and the rest of the columns.
Examples
The following example shows the number of times syslog messages have occurred and the most recent time that each error message occurred. In this example, the show logging command is used to determine if the syslog counting feature is enabled:
Router# show logging | include countCount and timestamp logging messages: enabledRouter# show logging countFacility Message Name Sev Occur Last Time=============================================================================SYS BOOTTIME 6 1 00:00:12SYS RESTART 5 1 00:00:11SYS CONFIG_I 5 1 00:00:05------------- ------------------------------- -----------------------------SYS TOTAL 3LINEPROTO UPDOWN 5 13 00:00:19------------- ------------------------------- -----------------------------LINEPROTO TOTAL 13LINK UPDOWN 3 1 00:00:18LINK CHANGED 5 12 00:00:09------------- ------------------------------- -----------------------------LINK TOTAL 13SNMP COLDSTART 5 1 00:00:11------------- ------------------------------- -----------------------------SNMP TOTAL 1Table 85 describes the significant fields shown in the display.
In the following example, the user is interested only in the totals:
Router# show logging count | include totalSYS TOTAL 3LINEPROTO TOTAL 13LINK TOTAL 13SNMP TOTAL 1
Related Commands
show logging history
To display information about the state of the syslog history table, use the show logging history command in privileged EXEC mode.
show logging history
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
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 historySyslog History Table: 1 maximum table entries,saving level notifications or higher0 messages ignored, 0 dropped, 15 table entries flushed,SNMP notifications not enabledentry number 16: SYS-5-CONFIG_IConfigured from console by consoletimestamp: 1110Router#Table 86 describes the significant fields shown in the output.
Related Commands
show logging xml
To display the state of system message logging in an XML format, and to display the contents of the XML syslog buffer, use the show logging xml command in privileged EXEC mode.
show logging xml
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command displays the same syslog state information as the standard show logging command, but displays the information in XML format. This command also displays the content of the XML syslog buffer (if XML-formatted buffer logging is enabled).
Examples
The following example compares the output of the standard show logging command with the output of the show logging xml command so that you can see how the standard information is formatted in XML.
Router# show loggingSyslog logging: enabled (10 messages dropped, 6 messages rate-limited, 0 flushes, 0 overruns, xml enabled)Console logging: level debugging, 28 messages logged, xml enabledMonitor logging: level debugging, 0 messages logged, xml enabledBuffer logging: level debugging, 2 messages logged, xml enabled (2 messages logged)Logging Exception size (8192 bytes)Count and timestamp logging messages: disabledTrap logging: level informational, 35 message lines loggedLogging to 1.2.3.4, 1 message lines logged, xml disabledLogging to 4.3.2.1, 1 message lines logged, xml enabledLog Buffer (8192 bytes):00:04:20: %SYS-5-CONFIG_I: Configured from console by console00:04:41: %SYS-5-CONFIG_I: Configured from console by consoleRouter#show logging xml<syslog-logging status="enabled" msg-dropped="10" msg-rate-limited="6" flushes="0" overruns="0"><xml>enabled</xml></syslog-logging><console-logging level="debugging" messages-logged="28"><xml>enabled</xml></console-logging><monitor-logging level="debugging" messages-logged="0"><xml>enabled</xml></monitor-logging><buffer-logging level="debugging" messages-logged="2"><xml messages-logged="2">enabled</xml></buffer-logging><logging-exception size="8192 bytes"></logging-exception><count-and-timestamp-logging status="disabled"></count-and-timestamp-logging><trap-logging level="informational" messages-lines-logged="35"></trap-logging><logging-to><dest id="0" ipaddr="1.2.3.4" message-lines-logged="1"><xml>disabled</xml><dest></logging-to><logging-to><dest id="1" ipaddr="4.3.2.1" message-lines-logged="1"><xml>enabled</xml><dest></logging-to><log-xml-buffer size="44444 bytes"></log-xml-buffer><ios-log-msg><facility>SYS</facility><severity>5</severity><msg-id>CONFIG_I</msg-id><time> 00:04:20</time><args><arg id="0">console</arg><arg id="1">console</arg></args></ios-log-msg><ios-log-msg><facility>SYS</facility><severity>5</severity><msg-id>CONFIG_I</msg-id><time> 00:04:41</time><args><arg id="0">console</arg><arg id="1">console</arg></args></ios-log-msg>Router#Table 82 describes the significant fields shown in the displays.
Related Commands
show memory
To show statistics about memory, including memory-free pool statistics, use the show memory command in EXEC mode.
show memory [memory-type] [free] [summary]
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
The show memory command displays information about memory available after the system image decompresses and loads.
Examples
The following is sample output from the show memory command:
Router# show memoryHead Total(b) Used(b) Free(b) Lowest(b) Largest(b)Processor B0EE38 5181896 2210036 2971860 2692456 2845368Processor memoryAddress Bytes Prev. Next Ref PrevF NextF Alloc PC WhatB0EE38 1056 0 B0F280 1 18F132 List ElementsB0F280 2656 B0EE38 B0FD08 1 18F132 List HeadersB0FD08 2520 B0F280 B10708 1 141384 TTY dataB10708 2000 B0FD08 B10F00 1 14353C TTY Input BufB10F00 512 B10708 B11128 1 14356C TTY Output BufB11128 2000 B10F00 B11920 1 1A110E Interrupt StackB11920 44 B11128 B11974 1 970DE8 *Init*B11974 1056 B11920 B11DBC 1 18F132 messagesB11DBC 84 B11974 B11E38 1 19ABCE Watched BooleanB11E38 84 B11DBC B11EB4 1 19ABCE Watched BooleanB11EB4 84 B11E38 B11F30 1 19ABCE Watched BooleanB11F30 84 B11EB4 B11FAC 1 19ABCE Watched BooleanRouter#The following is sample output from the show memory free command:
Router# show memory freeHead Total(b) Used(b) Free(b) Lowest(b) Largest(b)Processor B0EE38 5181896 2210076 2971820 2692456 2845368Processor memoryAddress Bytes Prev. Next Ref PrevF NextF Alloc PC What24 Free list 1CEB844 32 CEB7A4 CEB88C 0 0 0 96B894 SSE Manager52 Free list 272 Free list 376 Free list 480 Free list 5D35ED4 80 D35E30 D35F4C 0 0 D27AE8 96B894 SSE ManagerD27AE8 80 D27A48 D27B60 0 D35ED4 0 22585E SSE Manager88 Free list 6100 Free list 7D0A8F4 100 D0A8B0 D0A980 0 0 0 2258DA SSE Manager104 Free list 8B59EF0 108 B59E8C B59F84 0 0 0 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 88 describes the significant fields shown in the first section of the display.
The second section of the display is a block-by-block listing of memory use. Table 89 describes the significant fields shown in the second section of the display.
The show memory io command displays the free I/O memory blocks. On the Cisco 4000 router, this command quickly shows how much unused I/O memory is available.
The following is sample output from the show memory io command:
Router# show memory ioAddress Bytes Prev. Next Ref PrevF NextF Alloc PC What6132DA0 59264 6132664 6141520 0 0 600DDEC 3FCF0 *Packet Buffer*600DDEC 500 600DA4C 600DFE0 0 6132DA0 600FE68 0600FE68 376 600FAC8 600FFE0 0 600DDEC 6011D54 06011D54 652 60119B4 6011FEO 0 600FE68 6013D54 0614FCA0 832 614F564 614FFE0 0 601FD54 6177640 06177640 2657056 6172E90 0 0 614FCA0 0 0Total: 2723244The show memory sram command displays the free SRAM memory blocks. For the Cisco 4000 router, this command supports the high-speed static RAM memory pool to make it easier to debug or diagnose problems with allocation or freeing of such memory.
The following is sample output from the show memory sram command:
Router# show memory sramAddress Bytes Prev. Next Ref PrevF NextF Alloc PC What7AE0 38178 72F0 0 0 0 0 0Total 38178The following example of the show memory command used on the Cisco 4000 router includes information about SRAM memory and I/O memory:
Router# show memoryHead Total(b) Used(b) Free(b) Lowest(b) Largest(b)Processor 49C724 28719324 1510864 27208460 26511644 15513908I/O 6000000 4194304 1297088 2897216 2869248 2896812SRAM 1000 65536 63400 2136 2136 2136Address Bytes Prev. Next Ref PrevF NextF Alloc PC What1000 2032 0 17F0 1 3E73E *Init*17F0 2032 1000 1FE0 1 3E73E *Init*1FE0 544 17F0 2200 1 3276A *Init*2200 52 1FE0 2234 1 31D68 *Init*2234 52 2200 2268 1 31DAA *Init*2268 52 2234 229C 1 31DF2 *Init*72F0 2032 6E5C 7AE0 1 3E73E Init7AE0 38178 72F0 0 0 0 0 0The 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 a partial sample output from the show memory summary command. This command shows the size, blocks, and bytes allocated. Bytes equal the size multiplied by the blocks. For a description of the other fields, see Table 20 and Table 21.
Router# show memory summaryHead Total(b) Used(b) Free(b) Lowest(b) Largest(b)Processor B0EE38 5181896 2210216 2971680 2692456 2845368Processor memoryAlloc PC Size Blocks Bytes What0x2AB2 192 1 192 IDB: Serial Info0x70EC 92 2 184 Init0xC916 128 50 6400 RIF Cache0x76ADE 4500 1 4500 XDI data0x76E84 4464 1 4464 XDI data0x76EAC 692 1 692 XDI data0x77764 408 1 408 Init0x77776 116 1 116 Init0x777A2 408 1 408 Init0x777B2 116 1 116 Init0xA4600 24 3 72 List0xD9B5C 52 1 52 SSE Manager.......................0x0 0 3413 2072576 Pool Summary0x0 0 28 2971680 Pool Summary (Free Blocks)0x0 40 3441 137640 Pool Summary(All Block Headers)0x0 0 3413 2072576 Memory Summary0x0 0 28 2971680 Memory Summary (Free Blocks)Related Commands
show memory ecc
To display single-bit Error Code Correction (ECC) error logset data, use the show memory ecc command in privileged EXEC mode.
show memory ecc
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
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 eccECC 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/WriteTotal Single Bit error(s) thus far: 2Table 88 describes the significant fields shown in the first section of the display.
Related Commands
show memory
Displays statistics about memory, including memory-free pool statistics.
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 command in EXEC mode.
show pci {hardware | bridge [register]}
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
The output of this command is generally useful for diagnostic tasks performed by technical support only.
Note
Examples
The following is sample output for the PCI bridge register 1 on a Cisco 7200 series router:
Router# show pci bridge 1Bridge 4, Port Adaptor 1, Handle=1DEC21050 bridge chip, config=0x0(0x00): cfid = 0x00011011(0x04): cfcs = 0x02800147(0x08): cfccid = 0x06040002(0x0C): cfpmlt = 0x00010010(0x18): cfsmlt = 0x18050504(0x1C): cfsis = 0x22805050(0x20): cfmla = 0x48F04880(0x24): cfpmla = 0x00004880(0x3C): cfbc = 0x00000000(0x40): cfseed = 0x00100000(0x44): cfstwt = 0x00008020The 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 hardwareGT64010 External PCI Configuration registers:Vendor / Device ID : 0xAB114601 (b/s 0x014611AB)Status / Command : 0x17018002 (b/s 0x02800117)Class / Revision : 0x00000006 (b/s 0x06000000)Latency : 0x0F000000 (b/s 0x0000000F)RAS[1:0] Base : 0x00000000 (b/s 0x00000000)RAS[3:2] Base : 0x00000001 (b/s 0x01000000)CS[2:0] Base : 0x00000000 (b/s 0x00000000)CS[3] Base : 0x00000000 (b/s 0x00000000)Mem Map Base : 0x00000014 (b/s 0x14000000)IO Map Base : 0x01000014 (b/s 0x14000001)Int Pin / Line : 0x00010000 (b/s 0x00000100)Bridge 0, Downstream MB0 to MB1, Handle=0DEC21050 bridge chip, config=0x0(0x00): cfid = 0x00011011(0x04): cfcs = 0x02800143(0x08): cfccid = 0x06040002(0x0C): cfpmlt = 0x00011810(0x18): cfsmlt = 0x18000100(0x1C): cfsis = 0x02809050(0x20): cfmla = 0x4AF04880(0x24): cfpmla = 0x4BF04B00(0x3C): cfbc = 0x00000000(0x40): cfseed = 0x00100000(0x44): cfstwt = 0x00008020...show pci hardware
To display information about the Host-PCI bridge, use the show pci hardware command in EXEC mode.
show pci hardware
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Usage Guidelines
The output of this command is generally useful for diagnostic tasks performed by technical support only:
router# show pci hardwarehardware PCI hardware registersEach device on the PCI bus is assigned a PCI device number. For theC2600, device numbers are as follows:Device Device number0 First LAN device1 Second LAN device2 AIM device (if present)3 Not presently used4 Port module - first PCI device5 Port module - second PCI device6 Port module - third PCI device7 Port module - fourth PCI device8-14 Not presently used15 Xilinx PCI bridgeExamples
The following is partial sample output for the PCI hardware register, which also includes information on all the PCI bridge registers. Table 91 describes the significant fields shown in the display.
router# show pci hardwareXILINX Host-PCI Bridge Registers:Vendor / Device ID: 0x401310EEStatus / Command: 0x040001C6PCI Slave Base Reg 0: 0x00000000PCI Slave Base Reg 1: 0x04000000
show processes
To display information about the active processes, use the show processes command in EXEC mode.
show processes [history]
Syntax Description
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the show processes command:
Router# show processesCPU utilization for five seconds: 21%/0%; one minute: 2%; five minutes: 2%PID QTy PC Runtime (ms) Invoked uSecs Stacks TTY Process1 Mwe 2FEA4E 1808 464 3896 1796/3000 0 IP-EIGRP Router2 Lst 11682 10236 109 93908 1828/2000 0 Check heaps3 Mst 3AE9C 0 280 0 1768/2000 0 Timers4 Lwe 74AD2 0 12 0 1492/2000 0 ARP Input5.ME 912E4 0 2 0 1892/2000 0 IPC Zone Manager6.ME 91264 0 1 0 1936/2000 0 IPC Realm Manager7.ME 91066 0 30 0 1784/2000 0 IPC Seat Manager8.ME 133368 0 1 0 1928/2000 0 CXBus hot stall9.ME 1462EE 0 1 0 1940/2000 0 Microcode load10 Msi 127538 4 76 52 1608/2000 0 Env Mon11.ME 160CF4 0 1 0 1932/2000 0 MIP Mailbox12 Mwe 125D7C 4 280 14 1588/2000 0 SMT input13 Lwe AFD0E 0 1 0 1772/2000 0 Probe Input14 Mwe AF662 0 1 0 1784/2000 0 RARP Input15 Hwe A1F9A 228 549 415 3240/4000 0 IP Input16 Msa C86A0 0 114 0 1864/2000 0 TCP Timer17 Lwe CA700 0 1 0 1756/2000 0 TCP Protocols18.ME CCE7C 0 1 0 1940/2000 0 TCP Listener19 Mwe AC49E 0 1 0 1592/2000 0 BOOTP Server20 Mwe 10CD84 24 77 311 1652/2000 0 CDP Protocol21 Mwe 27BF82 0 2 0 1776/2000 0 ATMSIG InputThe following is sample output from the show processes history command:
Router# show process historyPID Exectime(ms) Caller PC Process Name3 12 0x0 Exec16 0 0x603F4DEC GraphIt21 0 0x603CFEF4 TTY Background22 0 0x6042FD7C Per-Second Jobs67 0 0x6015CD38 SMT input39 0 0x60178804 FBM Timer16 0 0x603F4DEC GraphIt21 0 0x603CFEF4 TTY Background22 0 0x6042FD7C Per-Second Jobs16 0 0x603F4DEC GraphIt21 0 0x603CFEF4 TTY Background22 0 0x6042FD7C Per-Second Jobs67 0 0x6015CD38 SMT input39 0 0x60178804 FBM Timer24 0 0x60425070 Compute load avgs11 0 0x605210A8 ARP Input69 0 0x605FDAF4 DHCPD Database69 0 0x605FD568 DHCPD Database51 0 0x60670B3C IP Cache Ager69 0 0x605FD568 DHCPD Database36 0 0x606E96DC SSS Test Client69 0 0x605FD568 DHCPD Database--More--PID Exectime(ms) Caller PC Process Name16 0 0x603F4DEC GraphIt21 0 0x603CFEF4 TTY Background22 0 0x6042FD7C Per-Second Jobs34 0 0x60679D74 CDP Protocol19 0 0x6041FBA4 Net Background36 0 0x606E97AC SSS Test Client12 0 0x60722A40 HC Counter Timers69 0 0x605FD568 DHCPD Database44 0 0x6031AD14 Adj Manager65 4 0x60BC5BE0 SAA Event Processor25 8 0x6042FDDC Per-minute Jobs16 0 0x603F4DEC GraphIt21 0 0x603CFEF4 TTY Background22 0 0x6042FD7C Per-Second Jobs67 0 0x6015CD38 SMT input39 0 0x60178804 FBM Timer2 0 0x60496768 Load Meter16 0 0x603F4DEC GraphIt21 0 0x603CFEF4 TTY Background22 0 0x6042FD7C Per-Second Jobs16 0 0x603F4DEC GraphIt21 0 0x603CFEF4 TTY Background22 0 0x6042FD7C Per-Second Jobs--More--. . .Table 92 describes the significant fields shown in the displays.
Note
For a list of process descriptions, see /en/US/products/sw/iosswrel/ps1828/products_tech_note09186a00800a65d0.shtml .
Related Commands
show processes cpu
To display CPU utilization information about the active processes in a device, use the show processes cpu command in privileged EXEC mode.
show processes cpu [history | sorted]
Syntax Description
history
(Optional) Displays CPU history in a graph format.
sorted
(Optional) Displays CPU utilization sorted by percentage.
Command Modes
Privileged EXEC
Command History
12.0
This command was introduced.
12.2(2)T
The history keyword was added.
12.3(8)T
This command was enhanced to display Address Resolution Protocol (ARP) output.
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 cpuCPU utilization for five seconds: 5%/2%; one minute: 3%; five minutes: 2%PID Runtime (ms) Invoked uSecs 5Sec 1Min 5Min TTY Process1 1736 58 29931 0% 0% 0% 0 Check heaps2 68 585 116 1.00% 1.00% 0% 0 IP Input3 0 744 0 0% 0% 0% 0 TCP Timer4 0 2 0 0% 0% 0% 0 TCP Protocols5 0 1 0 0% 0% 0% 0 BOOTP Server6 16 130 123 0% 0% 0% 0 ARP Input7 0 1 0 0% 0% 0% 0 Probe Input8 0 7 0 0% 0% 0% 0 MOP Protocols9 0 2 0 0% 0% 0% 0 Timers10 692 64 10812 0% 0% 0% 0 Net Background11 0 5 0 0% 0% 0% 0 Logger12 0 38 0 0% 0% 0% 0 BGP Open13 0 1 0 0% 0% 0% 0 Net Input14 540 3466 155 0% 0% 0% 0 TTY Background15 0 1 0 0% 0% 0% 0 BGP I/O16 5100 1367 3730 0% 0% 0% 0 IGRP Router17 88 4232 20 0.20% 1.00% 0% 0 BGP Router18 152 14650 10 0% 0% 0% 0 BGP Scanner19 224 99 2262 0% 0% 1.00% 0 ExecThe 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 omitted6665776865756676676666667667677676766666766767767666566667 63780161989935137097719914437323586899327408582696439226131009080 * * * * * * * *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 5CPU% per minute (last 60 minutes)* = maximum CPU% # = average CPU%!--- 72-hour output omittedThe 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 ARP17 38140 389690 97 0.00% 0.00% 0.00% 0 ARP Input36 0 1 0 0.00% 0.00% 0.00% 0 IP ARP Probe40 0 1 0 0.00% 0.00% 0.00% 0 ATM ARP INPUT80 0 1 0 0.00% 0.00% 0.00% 0 RARP Input114 0 1 0 0.00% 0.00% 0.00% 0 FR ARPTable 93 describes the fields shown in the output.
Note
Related Commands
show processes memory
Displays the amount of system memory used per system process.
show processes memory
To show memory used, use the show processes memory command in EXEC mode.
show processes memory [pid | sorted]
Syntax Description
pid
(Optional) Process ID number of a specific process. This keyword shows detail for only the specified process.
sorted
(Optional) Displays CPU history sorted by percentage of utilization.
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the show processes memory command:
Router# show processes memoryTotal: 5611448, Used: 2307548, Free: 3303900PID TTY Allocated Freed Holding Getbufs Retbufs Process0 0 199592 1236 1907220 0 0 *Init*0 0 400 76928 400 0 0 *Sched*0 0 5431176 3340052 140760 349780 0 *Dead*1 0 256 256 1724 0 0 Load Meter2 0 264 0 5032 0 0 Exec3 0 0 0 2724 0 0 Check heaps4 0 97932 0 2852 32760 0 Pool Manager5 0 256 256 2724 0 0 Timers6 0 92 0 2816 0 0 CXBus hot stall7 0 0 0 2724 0 0 IPC Zone Manager8 0 0 0 2724 0 0 IPC Realm Manager9 0 0 0 2724 0 0 IPC Seat Manager10 0 892 476 3256 0 0 ARP Input11 0 92 0 2816 0 0 SERIAL A'detect12 0 216 0 2940 0 0 Microcode Loader13 0 0 0 2724 0 0 RFSS watchdog14 0 15659136 15658584 3276 0 0 Env Mon...77 0 116 0 2844 0 0 IPX-EIGRP Hello2307224 TotalTable 94 describes the significant fields shown in the display.
The following is sample output from the show process memory command when a PID is specified:
Router# show process memory 1Proc Memory Summary for pid = 1Holding = 6844pc = 0x6049B900, size = 000006044, count = 0001pc = 0x60480650, size = 000000612, count = 0001pc = 0x6048254C, size = 000000188, count = 0001Router#Related Commands
show memory
Displays statistics about memory, including memory-free pool statistics.
show processes
Displays information about the active processes.
show protocols
To display configured Level 3 protocols, use the show protocols command in EXEC mode.
show protocols
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Usage Guidelines
This command shows the global and interface-specific status of any configured Level 3 protocol; for example, IP, DECnet, IPX, AppleTalk, and so on.
Examples
The following is sample output from the show protocols command:
Router# show protocolsGlobal values:Internet Protocol routing is enabledDECNET routing is enabledXNS routing is enabledAppletalk routing is enabledX.25 routing is enabledEthernet 0 is up, line protocol is upInternet address is 192.168.1.1, subnet mask is 255.255.255.0Decnet cost is 5XNS address is 2001.AA00.0400.06CCAppleTalk address is 4.129, zone TwilightSerial 0 is up, line protocol is upInternet address is 192.168.7.49, subnet mask is 255.255.255.240Ethernet 1 is up, line protocol is upInternet address is 192.168.2.1, subnet mask is 255.255.255.0Decnet cost is 5XNS address is 2002.AA00.0400.06CCAppleTalk address is 254.132, zone TwilightSerial 1 is down, line protocol is downInternet address is 192.168.7.177, subnet mask is 255.255.255.240AppleTalk address is 999.1, zone Magnolia EstatesFor more information on the parameters or protocols shown in this sample output, see the Cisco IOS Network Protocols Configuration Guide.
show stacks
To monitor the stack usage of processes and interrupt routines, use the show stacks command in EXEC mode.
show stacks
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Usage Guidelines
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.
Examples
The following is sample output from the show stacks command following a system failure:
Router# show stacksMinimum process stacks:Free/Size Name652/1000 Router Init726/1000 Init744/1000 BGP Open686/1200 Virtual ExecInterrupt level stacks:Level Called Free/Size Name1 0 1000/1000 env-flash3 738 900/1000 Multiport Communications Interfaces5 178 970/1000 Console UARTSystem was restarted by bus error at PC 0xAD1F4, address 0xD0D0D1AGS Software (GS3), Version 9.1(0.16), BETA TEST SOFTWARECompiled Tue 11-Aug-92 13:27 by jthomasStack trace from system failure:FP: 0x29C158, RA: 0xACFD4FP: 0x29C184, RA: 0xAD20CFP: 0x29C1B0, RA: 0xACFD4FP: 0x29C1DC, RA: 0xAD304FP: 0x29C1F8, RA: 0xAF774FP: 0x29C214, RA: 0xAF83EFP: 0x29C228, RA: 0x3E0CAFP: 0x29C244, RA: 0x3BD3CRelated Commands
show subsys
To display the subsystem information, use the show subsys command in privileged EXEC mode.
show subsys [class class | name name]
Syntax Description
Command Modes
Privileged EXEC
Command History
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 subsysClass Versionstatic_map Kernel 1.000.001arp Kernel 1.000.001ether Kernel 1.000.001compress Kernel 1.000.001alignment Kernel 1.000.002monvar Kernel 1.000.001slot Kernel 1.000.001oir Kernel 1.000.001atm Kernel 1.000.001ip_addrpool_sys Library 1.000.001chat Library 1.000.001dialer Library 1.000.001flash_services Library 1.000.001ip_localpool_sys Library 1.000.001nvram_common Driver 1.000.001ASP Driver 1.000.001sonict Driver 1.000.001oc3suni Driver 1.000.001oc12suni Driver 1.000.001ds3suni Driver 1.000.001...Table 95 describes the significant fields shown in the display.
show tcp
To display the status of TCP connections, use the show tcp command in EXEC mode.
show tcp [line-number]
Syntax Description
line-number
(Optional) Absolute line number of the line for which you want to display Telnet connection status.
Command Modes
EXEC
Command History
Examples
The following is sample output from the show tcp command:
Router# show tcptty0, connection 1 to host ciderConnection state is ESTAB, I/O status: 1, unread input bytes: 0Local host: 172.31.232.17, Local port: 11184Foreign host: 172.31.1.137, Foreign port: 23Enqueued packets for retransmit: 0, input: 0, saved: 0Event Timers (current time is 67341276):Timer: Retrans TimeWait AckHold SendWnd KeepAlive GiveUp PmtuAgerStarts: 30 0 32 0 0 0 0Wakeups: 1 0 14 0 0 0 0Next: 0 0 0 0 0 0 0iss: 67317172 snduna: 67317228 sndnxt: 67317228 sndwnd: 4096irs: 1064896000 rcvnxt: 1064897597 rcvwnd: 2144 delrcvwnd: 0SRTT: 317 ms, RTTO: 900 ms, RTV: 133 ms, KRTT: 0 msminRTT: 4 ms, maxRTT: 300 ms, ACK hold: 300 msFlags: higher precedence, idle user, retransmission timeoutDatagrams (max data segment is 536 bytes):Rcvd: 41 (out of order: 0), with data: 34, total data bytes: 1596Sent: 57 (retransmit: 1), with data: 35, total data bytes: 55Table 96 describes the first five lines of output shown in the display.
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: Retrans TimeWait AckHold SendWnd KeepAlive GiveUp PmtuAgerStarts: 30 0 32 0 0 0 0Wakeups: 1 0 14 0 0 0 0Next: 0 0 0 0 0 0 0Table 97 describes the fields in the preceding lines of output.
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 98 describes the significant fields shown in the display.
iss: 67317172 snduna: 67317228 sndnxt: 67317228 sndwnd: 4096irs: 1064896000 rcvnxt: 1064897597 rcvwnd: 2144 delrcvwnd: 0
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 99 describes the significant fields shown in the display.
SRTT: 317 ms, RTTO: 900 ms, RTV: 133 ms, KRTT: 0 msminRTT: 4 ms, maxRTT: 300 ms, ACK hold: 300 msFlags: higher precedence, idle user, retransmission timeout
For more information on these fields, refer to Round Trip Time Estimation, P. Karn & C. Partridge, ACM SIGCOMM-87, August 1987.
Table 100 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: 1596Sent: 57 (retransmit: 1), with data: 35, total data bytes: 55
Related Commands
show tcp brief
To display a concise description of TCP connection endpoints, use the show tcp brief command in EXEC mode.
show tcp brief [all]
Syntax Description
all
(Optional) Displays status for all endpoints. Without this keyword, endpoints in the LISTEN state are not shown.
Command Modes
EXEC
Command History
Examples
The following is sample output from the show tcp brief command while a user has connected into the system via Telnet:
Router> show tcp briefTCB Local Address Foreign Address (state)609789AC Router.cisco.com.23 cider.cisco.com.3733 ESTABTable 101 describes the significant fields shown in the display.
Related Commands
show tdm connections
To display a snapshot of the time-division multiplexing (TDM) bus connection memory in a Cisco AS5200 access server, use the show tdm connections command in EXEC mode.
show tdm connections [motherboard | slot slot-number]
Syntax Description
motherboard
(Optional) Motherboard in the Cisco AS5200 access server.
slot slot-number
(Optional) Slot number.
Command Modes
EXEC
Command History
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 motherboardMT8980 motherboard unit 0, Control Register = 0x1F, ODE Register = 0x06Connection Memory for ST6:Ch0: 0x62, Ch1: 0x00, Ch2: 0x00, Ch3: 0x00Ch4: 0x00, Ch5: 0x00, Ch6: 0x00, Ch7: 0x00Ch8: 0x00, Ch9: 0x00, Ch10: 0x00, Ch11: 0x00Ch12: 0x00, Ch13: 0x00, Ch14: 0x00, Ch15: 0x00Ch16: 0x00, Ch17: 0x00, Ch18: 0x00, Ch19: 0x00Ch20: 0x00, Ch21: 0x00, Ch22: 0x00, Ch23: 0x00Ch24: 0x00, Ch25: 0x00, Ch26: 0x00, Ch27: 0x00Ch28: 0x00, Ch29: 0x00, Ch30: 0x00, Ch31: 0x00To 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
show tdm data
To display a snapshot of the time-division multiplexing (TDM) bus data memory in a Cisco AS5200 access server, use the show tdm data command in EXEC mode.
show tdm data [motherboard | slot slot-number]
Syntax Description
motherboard
(Optional) Motherboard in the Cisco AS5200 access server.
slot slot-number
(Optional) Slot number.
Command Modes
EXEC
Command History
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 motherboardMT8980 motherboard unit 0, Control Register = 0x1F, ODE Register = 0x06Data Memory for ST0:Ch0: 0x7E, Ch1: 0x7E, Ch2: 0x7E, Ch3: 0x7ECh4: 0x7E, Ch5: 0x7E, Ch6: 0x7E, Ch7: 0x7ECh8: 0x7E, Ch9: 0x7E, Ch10: 0x7E, Ch11: 0x7ECh12: 0x7E, Ch13: 0x7E, Ch14: 0x7E, Ch15: 0x7ECh16: 0x7E, Ch17: 0x7E, Ch18: 0x7E, Ch19: 0x7ECh20: 0x7E, Ch21: 0x7E, Ch22: 0x7E, Ch23: 0x7ECh24: 0x7E, Ch25: 0x7E, Ch26: 0x7E, Ch27: 0x7ECh28: 0x7E, Ch29: 0x7E, Ch30: 0x7E, Ch31: 0x7EData Memory for ST1:Ch0: 0x7E, Ch1: 0x7E, Ch2: 0x7E, Ch3: 0x7ECh4: 0x7E, Ch5: 0x7E, Ch6: 0x7E, Ch7: 0x7ECh8: 0x7E, Ch9: 0x7E, Ch10: 0x7E, Ch11: 0x7ECh12: 0x7E, Ch13: 0x7E, Ch14: 0x7E, Ch15: 0x7ECh16: 0x7E, Ch17: 0x7E, Ch18: 0x7E, Ch19: 0x7ECh20: 0x7E, Ch21: 0x7E, Ch22: 0x7E, Ch23: 0x7ECh24: 0x7E, Ch25: 0x7E, Ch26: 0x7E, Ch27: 0x7ECh28: 0x7E, Ch29: 0x7E, Ch30: 0x7E, Ch31: 0x7ERelated Commands
show tdm connections
Displays data about the TDM bus connection memory in a Cisco AS5200 access server.
show tech-support
To display general information about the router when reporting a problem to Cisco technical support, use the show tech-support command in privileged EXEC mode.
show tech-support [page] [password] [ipmulticast | rsvp]
Syntax Description
Defaults
Displays output without page breaks and remove passwords and other security information.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The show tech-support command displays a large amount of configuration, run-time status, and other information about the router for troubleshooting purposes. The output of this command can be provided to technical support representatives when reporting a problem.
Tip
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 command output, and 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:
Configuration Information
•
•
Run-time State Information
•
•
•
•
•
•
•
System and Memory Information
•
•
•
•
•
•
•
Voice Port Information
•
•
•
•
•
Traffic Information
•
•
•
•
Cisco Easy VPN Configuration Information
•
•
•
•
•
•
•
•
•
•
Examples
For a sample display of the output of the show tech-support command, refer to the documentation for the show commands listed.
Related Commands
show tech-support
To display general information about the router when it reports a problem, use the show tech-support command in privileged EXEC mode.
show tech-support [page] [password]
Syntax Description
Defaults
Display output without page breaks and remove passwords and other security information.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
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:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
For a sample display of the output of the show tech-support command, refer to the documentation for the show commands listed.
Related Commands
test flash
To test Flash memory on MCI and envm Flash EPROM interfaces, use the test flash command in EXEC mode.
test flash
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Examples
In the following example, the Flash memory is tested:
test flashRelated Commands
test interfaces
Tests the system interfaces on the modular router.
test memory
Performs a test of Multibus memory (including nonvolatile memory) on the modular router.
test interfaces
To test the system interfaces on the modular router, use the test interfaces command in EXEC mode.
test interfaces
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
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
In the following example, the system interfaces are tested:
test interfacesRelated Commands
test flash
Tests Flash memory on MCI and envm Flash EPROM interfaces.
test memory
Performs a test of Multibus memory (including nonvolatile memory) on the modular router.
test memory
To perform a test of Multibus memory (including nonvolatile memory) on the modular router, use the test memory command in EXEC mode. The memory test overwrites memory.
test memory
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Usage Guidelines
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.
Examples
In the following example, the memory is tested:
test memoryRelated Commands
test flash
Tests Flash memory on MCI and envm Flash EPROM interfaces.
test interfaces
Tests the system interfaces on the modular router.
trace (privileged)
To discover the routes that packets will actually take when traveling to their destination, use the trace command in privileged EXEC mode.
trace [protocol] [destination]
Syntax Description
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
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.
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.milType 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 msec2 BARRNET-GW.CISCO.COM (192.180.16.2) 8 msec 8 msec 8 msec3 EXTERNAL-A-GATEWAY.STANFORD.EDU (192.42.110.225) 8 msec 4 msec 4 msec4 BB2.SU.BARRNET.NET (192.200.254.6) 8 msec 8 msec 8 msec5 SU.ARC.BARRNET.NET (192.200.3.8) 12 msec 12 msec 8 msec6 MOFFETT-FLD-MB.in.MIL (192.52.195.1) 216 msec 120 msec 132 msec7 ABA.NYC.mil (26.0.0.73) 412 msec 628 msec 664 msecTable 102 describes the significant fields shown in the display.
Extended IP Trace Dialog
The following display shows a sample trace session involving the extended dialog of the trace command:
Router# traceProtocol [ip]:Target IP address: mit.eduSource 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 msec2 ICM-FIX-E-H0-T3.ICP.NET (192.157.65.122) 80 msec 128 msec 80 msec3 192.203.229.246 540 msec 88 msec 84 msec4 T3-2.WASHINGTON-DC-CNSS58.T3.ANS.NET (140.222.58.3) 84 msec 116 msec 88 msec5 T3-3.WASHINGTON-DC-CNSS56.T3.ANS.NET (140.222.56.4) 80 msec 132 msec 88 msec6 T3-0.NEW-YORK-CNSS32.T3.ANS.NET (140.222.32.1) 92 msec 132 msec 88 msec7 T3-0.HARTFORD-CNSS48.T3.ANS.NET (140.222.48.1) 88 msec 88 msec 88 msec8 T3-0.HARTFORD-CNSS49.T3.ANS.NET (140.222.49.1) 96 msec 104 msec 96 msec9 T3-0.ENSS134.T3.ANS.NET (140.222.134.1) 92 msec 128 msec 92 msec10 W91-CISCO-EXTERNAL-FDDI.MIT.EDU (192.233.33.1) 92 msec 92 msec 112 msec11 E40-RTR-FDDI.MIT.EDU (18.168.0.2) 92 msec 120 msec 96 msec12 MIT.EDU (18.72.2.1) 96 msec 92 msec 96 msecTable 103 describes the fields that are unique to the extended trace sequence, as shown in the display.
Table 104describes the characters that can appear in trace command output.
Related Commands
trace (user)
Discovers the CLNS routes that packets will actually take when traveling to their destination.
trace (user)
To discover the IP routes that packets will actually take when traveling to their destination, use the trace command in EXEC mode.
trace [protocol] [destination]
Syntax Description
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
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, 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.
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.milType 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 msec2 BARRNET-GW.CISCO.COM (192.180.16.2) 8 msec 8 msec 8 msec3 EXTERNAL-A-GATEWAY.STANFORD.EDU (192.42.110.225) 8 msec 4 msec 4 msec4 BB2.SU.BARRNET.NET (192.200.254.6) 8 msec 8 msec 8 msec5 SU.ARC.BARRNET.NET (192.200.3.8) 12 msec 12 msec 8 msec6 MOFFETT-FLD-MB.in.MIL (192.52.195.1) 216 msec 120 msec 132 msec7 ABA.NYC.mil (26.0.0.73) 412 msec 628 msec 664 msecTable 105 describes the significant fields shown in the display.
Table 106 describes the characters that can appear in trace output.
Related Commands
trace (privileged)
Probes the routes that packets follow when traveling to their destination from the router.
