![Troubleshooting and Fault Management Commands [12.2]](http://www.cisco.com/swa/i/icon_pdf.gif){kind=icon}
Feedback
Table Of Contents
Troubleshooting and Fault Management Commands
show controllers (line card image)
show memory allocating-process
show memory statistics history table
Troubleshooting and Fault Management Commands
Cisco IOS Release 12.2
This chapter describes the commands used to troubleshoot a routing device. To troubleshoot, you need to discover, isolate, and resolve the system problems. You can discover problems with the system monitoring commands, isolate problems with the system test commands (including debug commands), and resolve problems by reconfiguring your system with the suite of Cisco IOS software commands.
This chapter describes general fault management commands. For detailed troubleshooting procedures and a variety of scenarios, see the Cisco IOS Internetwork Troubleshooting Guide publication. For complete details on all debug commands, see the Cisco IOS Debug Command Reference.
For troubleshooting tasks and examples, refer to the "Troubleshooting and Fault Management" chapter in the Release 12.2 Cisco IOS Configuration Fundamentals Configuration Guide.
For documentation of commands in Cisco IOS Release 12.2T or 12.3 mainline, see the Cisco IOS Configuration Fundamentals and Network Management Command Reference, Release 12.3.
attach
To connect to a specific line card for the purpose of executing monitoring and maintenance commands on that line card only, use the attach privileged EXEC command. To exit from the Cisco IOS software image on the line card and return to the Cisco IOS image on the GRP card, use the exit command.
attach slot-number
Syntax Description
Defaults
None
Command Modes
Privileged EXEC
Command History
11.2 GS
This command was added to support the Cisco 12000 series Gigabit Switch Routers.
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
Do not execute the config EXEC command from the Cisco IOS software image on the line card.
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 privileged EXEC command.
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).
diag
To perform field diagnostics on a line card, on the Gigabit Route Processor (GRP), on the Switch Fabric Cards (SFCs), and on the Clock Scheduler Card (CSC) in Cisco 12000 series Gigabit Switch Routers (GSRs), use the diag privileged EXEC command. To disable field diagnostics on a line card, use the no form of this command.
diag slot-number [halt | previous | post | verbose [wait] | wait]
no diag slot-number
Syntax Description
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 global configuration command. To return to the default core filename, use the no form of this command.
exception core-file file-name
no exception core-file
Syntax Description
Defaults
The core file is named hostname-core, where hostname is the name of the router.
Command Modes
Global configuration (config)
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, 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 dump
To configure the router to dump a core file to a particular server when the router crashes, use the exception dump global configuration command. To disable core dumps, use the no form of this command.
exception dump ip-address
no exception dump
Syntax Description
Defaults
Disabled
Command Modes
Global configuration (config)
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 global configuration command. To disable the storing of crash information for the line card, use the no form of this command.
exception linecard {all | slot slot-number} [corefile filename | main-memory size [k | m] | queue-ram size [k | m] | rx-buffer size [k | m] | sqe-register-rx | sqe-register-tx | tx-buffer size [k | m]]
no exception linecard
Syntax Description
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 (config)
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.
12000(config)# exception linecard slot 8exception memory
To cause the router to create a core dump and reboot when certain memory size parameters are violated, use the exception memory global configuration command. To disable the rebooting and core dump, use the no form of this command.
exception memory {fragment size | minimum size}
no exception memory {fragment | minimum}
Syntax Description
fragment size
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 (config)
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 global configuration command. To configure the router to use the default protocol, use the no form of this command.
exception protocol {ftp | rcp | tftp}
no exception protocol
Syntax Description
ftp
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 (config)
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 global configuration command. To use the default region size, use the no form of this command.
exception region-size size
no exception region-size
Syntax Description
Defaults
16,384 bytes
Command Modes
Global configuration (config)
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 global configuration command. To disable the core dump and reload, use the no form of this command.
exception spurious-interrupt [number]
no exception spurious-interrupt
Syntax Description
number
(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 (config)
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 privileged EXEC command.
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
To log messages to a syslog server host, use the logging global configuration command. To delete the syslog server with the specified address from the list of syslogs, use the no form of this command.
logging host-name
no logging host-name
Syntax Description
Defaults
No messages are logged to a syslog server host.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
This command identifies a syslog server host to receive logging messages. By issuing this command more than once, you build a list of syslog servers that receive logging messages.
Examples
In the following example, messages are logged to a host named john:
logging johnRelated Commands
logging buffered
To limit messages logged to an internal buffer based on severity, use the logging buffered global configuration command. To cancel the use of the buffer, use the no form of this command. The default form of this command returns the buffer size to the default size.
logging buffered [buffer-size | level]
no logging buffered
default logging buffered
Syntax Description
buffer-size
(Optional) Size of the buffer from 4096 to 4,294,967,295 bytes. The default size varies by platform.
level
(Optional) Limits the logging of messages to the buffer to a specified level. You can enter the level name or level number. See Table 55 for a list of the accepatable level name or level number keywords.
Defaults
For most platforms, the Cisco IOS software logs messages to the internal buffer.
Command Modes
Global configuration (config)
Command History
10.0
This command was introduced.
11.1(17)T
The command syntax was changed to include the level argument.
Usage Guidelines
This command copies logging messages to an internal buffer. The buffer is circular in nature, so newer messages overwrite older messages after the buffer is filled.
Specifying a level causes messages at that level and numerically lower levels to be logged in an internal buffer. See Table 55 for a list of level arguments.
Do not make the buffer size too large because the router could run out of memory for other tasks. You can use the show memory EXEC command to view the free processor memory on the router; however, this is the maximum available and should not be approached. The default logging buffered command resets the buffer size to the default for the platform.
To display the messages that are logged in the buffer, use the show logging EXEC command. The first message displayed is the oldest message in the buffer.
The show logging EXEC command displays the addresses and levels associated with the current logging setup, and any other logging statistics.
Examples
In the following example, the user enables logging to an internal buffer:
logging bufferedRelated Commands
clear logging
Clears messages from the logging buffer.
show logging
Displays the state of logging (syslog).
logging console
To limit messages logged to the console based on severity, use the logging console global configuration command. To disable logging to the console terminal, use the no form of this command.
logging console level
no logging console
Syntax Description
level
Limits the logging of messages displayed on the console terminal to a specified level. You can enter the level number or level name. See Table 56 for a list of the level arguments.
Defaults
debugging
Command Modes
Global configuration (config)
Command History
Usage Guidelines
Specifying a level causes messages at that level and numerically lower levels to be displayed at the console terminal.
The show logging EXEC command displays the addresses and levels associated with the current logging setup, and any other logging statistics. See Table 56.
The effect of the log keyword with the IP access list (extended) interface configuration command depends on the setting of the logging console command. The log keyword takes effect only if the logging console level is set to 6 or 7. If you change the default to a level lower than 6 and specify the log keyword with the IP access list (extended) command, no information is logged or displayed.
Examples
In the following example, the user changes the level of messages displayed to the console terminal to alerts, which means alerts and emergencies are displayed:
logging console alertsRelated Commands
access-list (extended)
Defines an extended XNS access list.
logging facility
Configures the syslog facility in which system messages are sent.
logging facility
To configure the syslog facility in which system messages are sent, use the logging facility global configuration command. To revert to the default of local7, use the no form of this command.
logging facility facility-type
no logging facility
Syntax Description
facility-type
Syslog facility. See the Usage Guidelines section of this command reference entry for descriptions of acceptable keywords.
Defaults
local7
Command Modes
Global configuration (config)
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 the Simple Network Management Protocol (SNMP) network management station based on severity, use the logging history global configuration command. To return the logging of syslog messages to the default level, use the no form of this command with the previously configured severity level argument.
logging history [severity-level-name | severity-level-number]
no logging history [severity-level-name | severity-level-number]
Syntax Description
Defaults
Logging of system messages of severity levels 0 through 4 (emergency, alert, critical, error, and warning levels); in other words, "saving level warnings or higher"
Command Modes
Global configuration (config)
Command History
Usage Guidelines
Sending syslog messages to the SNMP network management station occurs when you enable syslog traps with the snmp-server enable traps global configuration command. Because SNMP traps are inherently unreliable and much too important to lose, at least one syslog message, the most recent message, is stored in a history table on the router. The history table, which contains table size, message status, and message text data, can be viewed using the show logging history command. The number of messages stored in the table is governed by the logging history size EXEC command.
Severity levels are numbered 0 through 7, with 0 being the highest severity level and 7 being the lowest severity level (that is, the lower the number, the more critical the message). Specifying a level causes messages at that severity level and numerically lower levels to be stored in the 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) levles to be saved to the logging history table.
Table 58 provides a description of logging severity levels, listed from higest severity to lowest severity, and the arguments used inthe logging history command syntax. Note that you can use the level name or the level number as the level argument in this command.
Examples
In the following example, the system is initially configured to the default of saving severity level 4 or higher. The logging history1 command is used to configure the system to save only level 1 (alert) and level 0 (emergency) messages to the logging history table. The configuration is then confirmed using the show logging history command.
Router#show logging 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)#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' is configured.saving level alerts or higher18 messages ignored, 0 dropped, 0 recursion drops1 table entries flushedSNMP notifications not enabledentry 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 global configuration command. 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 (config)
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 linecard
To log messages to an internal buffer on a line card, use the logging linecard global configuration command. To cancel the use of the internal buffer on the line cards, use the no form of this command.
logging linecard [size | level]
no logging linecard
Syntax Description
Defaults
The Cisco IOS software logs messages to the internal buffer on the GRP card.
Command Modes
Global configuration (config)
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:
(config)# logging linecard warningsRelated Commands
Clears messages from the logging buffer.
Displays the state of logging (syslog).
logging monitor
To limit messages logged to the terminal lines (monitors) based on severity, use the logging monitor global configuration command. This command limits the logging messages displayed on terminal lines other than the console line to messages with a level at or above the level argument. To disable logging to terminal lines other than the console line, use the no form of this command.
logging monitor severity-level
no logging monitor
Syntax Description
Defaults
debugging (severity-level 7)
Command Modes
Global configuration (config)
Command History
Usage Guidelines
Specifying a level causes messages at that level and numerically lower levels to be displayed to the monitor.
Examples
In the following example, the user specifies that only messages of the levels errors, critical, alerts, and emergencies be displayed on terminals:
logging monitor 3Related Commands
terminal monitor
Enables the display of system messages to the terminal connection.
logging on
To control logging of system messages (including error messages or debugging messages), use the logging on global configuration command. This command sends system messages to a logging process, which logs messages to designated locations asynchronously to the processes that generated the messages. To disable the logging process, use the no form of this command.
logging on
no logging on
Syntax Description
This command has no arguments or keywords.
Defaults
The Cisco IOS software sends messages to the asynchronous logging process.
Command Modes
Global configuration (config)
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. 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 number | console {number | all number}} [except severity]
no logging rate-limit
Syntax Description
Command Default
The default for this command is 10 messages logged per second and exclusion of messages of the errors level or lower.
Command Modes
Global configuration
Command History
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 (lower than 2) to only 10 per second.
Table 61 compares the error message logging numeric severity level with its equivalent word description.
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
logging source-interface
To specify the source IP address of syslog packets, use the logging source-interface global configuration command. To remove the source designation, use the no form of this command.
logging source-interface interface-type interface-number
no logging source-interface
Syntax Description
Defaults
No interface is specified.
Command Modes
Global configuration (config)
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 line configuration command. To disable synchronization of unsolicited messages and debug output, use the no form of this command.
logging synchronous [level severity-level | all] [limit number-of-buffers]
no logging synchronous [level severity-level | all] [limit number-of-buffers]
Syntax Description
Defaults
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 4 logging 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 global configuration command. The command limits the logging of system messages sent to syslog servers to only those messages at the specified level. To disable logging to syslog servers, use the no form of this command.
logging trap level
no logging trap
Syntax Description
Defaults
informational (level 6)
Command Modes
Global configuration (config)
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 (privileged)
To diagnose basic network connectivity on Apollo, AppleTalk, Connectionless Network Service (CLNS), DECnet, IP, Novell IPX, VINES, or XNS networks, use the ping privileged EXEC command.
ping [protocol | tag] {host-name | system-address} [data [hex-data-pattern] | df-bit | repeat [repeat-count] | size [datagram-size] | source [source-address | async | bvi | ctunnel | dialer | ethernet | fastEthernet | lex | loopback | multilink | null | port-channel | tunnel | vif | virtual-template | virtual-tokenring | xtagatm] | timeout [seconds] | validate]
Syntax Description
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 (packet internet groper) command sends ISO CLNS echo packets to test the reachability of a remote router over a connectionless Open System Interconnection (OSI) network.
The ping command sends an echo request packet to an address, then awaits a reply. Ping output can help you evaluate path-to-host reliability, delays over the path, and whether the host can be reached or is functioning.
To abnormally terminate a ping session, type the escape 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 63 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 64 describes the default ping fields shown in the display.
Related Commands
ping (user)
Tests the connection to a remote host on the network.
ping vrf
Tests the connection to a remote device in a VPN.
ping (user)
To diagnose basic network connectivity on AppleTalk, Connection Network Service (CLNS), IP, Novell, Apollo, VINES, DECnet, or XNS networks, use the ping (packet internet groper) user EXEC command.
ping [protocol] {host-name | system-address}
Syntax Description
protocol
(Optional) Protocol keyword, one of apollo, appletalk, clns, decnet, ip, ipx, vines, or xns.
host-name
Host name of the system to ping.
system-address
Address of the system to ping.
Command Modes
EXEC
Command History
Usage Guidelines
The user-level ping feature provides a basic ping facility for users that do not have system privileges. This feature allows the Cisco IOS software to perform the simple default ping functionality for a number of protocols. Only the terse form of the ping command is supported for user-level pings.
If the system cannot map an address for a host name, it returns an "%Unrecognized host or address" error message.
To abnormally terminate a ping session, type the escape 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.
Examples
The following display shows sample ping output when you ping the IP host named donald:
Router> ping donaldType 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/3/4 msRelated Commands
service slave-log
To allow slave Versatile Interface Processor (VIP) cards to log important system messages to the console, use the service slave-log global configuration command. To disable slave logging, use the no form of this command.
service slave-log
no service slave-log
Syntax Description
This command has no arguments or keywords.
Defaults
This command is enabled by default.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
This command allows slave slots to log system messages of level 2 or higher (critical, alerts, and emergencies).
Examples
In the following example, important messages from the slave cards to the console are logged:
service slave-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 system 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 global configuration command. To disable the keepalives, use the no form of this command.
service tcp-keepalives-in
no service tcp-keepalives-in
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Global configuration (config)
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 global configuration command. To disable the keepalives, use the no form of this command.
service tcp-keepalives-out
no service tcp-keepalives-out
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Global configuration (config)
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 logging messages, use one of the service timestamps global configuration commands. To disable this service, use the no form of this command.
service timestamps [debug | log] [ uptime | datetime [msec] [localtime] [show-timezone] ]
no service timestamps [debug | log]
Syntax Description
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.
Command Modes
Global configuration (config)
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. If the system clock has not been set, the date and time are preceded by an asterisk (*) to indicate that the date and time are probably not correct.
Examples
In the following example, the user enables time stamps on debugging messages, showing the time since reboot:
service timestamps debug 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:
service timestamps log datetime localtime show-timezoneRelated Commands
clock set
Manually sets the system clock.
ntp
Controls access to the system's NTP services.
show c2600 (2600)
To display information for troubleshooting the Cisco 2600 series router, use the show c2600 EXEC command.
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 66 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 EXEC command.
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 EXEC command.
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.
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.
show context (2600)
To display information stored in NVRAM when an exception occurs, use the show context EXEC command.
show context
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Usage Guidelines
Context information is specific to processors and architectures, whereas software version and uptime information is not specific to architectures. Context information for the Cisco 2600 series router differs from that for other router types because the Cisco 2600 runs with an M860 processor. The display from the show context command includes the following information:
•
•
•
•
•
This information is useful only to your technical support representative for analyzing crashes in the field. Use this information when you read the displayed statistics to an engineer over the phone.
Examples
The following is sample output from the show context command following a system failure on a Cisco 2600 series router. See Table 67 for a description of the fields in this output.
router# show 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 context
To display information stored in NVRAM when the router crashes, use the show context EXEC command.
show context summary
show context {all | slot slot-number [crash-index] [all] [debug]}
Syntax Description
Command Modes
EXEC
Command History
11.2 GS
This command was modified to add the all, debug, slot, and summary keywords.
Usage Guidelines
The display from the show context command includes the following information:
•
•
•
•
•
Note
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.
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#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 privileged EXEC command.
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 privileged EXEC command to connect to the line card and then use the show controllers privileged EXEC command or the execute-on privileged EXEC command.
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 command is intended for use by Cisco technical support.
Note
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 privileged EXEC command.
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 68 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 privileged EXEC command.
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 privileged EXEC command.
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 diag
To display hardware information including DRAM and static RAM (SRAM) on line cards, use the show diag command in privileged EXEC mode.
show diag [slot-number] [details] [summary]
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command to determine the type of hardware installed in your router. This command applies line cards in Cisco Universal Access Servers; Cisco 1750, 7200, and 7500 series routers; and Cisco 12000 series GSRs.
Note
Examples of output showing the FRU number are included in the Examples section.
Cisco 7304 Router Usage Guidelines
For the Cisco 7304 router, this command applies to NSEs, line cards, MSCs, and SPAs.
•
•
Shared Port Adapter Usage Guidelines
•
•
Examples
Example for a 1-Port T3 Serial Port Adapter on the Cisco 7200 Series Router
The following is sample output from the show diag command for a 1-port T3 serial port adapter in chassis slot 1 on a Cisco 7200 series router:
Router# show diag 1Slot 1:Physical slot 1, ~physical slot 0xE, logical slot 1, CBus 0Microcode Status 0x4Master Enable, LED, WCS LoadedBoard is analyzedPending I/O Status: NoneEEPROM format version 1VIP2 controller, HW rev 2.4, board revision D0Serial number: 04372053 Part number: 73-1684-03Test history: 0x00 RMA number: 00-00-00Flags: cisco 7000 board; 7500 compatibleEEPROM contents (hex):0x20: 01 15 02 04 00 42 B6 55 49 06 94 03 00 00 00 000x30: 68 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00Slot database information:Flags: 0x4 Insertion time: 0x14A8 (5d02h ago)Controller Memory Size: 16 MBytes DRAM, 1024 KBytes SRAMPA Bay 0 Information:T3 Serial PA, 1 portsEEPROM format version 1HW rev FF.FF, Board revision UNKNOWNSerial number: 4294967295 Part number: 255-65535-255Example Output from a Cisco 7200 Showing the FRU Number
The following is sample output from the show diag command on a Cisco 7200 series router showing the FRU number:
Router# show diagSlot 0:Dual FastEthernet (RJ-45) I/O Card Port adapter, 2 portsPort adapter is analyzedPort adapter insertion time 6d02h agoEEPROM contents at hardware discovery:Hardware Revision : 2.1Top Assy. Part Number : 800-07114-06Part Number : 73-5003-06Board Revision : B0PCB Serial Number : 31558694RMA History : 00Fab Version : 03Fab Part Number : 28-3455-03Product (FRU) Number : C7200-I/O-2FE/EDeviation Number : 0-0EEPROM format version 4EEPROM contents (hex):0x00: 04 FF 40 02 15 41 02 01 C0 46 03 20 00 1B CA 060x10: 82 49 13 8B 06 42 42 30 C1 8B 33 31 35 35 38 360x20: 39 34 00 00 00 04 00 02 03 85 1C 0D 7F 03 CB 8F0x30: 43 37 32 30 30 2D 49 2F 4F 2D 32 46 45 2F 45 800x40: 00 00 00 00 FF FF FF FF FF FF FF FF FF FF FF FF0x50: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF0x60: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF0x70: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FFRouter#Examples for a Cisco 12000 Series Internet Router
The following is sample output from the show diag command on a Cisco 12000 series Internet router:
Router# show diag 3SLOT 3 (RP/LC 3 ): 4 Port Packet Over SONET OC-3c/STM-1 Multi ModeMAIN: type 33, 00-0000-00 rev 70 dev 0HW config: 0x01 SW key: 00-00-00PCA: 73-2147-02 rev 94 ver 2HW version 1.0 S/N 04499695MBUS: MBUS Agent (1) 73-2146-05 rev 73 dev 0HW version 1.1 S/N 04494882Test hist: 0x00 RMA#: 00-00-00 RMA hist: 0x00DIAG: Test count: 0x05000001 Test results: 0x00000000MBUS Agent Software version 01.27 (RAM) using CAN Bus AROM Monitor version 00.0DFabric Downloader version used 00.0D (ROM version is 00.0D)Board is analyzedBoard State is Line Card Enabled (IOS RUN )Insertion time: 00:00:10 (00:04:51 ago)DRAM size: 33554432 bytesFrFab SDRAM size: 67108864 bytesToFab SDRAM size: 16777216 bytesThe following is sample output from the show diag command with the summary keyword:
Router# show diag summarySLOT 0 (RP/LC 0 ): Route ProcessorSLOT 2 (RP/LC 2 ): 4 Port Packet Over SONET OC-3c/STM-1 Single ModeSLOT 4 (RP/LC 4 ): 4 Port Packet Over SONET OC-3c/STM-1 Single ModeSLOT 7 (RP/LC 7 ): 4 Port Packet Over SONET OC-3c/STM-1 Single ModeSLOT 9 (RP/LC 9 ): 4 Port Packet Over SONET OC-3c/STM-1 Single ModeSLOT 11 (RP/LC 11): 4 Port Packet Over SONET OC-3c/STM-1 Single ModeSLOT 16 (CSC 0 ): Clock Scheduler CardSLOT 17 (CSC 1 ): Clock Scheduler CardSLOT 18 (SFC 0 ): Switch Fabric CardSLOT 19 (SFC 1 ): Switch Fabric CardSLOT 20 (SFC 2 ): Switch Fabric CardSLOT 24 (PS A1 ): AC Power SupplySLOT 26 (PS B1 ): AC Power SupplySLOT 28 (TOP FAN ): Blower ModuleSLOT 29 (BOT FAN ): Blower ModuleThe following is sample output from the show diag command with the details keyword:
Router# show diag 4 detailsSLOT 4 (RP/LC 4): 4 Port Packet Over SONET OC-3c/STM-1 Single ModeMAIN: type 33, 800-2389-01 rev 71 dev 16777215HW config: 0x00 SW key: FF-FF-FFPCA: 73-2275-03 rev 75 ver 3HW version 1.1 S/N 04529465MBUS: MBUS Agent (1) 73-2146-06 rev 73 dev 0HW version 1.1 S/N 04541395Test hist: 0xFF RMA#: FF-FF-FF RMA hist: 0xFFDIAG: Test count: 0x05000001 Test results: 0x00000000EEPROM contents (hex):00: 01 00 01 00 49 00 08 62 06 03 00 00 00 FF FF FF10: 30 34 35 34 31 33 39 35 FF FF FF FF FF FF FF FF20: 01 01 00 00 00 00 00 FF FF FF FF FF FF FF FF FF30: A5 FF A5 A5 A5 A5 FF A5 A5 A5 A5 A5 A5 A5 A5 A540: 00 21 01 01 00 49 00 08 E3 03 05 03 00 01 FF FF50: 03 20 00 09 55 01 01 FF FF FF 00 FF FF FF FF FF60: 30 34 35 32 39 34 36 35 FF FF FF FF FF FF FF FF70: FF FF FF FF FF FF FF FF 05 00 00 01 00 00 00 00MBUS Agent Software version 01.24 (RAM)Fabric Downloader version 00.0DBoard is analyzedFlags: 0x4Board State is Line Card Enabled (IOS RUN)Insertion time: 00:00:10 (00:04:51 ago)DRAM size: 33554432 bytesFrFab SDRAM size: 67108864 bytesToFab SDRAM size: 16777216 bytesExample for an ATM SAR AIM in a Cisco 3660
The following is sample output from the show diag command for one ATM Segmentation and Reassembly (SAR) AIM in a Cisco 3660 router:
Router# show diag 03660 Chassis type: ENTERPRISEc3600 Backplane EEPROM:Hardware Revision : 1.0Top Assy. Part Number : 800-04740-02...ATM AIM: 1ATM AIM module with SAR only (no DSPs)Hardware Revision : 1.0Top Assy. Part Number : 800-03700-01Board Revision : A0Deviation Number : 0-0Fab Version : 02PCB Serial Number : JAB9801ABCDExample Output from a Cisco 3660 Showing the FRU Number
The following is sample output from the show diag command on a Cisco 3660 router that shows the FRU numbers for slots 0 and 1:
Router# show diag3660 Chassis type: ENTERPRISE3660 Backplane EEPROM:Hardware Revision : 1.0Top Assy. Part Number : 800-04740-02Board Revision : C0Deviation Number : 0-0Fab Version : 02PCB Serial Number : HAD04471U36RMA Test History : 00RMA Number : 0-0-0-0RMA History : 00Chassis Serial Number : JAB055180FFChassis MAC Address : 0007.ebea.4460MAC Address block size : 112Manufacturing Test Data : 00 00 00 00 00 00 00 00Fab Part Number : 28-2651-02Number of Slots : 6EEPROM format version 4EEPROM contents (hex):0x00: 04 FF 40 00 C8 41 01 00 C0 46 03 20 00 12 84 020x10: 42 43 30 80 00 00 00 00 02 02 C1 8B 48 41 44 300x20: 34 34 37 31 55 33 36 03 00 81 00 00 00 00 04 000x30: C2 8B 4A 41 42 30 35 35 31 38 30 46 46 C3 06 000x40: 07 EB EA 44 60 43 00 70 C4 08 00 00 00 00 00 000x50: 00 00 85 1C 0A 5B 02 01 06 FF FF FF FF FF FF FF0x60: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF0x70: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FFSlot 0:C3600 Mother board 2FE(TX) Port adapter, 2 portsPort adapter is analyzedPort adapter insertion time unknownEEPROM contents at hardware discovery:PCB Serial Number : JAB05460CSVProcessor type : 34Top Assy. Part Number : 800-04737-04Board Revision : C0Fab Part Number : 28-3234-02Deviation Number : 65535-65535Manufacturing Test Data : FF FF FF FF FF FF FF FFRMA Number : 255-255-255-255RMA Test History : FFRMA History : FFField Diagnostics Data : FF FF FF FF FF FF FF FFProduct (FRU) Number : Leopard-2FEEEPROM format version 4EEPROM contents (hex):0x00: 04 FF C1 8B 4A 41 42 30 35 34 36 30 43 53 56 090x10: 34 40 00 B3 C0 46 03 20 00 12 81 04 42 43 30 850x20: 1C 0C A2 02 80 FF FF FF FF C4 08 FF FF FF FF FF0x30: FF FF FF 81 FF FF FF FF 03 FF 04 FF C5 08 FF FF0x40: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF0x50: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF0x60: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF0x70: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 00Slot 1:Mueslix-4T Port adapter, 4 portsPort adapter is analyzedPort adapter insertion time unknownEEPROM contents at hardware discovery:Hardware revision 1.1 Board revision D0Serial number 17202570 Part number 800-02314-02FRU Part Number: NM-4T=Test history 0x0 RMA number 00-00-00EEPROM format version 1EEPROM contents (hex):0x00: 01 54 01 01 01 06 7D 8A 50 09 0A 02 00 00 00 000x10: 68 00 00 00 99 11 21 00 00 05 FF FF FF FF FF FFRouter#Example for an NM-AIC-64 Installed in a Cisco 2611
The following is sample output from the show diag command for a Cisco 2611 router with the NM-AIC-64 installed.
Router# show diagSlot 0: C2611 2E Mainboard Port adapter, 2 ports Port adapter is analyzed Port adapter insertion time unknown EEPROM contents at hardware discovery: Hardware Revision : 2.3 PCB Serial Number : JAD044808SG (1090473337) Part Number : 73-2840-13 RMA History : 00 RMA Number : 0-0-0-0 Board Revision : C0 Deviation Number : 0-0 EEPROM format version 4 EEPROM contents (hex): 0x00: 04 FF 40 00 92 41 02 03 C1 18 4A 41 44 30 34 34 0x10: 38 30 38 53 47 20 28 31 30 39 30 34 37 33 33 33 0x20: 37 29 82 49 0B 18 0D 04 00 81 00 00 00 00 42 43 0x30: 30 80 00 00 00 00 FF FF FF FF FF FF FF FF FF FF 0x40: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 0x50: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 0x60: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 0x70: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF Slot 1: NM_AIC_64 Port adapter, 3 ports Port adapter is analyzed Port adapter insertion time unknown EEPROM contents at hardware discovery: Hardware Revision : 1.0 Part Number : 74-1923-01 Board Revision : 02 PCB Serial Number : DAN05060012 EEPROM format version 4 EEPROM contents (hex): 0x00: 04 FF 40 02 55 41 01 00 82 4A 07 83 01 42 30 32 0x10: C1 8B 44 41 4E 30 35 30 36 30 30 31 32 FF FF FF 0x20: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 0x30: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 0x40: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 0x50: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 0x60: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 0x70: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FFTable 69 describes significant fields shown in the display.
Example for an AIM-VPN in a Cisco 2611XM
The following example shows how to obtain hardware information about an installed AIM-VPN on the Cisco 2611XM router.
Router# show diag 0
Encryption AIM 1:
Hardware Revision :1.0
Top Assy. Part Number :800-03700-01
Board Revision :A0
Deviation Number :0-0
Fab Version :02
PCB Serial Number :JAB9801ABCD
RMA Test History :00
RMA Number :0-0-0-0
RMA History :00
EEPROM format version 4
EEPROM contents (hex):
0x00:04 FF 40 03 0B 41 01 00 C0 46 03 20 00 0E 74 01
0x10:42 41 30 80 00 00 00 00 02 02 C1 8B 4A 41 42 39
0x20:38 30 31 41 42 43 44 03 00 81 00 00 00 00 04 00
0x30:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x40:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x50:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x60:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
0x70:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
Table 70 describes significant fields shown in the display.
Example for an MSC-100 on the Cisco 7304 Router
The following is sample output from the show diag slot-number version of the command for an MSC-100 located in slot number 4 on a Cisco 7304 router. Information about the MSC is followed by information for its associated SPAs:
Router# show diag 4Slot 4:7304-MSC-100 SPA Carrier Card Line CardLine Card state: ActiveInsertion time: 00:08:49 agoBandwidth points: 4000000EEPROM contents at hardware discovery:Hardware Revision : 0.18Boot Time out : 0000PCB Serial Number : CSJ07288905Part Number : 73-8789-01Board Revision : A0Fab Version : 02RMA Test History : 00RMA Number : 0-0-0-0RMA History : 00Deviation Number : 0-0Product Number : 7304-MSC-100Top Assy. Part Number : 68-1163-04Manufacturing Test Data : 00 00 00 00 00 00 00 00Field Diagnostics Data : 00 00 00 00 00 00 00 00Calibration Data : Minimum: 0 dBmV, Maximum: 0 dBmVCalibration values :EEPROM format version 4EEPROM contents (hex):0x00: 04 FF 40 04 50 41 00 12 46 00 00 C1 8B 43 53 4A0x10: 30 37 32 38 38 39 30 35 82 49 22 55 01 42 41 300x20: 02 02 03 00 81 00 00 00 00 04 00 80 00 00 00 000x30: CB 94 37 33 30 34 2D 4D 53 43 2D 31 30 30 20 200x40: 20 20 20 20 20 20 87 44 04 8B 04 C4 08 00 00 000x50: 00 00 00 00 00 C5 08 00 00 00 00 00 00 00 00 C80x60: 09 00 00 00 00 00 00 00 00 00 C7 7C F6 44 3F 300x70: 00 00 00 00 00 00 00 00 00 00 00 00 02 EE FF C80x80: C8 37 26 05 DC 64 28 1E 37 26 09 C4 64 32 28 320x90: DD 0C E4 64 32 28 43 24 2E E0 AA 82 64 F4 24 000xA0: 00 00 00 00 00 00 F0 2E FF FF FF FF FF FF FF FF0xB0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF0xC0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF0xD0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF0xE0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF0xF0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF0x100: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF0x110: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF0x120: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF0x130: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF0x140: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF0x150: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF0x160: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF0x170: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF0x180: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF0x190: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF0x1A0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF0x1B0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF0x1C0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF0x1D0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF0x1E0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF0x1F0: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FFFPGA information:Current FPGA version : 00.23IOS bundled FPGA version : 00.23CPLD version : 01.02Subslot 4/1:Shared port adapter: SPA-4FE-7304, 4 portsState: okInsertion time: 00:15:13 agoBandwidth: 400000 kbpsEEPROM contents:Examples for Shared Port Adapters on the Cisco 7304 Router
The following is sample output from the show diag subslot command for a 4-Port 10/100 Fast Ethernet SPA located in the bottom subslot (1) of the MSC that is installed in slot 4 on a Cisco 7304 router:
Router# show diag subslot 4/1Subslot 4/1:Shared port adapter: SPA-4FE-7304, 4 portsInfo: hw-ver=0x100, sw-ver=0x0 fpga-ver=0x0State: okInsertion time: 23:20:42 agoBandwidth: 400000 kbpsEEPROM contents:Hardware Revision : 1.0Boot Time out : 0190PCB Serial Number : JAB073204G5Part Number : 73-8717-0373/68 Level Revision : 01Fab Version : 02RMA Test History : 00RMA Number : 0-0-0-0RMA History : 00Deviation Number : 0Product Number : SPA-4FE-7304Product Version Id : V01Top Assy. Part Number : 68-2181-0173/68 Level Revision : A0CLEI Code : CNS9420AAABase MAC Address : 0000.0000.0000MAC Address block size : 1024Manufacturing Test Data : 00 00 00 00 00 00 00 00Field Diagnostics Data : 00 00 00 00 00 00 00 00Field Diagnostics Data : 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00Calibration Data : Minimum: 0 dBmV, Maximum: 0 dBmVCalibration values :Power Consumption : 160000mW maxMode 1 : 0mWMode 2 : 0mWMode 3 : 0mWEEPROM format version 4EEPROM contents (hex):0x00: 04 FF 40 04 35 41 01 00 46 01 90 C1 8B 4A 41 420x10: 30 37 33 32 30 34 47 35 82 49 22 0D 03 8A 30 310x20: 20 20 02 02 03 00 81 00 00 00 00 04 00 88 00 000x30: 00 00 CB 94 53 50 41 2D 34 46 45 2D 37 33 30 340x40: 20 20 20 20 20 20 20 20 89 56 30 31 20 87 44 080x50: 85 01 8A 41 30 20 20 C6 8A 43 4E 53 39 34 32 300x60: 41 41 41 CF 06 00 00 00 00 00 00 43 04 00 C4 080x70: 00 00 00 00 00 00 00 00 C5 08 00 00 00 00 00 000x80: 00 00 F4 00 64 00 00 00 00 00 00 00 00 00 00 000x90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 000xA0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 000xB0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 000xC0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 000xD0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 000xE0: 00 00 00 00 00 00 00 00 00 C8 09 00 00 00 00 000xF0: 00 00 00 00 D7 08 3E 80 00 00 00 00 00 00 F3 000x100: 41 01 08 F6 48 43 34 F6 49 44 35 02 31 04 B0 B40x110: A0 8C 00 00 05 DC 64 46 32 00 00 07 08 64 46 320x120: 00 00 09 C4 64 46 32 00 00 0C E4 64 46 32 00 000x130: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 FE 020x140: F2 A6 FF FF FF FF FF FF FF FF FF FF FF FF FF FF0x150: CC A0 00 00 00 00 00 00 00 00 00 00 00 00 00 000x160: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 000x170: 00 00 D4 A0 00 00 00 00 00 00 00 00 00 00 00 000x180: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 000x190: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 000x1A0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 000x1B0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 000x1C0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 000x1D0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 000x1E0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 000x1F0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00FPGA version:Software version : 04.17Hardware version : 04.17The following is sample output from the show diag subslot command for a 2-Port 10/100/1000 Gigabit Ethernet SPA located in the top subslot (0) of the MSC that is installed in slot 4 on a Cisco 7304 router:
Router# show diag subslot 4/0Subslot 4/0:Shared port adapter: SPA-2GE-7304, 2 portsInfo: hw-ver=0x17, sw-ver=0x0 fpga-ver=0x0State: okInsertion time: 00:08:47 agoBandwidth: 2000000 kbpsEEPROM contents:Hardware Revision : 0.23Boot Time out : 0190PCB Serial Number : JAB073406YHPart Number : 73-8792-0273/68 Level Revision : 01Fab Version : 02RMA Test History : 00RMA Number : 0-0-0-0RMA History : 00Deviation Number : 0Product Number : SPA-2GE-7304Product Version Id : V01Top Assy. Part Number : 68-2181-0173/68 Level Revision : A0CLEI Code : CNS9420AAABase MAC Address : 0000.0000.0000MAC Address block size : 1024Manufacturing Test Data : 00 00 00 00 00 00 00 00Field Diagnostics Data : 00 00 00 00 00 00 00 00Field Diagnostics Data : 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00Calibration Data : Minimum: 0 dBmV, Maximum: 0 dBmVCalibration values :Power Consumption : 160000mW maxMode 1 : 0mWMode 2 : 0mWMode 3 : 0mWEEPROM format version 4EEPROM contents (hex):0x00: 04 FF 40 04 36 41 00 17 46 01 90 C1 8B 4A 41 420x10: 30 37 33 34 30 36 59 48 82 49 22 58 02 8A 30 310x20: 20 20 02 02 03 00 81 00 00 00 00 04 00 88 00 000x30: 00 00 CB 94 53 50 41 2D 32 47 45 2D 37 33 30 340x40: 20 20 20 20 20 20 20 20 89 56 30 31 20 87 44 080x50: 85 01 8A 41 30 20 20 C6 8A 43 4E 53 39 34 32 300x60: 41 41 41 CF 06 00 00 00 00 00 00 43 04 00 C4 080x70: 00 00 00 00 00 00 00 00 C5 08 00 00 00 00 00 000x80: 00 00 F4 00 64 00 00 00 00 00 00 00 00 00 00 000x90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 000xA0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 000xB0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 000xC0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 000xD0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 000xE0: 00 00 00 00 00 00 00 00 00 C8 09 00 00 00 00 000xF0: 00 00 00 00 D7 08 3E 80 00 00 00 00 00 00 F3 000x100: 41 01 08 F6 48 43 34 F6 49 44 35 02 31 03 E8 B40x110: A0 8C 37 26 05 DC 64 46 32 37 26 07 08 64 46 320x120: 37 26 09 C4 64 46 32 32 DD 0C E4 64 46 32 43 240x130: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 FE 020x140: EF E2 FF FF FF FF FF FF FF FF FF FF FF FF FF FF0x150: CC A0 00 00 00 00 00 00 00 00 00 00 00 00 00 000x160: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 000x170: 00 00 D4 A0 00 00 00 00 00 00 00 00 00 00 00 000x180: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 000x190: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 000x1A0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 000x1B0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 000x1C0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 000x1D0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 000x1E0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 000x1F0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00FPGA version:Software version : 04.17Hardware version : 04.17Examples for a Shared Port Adapter on a Cisco 12000 Series Router
The following is sample output from the show diag subslot command for the 1-Port OC-192c/STM-64c POS/RPR XFP SPA in subslot 1 of the SIP located in chassis slot 1 on a Cisco 12000 series router:
Router# show diag subslot 1/1SUBSLOT 1/1 (SPA-OC192POS-XFP): 1-port OC192/STM64 POS/RPR XFP Optics Shared Port AdapterProduct Identifier (PID) : SPA-OC192POS-XFPVersion Identifier (VID) : V01PCB Serial Number : PRTA1304061Top Assy. Part Number : 68-2190-01Top Assy. Revision : A0Hardware Revision : 2.0CLEI Code : UNASSIGNEDInsertion Time : 00:00:10 (13:14:17 ago)Operational Status : okTable 71 describes the significant fields shown in the display.
The following is sample output from the show diag subslot details command for the 1-Port OC-192c/STM-64c POS/RPR XFP SPA in subslot 1 of the SIP located in chassis slot 1 on a Cisco 12000 series router:
Router# show diag subslot 1/1 detailsSUBSLOT 1/1 (SPA-OC192POS-XFP): 1-port OC192/STM64 POS/RPR XFP Optics Shared Port AdapterEEPROM version : 4Compatible Type : 0xFFController Type : 1100Hardware Revision : 2.0Boot Timeout : 400 msecsPCB Serial Number : PRTA1304061PCB Part Number : 73-8546-01PCB Revision : A0 Fab Version : 01RMA Test History : 00RMA Number : 0-0-0-0RMA History : 00Deviation Number : 0Product Identifier (PID) : SPA-OC192POS-XFPVersion Identifier (VID) : V01Top Assy. Part Number : 68-2190-01Top Assy. Revision : A0 IDPROM Format Revision : 36System Clock Frequency : 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00CLEI Code : UNASSIGNEDBase MAC Address : 00 00 00 00 00 00MAC Address block size : 0Manufacturing Test Data : 00 00 00 00 00 00 00 00Field Diagnostics Data : 00 00 00 00 00 00 00 00Calibration Data : Minimum: 0 dBmV, Maximum: 0 dBmVCalibration values :Power Consumption : 11000 mWatts (Maximum)Environment Monitor Data : 03 30 04 B0 46 32 07 0846 32 09 C4 46 32 0C E446 32 13 88 46 32 07 0846 32 EB B0 50 3C 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 FE 02 F6 ACProcessor Label : 00 00 00 00 00 00 00Platform features : 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00 0000 00 00 00 00 00 00Asset ID :Asset Alias :Insertion Time : 00:00:10 (13:14:24 ago)Operational Status : okExample for a SPA Interface Processor on a Cisco 12000 Series Router
The following is sample output from the show diag command for a SIP located in chassis slot 2 on a Cisco 12000 series router:
Router# show diag 2SLOT 2 (RP/LC 2 ): Modular 10G SPA Interface CardMAIN: type 149, 800-26270-01 rev 84Deviation: 0HW config: 0x00 SW key: 00-00-00PCA: 73-9607-01 rev 91 ver 1Design Release 1.0 S/N SAD08460678MBUS: Embedded AgentTest hist: 0x00 RMA#: 00-00-00 RMA hist: 0x00DIAG: Test count: 0x00000000 Test results: 0x00000000FRU: Linecard/Module: 12000-SIP-650FRU: Linecard/Module: 12000-SIP-650Processor Memory: MEM-LC5-1024=(Non-Replaceable)Packet Memory: MEM-LC5-PKT-256=(Non-Replaceable)L3 Engine: 5 - ISE OC192 (10 Gbps)MBUS Agent Software version 1.114 (RAM) (ROM version is 3.4)ROM Monitor version 255.255Fabric Downloader version used 3.7 (ROM version is 255.255)Primary clock is CSC 1Board is analyzedBoard State is Line Card Enabled (IOS RUN )Insertion time: 1d00h (2d08h ago)Processor Memory size: 1073741824 bytesTX Packet Memory size: 268435456 bytes, Packet Memory pagesize: 32768 bytesRX Packet Memory size: 268435456 bytes, Packet Memory pagesize: 32768 bytes0 crashes since restartSPA Information:subslot 2/0: SPA-OC192POS-XFP (0x44C), status is oksubslot 2/1: Emptysubslot 2/2: Emptysubslot 2/3: EmptyExample for ADSL HWICs
The following is sample output from the show diag command for a Cisco 2811 router with HWIC-1ADSL installed in slot 1 and HWIC-1ADSLI installed in slot 2. Each HWIC has a daughtercard as part of its assembly. The command results below give the output from the HWIC followed by the output from its daughtercard.
Router# show diag 0
Slot 0:
C2811 Motherboard with 2FE and integrated VPN Port adapter, 2 portsPort adapter is analyzedPort adapter insertion time unknownOnboard VPN : v2.2.0EEPROM contents at hardware discovery:PCB Serial Number : FOC09052HHAHardware Revision : 2.0Top Assy. Part Number : 800-21849-02Board Revision : B0Deviation Number : 0Fab Version : 06RMA Test History : 00RMA Number : 0-0-0-0RMA History : 00Processor type : 87Hardware date code : 20050205Chassis Serial Number : FTX0908A0B0Chassis MAC Address : 0013.1ac2.2848MAC Address block size : 24CLEI Code : CNMJ7N0BRAProduct (FRU) Number : CISCO2811Part Number : 73-7214-09Version Identifier : NAEEPROM format version 4EEPROM contents (hex):0x00: 04 FF C1 8B 46 4F 43 30 39 30 35 32 48 48 41 400x10: 03 E7 41 02 00 C0 46 03 20 00 55 59 02 42 42 300x20: 88 00 00 00 00 02 06 03 00 81 00 00 00 00 04 000x30: 09 87 83 01 31 F1 1D C2 8B 46 54 58 30 39 30 380x40: 41 30 42 30 C3 06 00 13 1A C2 28 48 43 00 18 C60x50: 8A 43 4E 4D 4A 37 4E 30 42 52 41 CB 8F 43 49 530x60: 43 4F 32 38 31 31 20 20 20 20 20 20 82 49 1C 2E0x70: 09 89 20 20 4E 41 D9 02 40 C1 FF FF FF FF FF FFWIC Slot 1:ADSL over POTSHardware Revision : 7.0Top Assy. Part Number : 800-26247-01Board Revision : 01Deviation Number : 0Fab Version : 07PCB Serial Number : FHH093600D4RMA Test History : 00RMA Number : 0-0-0-0RMA History : 00Product (FRU) Number : HWIC-1ADSLVersion Identifier : V01CLEI Code :EEPROM format version 4EEPROM contents (hex):0x00: 04 FF 40 04 C8 41 07 00 C0 46 03 20 00 66 87 010x10: 42 30 31 88 00 00 00 00 02 07 C1 8B 46 48 48 300x20: 39 33 36 30 30 44 34 03 00 81 00 00 00 00 04 000x30: CB 94 48 57 49 43 2D 31 41 44 53 4C 20 20 20 200x40: 20 20 20 20 20 20 89 56 30 31 20 D9 02 40 C1 C60x50: 8A FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF0x60: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF0x70: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FFEM Slot 0:ADSL over POTS non-removable daughtercardHardware Revision : 5.0Part Number : 73-9307-05Board Revision : 03Deviation Number : 0Fab Version : 05PCB Serial Number : FHH0936006ERMA Test History : 00RMA Number : 0-0-0-0RMA History : 00Fab Part Number : 28-6607-05Manufacturing Test Data : 00 00 00 00 00 00 00 00Field Diagnostics Data : 00 00 00 00 00 00 00 00Connector Type : 01Version Identifier : V01Product (FRU) Number :EEPROM format version 4EEPROM contents (hex):0x00: 04 FF 40 04 7A 41 05 00 82 49 24 5B 05 42 30 330x10: 88 00 00 00 00 02 05 C1 8B 46 48 48 30 39 33 360x20: 30 30 36 45 03 00 81 00 00 00 00 04 00 85 1C 190x30: CF 05 C4 08 00 00 00 00 00 00 00 00 C5 08 00 000x40: 00 00 00 00 00 00 05 01 89 56 30 31 20 FF FF FF0x50: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF0x60: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF0x70: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FFWIC Slot 2:ADSL over ISDNHardware Revision : 7.0Top Assy. Part Number : 800-26248-01Board Revision : 01Deviation Number : 0Fab Version : 07PCB Serial Number : FHH093600DARMA Test History : 00RMA Number : 0-0-0-0RMA History : 00Product (FRU) Number : HWIC-1ADSLIVersion Identifier : V01CLEI Code :EEPROM format version 4EEPROM contents (hex):0x00: 04 FF 40 04 C9 41 07 00 C0 46 03 20 00 66 88 010x10: 42 30 31 88 00 00 00 00 02 07 C1 8B 46 48 48 300x20: 39 33 36 30 30 44 41 03 00 81 00 00 00 00 04 000x30: CB 94 48 57 49 43 2D 31 41 44 53 4C 49 20 20 200x40: 20 20 20 20 20 20 89 56 30 31 20 D9 02 40 C1 C60x50: 8A FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF0x60: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF0x70: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FFEM Slot 0:ADSL over ISDN non-removable daughtercardHardware Revision : 5.0Part Number : 73-9308-05Board Revision : 03Deviation Number : 0Fab Version : 05PCB Serial Number : FHH0936008MRMA Test History : 00RMA Number : 0-0-0-0RMA History : 00Fab Part Number : 28-6607-05Manufacturing Test Data : 00 00 00 00 00 00 00 00Field Diagnostics Data : 00 00 00 00 00 00 00 00Connector Type : 01Version Identifier : V01Product (FRU) Number :EEPROM format version 4EEPROM contents (hex):0x00: 04 FF 40 04 7B 41 05 00 82 49 24 5C 05 42 30 330x10: 88 00 00 00 00 02 05 C1 8B 46 48 48 30 39 33 360x20: 30 30 38 4D 03 00 81 00 00 00 00 04 00 85 1C 190x30: CF 05 C4 08 00 00 00 00 00 00 00 00 C5 08 00 000x40: 00 00 00 00 00 00 05 01 89 56 30 31 20 FF FF FF0x50: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF0x60: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF0x70: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FFThe following sample output from a Cisco 6500 series switch shows the FRU number:Router# show diagSlot 4: Logical_index 82 port adapter FlexWAN controllerBoard is analyzed ipc readyHW rev 1.5, board revision A0Serial Number: SAD062404C8 Part number: 73-3869-08Slot database information:Flags: 0x2004 Insertion time: 0x20960 (1d04h ago)Controller Memory Size:112 MBytes CPU Memory16 MBytes Packet Memory128 MBytes Total on Board SDRAMIOS (tm) cwlc Software (cwpa-DW-M), Version 12.2(18)SXF2, RELEASE SOFTW)PA Bay 0 Information:ENHANCED ATM OC3 MM PA, 1 ports, FRU: PA-A3-OC3-MMEEPROM format version 1HW rev 2.00, Board revision A0Serial number: 29360940 Part number: 73-2430-04Slot 4: Logical_index 92 port adapter FlexWAN controllerBoard is analyzed ipc readyHW rev 1.5, board revision A0Serial Number: SAD062404C8 Part number: 73-3869-08Slot database information:Flags: 0x2004 Insertion time: 0x20D10 (1d04h ago)Controller Memory Size:112 MBytes CPU Memory16 MBytes Packet Memory128 MBytes Total on Board SDRAMIOS (tm) cwlc Software (cwpa-DW-M), Version 12.2(18)SXF2, RELEASE SOFTW)PA Bay 1 Information:Mx Serial PA, 4 portsEEPROM format version 1HW rev 1.00, Board revision A0Serial number: 04387628 Part number: 73-1577-04Router#The following sample output from a Cisco 7600 series router shows the FRU number:
Router#show diagSlot 2: Logical_index 42 port adapter Enhanced FlexWAN controllerBoard is analyzed ipc readyHW rev 2.1, board revision A0Serial Number: JAE0940MH7Z Part number: 73-9539-04Slot database information:Flags: 0x2004 Insertion time: 0x256BC (1d01h ago)Controller Memory Size:384 MBytes CPU Memory127 MBytes Packet Memory511 MBytes Total on Board SDRAMIOS (tm) cwlc Software (cwpa2-DW-M), Version 12.2(18)SXF2, RELEASE SOFT)PA Bay 0 Information:ENHANCED ATM OC3 MM PA, 1 ports, FRU: PA-A3-OC3-MMEEPROM format version 4HW rev 2.00, Board revision A0Serial number: JAE0937KUPX Part number: 73-8728-01Slot 2: Logical_index 52 port adapter Enhanced FlexWAN controllerBoard is analyzed ipc readyHW rev 2.1, board revision A0Serial Number: JAE0940MH7Z Part number: 73-9539-04Slot database information:Flags: 0x2004 Insertion time: 0x22C34 (1d01h ago)Controller Memory Size:384 MBytes CPU Memory127 MBytes Packet Memory511 MBytes Total on Board SDRAMIOS (tm) cwlc Software (cwpa2-DW-M), Version 12.2(18)SXF2, RELEASE SOFT)PA Bay 1 Information:Mx Serial PA, 4 portsEEPROM format version 1HW rev 1.14, Board revision D0Serial number: 33929508 Part number: 73-1577-07Router#Related Commands
show disk0:
To display flash or file system information for a disk located in slot 0, use the show disk command in user EXEC or privileged EXEC mode.
show disk0: [all | filesys]
Syntax Description
Command Modes
User EXEC
Privileged EXECCommand History
Usage Guidelines
The show disk0: command is supported only on platforms that have a disk file system located in slot 0. Use the show disk0: command to display details about the files in a particular ATA PCMCIA flash disk memory card.
For more information regarding file systems and flash cards, access the PCMCIA Filesystem Compatibility Matrix and Filesystem Information document at the following URL:
http://www.cisco.com/en/US/partner/products/hw/routers/ps341/products_tech_note09186a00800a7515.shtml
Note
Examples
The following examples show displays of information about the flash disks or file system information for a disk. The output is self-explanatory.
c7200# show disk0:-#- --length-- -----date/time------ path1 29505176 Feb 27 2006 17:56:52 +00:00 c7200-jk9o3s-mz.124-6.T2 32768 Feb 24 2006 13:30:30 +00:00 file1.log34738176 bytes available (29540352 bytes used)c7200# show disk0: all-#- --length-- -----date/time------ path1 29505176 Feb 27 2006 17:56:52 +00:00 c7200-jk9o3s-mz.124-6.T2 32768 Feb 24 2006 13:30:30 +00:00 file1.log34738176 bytes available (29540352 bytes used)******** ATA Flash Card Geometry/Format Info ********ATA CARD GEOMETRYNumber of Heads: 4Number of Cylinders 984Sectors per Cylinder 32Sector Size 512Total Sectors 125952ATA CARD FORMATNumber of FAT Sectors 62Sectors Per Cluster 8Number of Clusters 15693Number of Data Sectors 125812Base Root Sector 232Base FAT Sector 108Base Data Sector 264ATA MONLIB INFOImage Monlib size = 73048Disk monlib size = 55296Name = NAMonlib end sector = NAMonlib Start sector = NAMonlib updated by = NAMonlib version = NAc7200# show disk0: filesys******** ATA Flash Card Geometry/Format Info ********ATA CARD GEOMETRYNumber of Heads: 4Number of Cylinders 984Sectors per Cylinder 32Sector Size 512Total Sectors 125952ATA CARD FORMATNumber of FAT Sectors 62Sectors Per Cluster 8Number of Clusters 15693Number of Data Sectors 125812Base Root Sector 232Base FAT Sector 108Base Data Sector 264ATA MONLIB INFOImage Monlib size = 73048Disk monlib size = 55296Name = NAMonlib end sector = NAMonlib Start sector = NAMonlib updated by = NAMonlib version = NARelated Commands
show disk1:
To display flash or file system information for a disk located in slot 1, use the show disk1: command in user EXEC or privileged EXEC mode.
show disk1: [all | filesys]
Syntax Description
Command Modes
User EXEC
Privileged EXECCommand History
Usage Guidelines
The show disk1: command is supported only on platforms that have a disk file system. Use the show disk01: command to display details about the files in a particular ATA PCMCIA flash disk memory card located in slot 1.
For more information regarding file systems and flash cards, access the PCMCIA Filesystem Compatibility Matrix and Filesystem Information document at the following URL:
http://www.cisco.com/en/US/partner/products/hw/routers/ps341/products_tech_note09186a00800a7515.shtml
Note
Examples
The following examples show displays of information about the flash disks or file system information for a disk. The output is self-explanatory.
c7200# show disk1:-#- --length-- -----date/time------ path1 29505176 Feb 27 2006 17:56:52 +00:00 c7200-jk9o3s-mz.124-6.T2 32768 Feb 24 2006 13:30:30 +00:00 file1.log34738176 bytes available (29540352 bytes used)c7200# show disk1: all-#- --length-- -----date/time------ path1 29505176 Feb 27 2006 17:56:52 +00:00 c7200-jk9o3s-mz.124-6.T2 32768 Feb 24 2006 13:30:30 +00:00 file1.log34738176 bytes available (29540352 bytes used)******** ATA Flash Card Geometry/Format Info ********ATA CARD GEOMETRYNumber of Heads: 4Number of Cylinders 984Sectors per Cylinder 32Sector Size 512Total Sectors 125952ATA CARD FORMATNumber of FAT Sectors 62Sectors Per Cluster 8Number of Clusters 15693Number of Data Sectors 125812Base Root Sector 232Base FAT Sector 108Base Data Sector 264ATA MONLIB INFOImage Monlib size = 73048Disk monlib size = 55296Name = NAMonlib end sector = NAMonlib Start sector = NAMonlib updated by = NAMonlib version = NAc7200# show disk1: filesys******** ATA Flash Card Geometry/Format Info ********ATA CARD GEOMETRYNumber of Heads: 4Number of Cylinders 984Sectors per Cylinder 32Sector Size 512Total Sectors 125952ATA CARD FORMATNumber of FAT Sectors 62Sectors Per Cluster 8Number of Clusters 15693Number of Data Sectors 125812Base Root Sector 232Base FAT Sector 108Base Data Sector 264ATA MONLIB INFOImage Monlib size = 73048Disk monlib size = 55296Name = NAMonlib end sector = NAMonlib Start sector = NAMonlib updated by = NAMonlib version = NARelated 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 privileged EXEC command.
show environment [alarms | all | fans | hardware | last | leds | power-supply | table | temperatures | voltages]
Note
Syntax Description
Defaults
If no options are specified, the default is all.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Once a minute a routine is run that gets environmental measurements from sensors and stores the output into a buffer. This buffer is displayed on the console when the show environment command is entered.
If a measurement exceeds desired margins, but has not exceeded fatal margins, a warning message is printed to the system console. The system software queries the sensors for measurements once a minute, but warnings for a given test point are printed at most once every hour for sensor readings in the warning range and once every 5 minutes for sensor readings in the critical range. If a measurement is out of line within these time segments, an automatic warning message appears on the console. As noted, you can query the environmental status with the show environment command at any time to determine whether a measurement is at the warning or critical tolerance.
If a shutdown occurs because of detection of fatal environmental margins, the last measured value from each sensor is stored in internal nonvolatile memory.
For environmental specifications, refer to the hardware installation and configuration publication for your individual chassis.
If the Cisco 12000 series exceeds environmental conditions, a message similar to the following is displayed on the console:
%GSR_ENV-2-WARNING: Slot 3 Hot Sensor Temperature exceeds 40 deg C;Check cooling systems
Note
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 72 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 73 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 74 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 75 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 76 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 77 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 78 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 79 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 80 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 system 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 81 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 82 describes the significant fields shown and lists the equipment supported by each environmental parameter. "NA" indicates that the reading could not be obtained, so the command should be again.
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 EXEC command.
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 EXEC command.
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 system logging message buffer,, use the show logging privileged EXEC command.
show logging [slot slot-number | summary]
Syntax Description
Command Modes
Privileged EXEC
Command History
10.0
This command was introduced.
11.2 GS
The slot and summary keywords were added for the Cisco 12000 family.
Usage Guidelines
This command displays the state of syslog error and event logging, including host addresses, and whether console logging is enabled. This command also displays Simple Network Management Protocol (SNMP) configuration parameters and protocol activity.
Note
Examples
The following is sample output from the show logging command:
Router# show loggingSyslog logging: enabledConsole logging: disabledMonitor logging: level debugging, 266 messages logged.Trap logging: level informational, 266 messages logged.Logging to 192.180.2.238SNMP logging: disabled, retransmission after 30 seconds0 messages loggedRouter#Table 83 describes the significant fields shown in the display.
The following is sample output from the show logging summary command for the Cisco 12012 router. A number in the column indicates that the syslog contains that many messages for the line card. For example, line card in slot 9 has 1 system message, 4 warning messages, and 47 notification messages.
Router# show logging summary+-----+-------+-------+-------+-------+-------+-------+-------+-------+SLOT | EMERG | ALERT | CRIT | ERROR |WARNING| NOTICE| INFO | DEBUG |+-----+-------+-------+-------+-------+-------+-------+-------+-------+|* 0* | . | . | . | . | . | . | . | . || 1 | | | | | | | | || 2 | | | | 1 | 4 | 45 | | || 3 | | | | | | | | || 4 | | | | 5 | 4 | 54 | | || 5 | | | | | | | | || 6 | | | | | | | | || 7 | | | | 17 | 4 | 48 | | || 8 | | | | | | | | || 9 | | | | 1 | 4 | 47 | | || 10 | | | | | | | | || 11 | | | | 12 | 4 | 65 | | |+-----+-------+-------+-------+-------+-------+-------+-------+-------+Router#Table 84 describes the logging level fields shown in the display.
Related Commands
show logging history
To display information about the state of the syslog history table, use the show logging history privileged EXEC command.
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 85 describes the significant fields shown in the output.
Related Commands
show memory
To display memory utilization statistics, use the show memory command in User or Privileged EXEC mode.
show memory [ start-address [end-address] | [ processor | io | multibus] [free] | summary ]
Syntax Description
Defaults
If a memory address is not specified, statistics for all memory addresses are displayed.
If a memory type (processor | io | multibus) is not specified, statistics for all memory types present are displayed.
Command Modes
EXEC
Command History
10.0
This command was introduced, using the following syntax:
show memory { <start_address> [end_address] | {[ processor | io | sram | multibus ] [free]} }
Usage Guidelines
This command prints detailed memory information to the screen. This information is intended for use by Cisco technical support personnel.
Tip
This command first displays how much memory is being used on the router by memory pool (processor, shared I/O memory, and, potentially, SRAM). Then this command displays, for each memory pool, a complete list of all blocks.
Examples
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 86 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 87 describes the significant fields shown in the second section of the display.
The show memory io command displays the free I/O memory blocks.
The following is sample output from the show memory io command:
Router# show memory 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 summary command displays a summary of all memory pools and memory usage per Alloc PC (address of the system call that allocated the block).
The following is partial sample output from the show memory summary command.
"Size" is the number of bytes in each block. "Bytes" is the total size for all blocks ("Bytes" equals the "Size" value multiplied by the "Blocks" value). For a description of the other fields, see Table 20 and Table 21.
Router# show memory summaryHead Total(b) Used(b) Free(b) Lowest(b) Largest(b)Processor 8404A580 64102816 10509276 53593540 52101448 51007568I/O 7C53000 3854336 2138224 1716112 1708432 1716064Processor 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 processes memory
Displays a summary of how much memory is being allocated and freed by each process on the router.
show memory allocating-process
To display statistics on allocated memory with corresponding allocating processes, use the show memory allocating-process command in user EXEC or privileged EXEC mode.
show memory allocating-process [totals]
Syntax Description
Command Modes
User EXEC
Privileged EXECCommand History
Usage Guidelines
The show memory allocating-process command displays information about memory available after the system image decompresses and loads.
Examples
The following is sample output from the show memory allocating-process command:
Router# show memory allocating-processHead Total(b) Used(b) Free(b) Lowest(b) Largest(b)Processor 44E03560 186632636 26131896 160500740 160402052 153078204Fast 44DE3560 131072 58280 72792 72792 72764Processor memoryAddress Bytes Prev. Next Ref Alloc Proc Alloc PC What6148EC40 1504 0 6148F24C 1 *Init* 602310FC List Elements6148F24C 3004 6148EC40 6148FE34 1 *Init* 60231128 List Headers6148FE34 9000 6148F24C 61492188 1 *Init* 6023C634 Interrupt Stack61492188 44 6148FE34 614921E0 1 *Init* 60C17FD8 *Init*614921E0 9000 61492188 61494534 1 *Init* 6023C634 Interrupt Stack61494534 44 614921E0 6149458C 1 *Init* 60C17FD8 *Init*6149458C 220 61494534 61494694 1 *Init* 602450F4 *Init*61494694 4024 6149458C 61495678 1 *Init* 601CBD64 TTY data...Table 92 describes the significant fields shown in the display.
The following is sample output from the show memory allocating-process totals command:
Router# show memory allocating-process totalsHead Total(b) Used(b) Free(b) Lowest(b) Largest(b)Processor 44E03560 186632636 26142524 160490112 160402052 153078204Fast 44DE3560 131072 58280 72792 72792 72764Allocator PC Summary for: ProcessorPC Total Count Name0x4041AF8C 5710616 3189 *Packet Data*0x4041AF40 2845480 3190 *Packet Header*0x404DBA28 1694556 203 Process Stack0x4066EA68 1074080 56 Init0x404B5F68 1049296 9 pak subblock chunk0x41DCF230 523924 47 TCL Chunks0x404E2488 448920 6 MallocLite0x4066EA8C 402304 56 Init0x40033878 397108 1 Init0x41273E24 320052 1 CEF: table event ring0x404B510C 253152 24 TW Buckets0x42248F0C 229428 1 Init0x42248F28 229428 1 Init0x42248F48 229428 1 Init0x423FF210 218048 5 Dn48oC!M0x421CB530 208144 1 epa crypto blk0x417A07F0 196764 3 L2TP Hash Table0x403AFF50 187836 3 InitTable 86 describes the significant fields shown in the display.
Related Commands
show memory dead
To display statistics of memory allocated by processes that are now dead, use the show memory dead command in user EXEC or privileged EXEC mode.
show memory dead [totals]
Syntax Description
Command Modes
User EXEC
Privileged EXECCommand History
Usage Guidelines
The show memory dead command displays information about processes that have been terminated. Terminated processes accounts for memory allocated under another process.
Examples
The following is sample output from the show memory dead command:
Router# show memory deadHead Total(b) Used(b) Free(b) Lowest(b) Largest(b)I/O 600000 2097152 461024 1636128 1635224 1635960Processor memoryAddress Bytes Prev. Next Ref PrevF NextF Alloc PC What1D8310 60 1D82C8 1D8378 1 3281FFE Router Init2CA964 36 2CA914 2CA9B4 1 3281FFE Router Init2CAA04 112 2CA9B4 2CAAA0 1 3A42144 OSPF Stub LSA RBTree2CAAA0 68 2CAA04 2CAB10 1 3A420D4 Router Init2ED714 52 2ED668 2ED774 1 3381C84 Router Init2F12AC 44 2F124C 2F1304 1 3A50234 Router Init2F1304 24 2F12AC 2F1348 1 3A420D4 Router Init2F1348 68 2F1304 2F13B8 1 3381C84 Router Init300C28 340 300A14 300DA8 1 3381B42 Router InitTable 86 describes the significant fields shown in the display.
show memory debug references
To display the list of blocks containing references to a given range of addresses in the memory or references to free memory, use the show memory debug references command in user EXEC or privileged EXEC mode.
show memory debug references [dangling[start-address start-address ]]
Syntax Description
dangling
(Optional) Displays the possible references to free memory.
start-address
(Optional) Address numbers <0-4294967295> that determine the address range.
Command Modes
User EXEC
Privileged EXECCommand History
Examples
The following is sample output from the show memory debug references command:
Router# show memory debug references 2 3Address Reference Cont_block Cont_block_name442850BC 2 44284960 bss44285110 3 44284960 bss4429C33C 2 44284960 bss4429C34C 2 44284960 bss4429C35C 3 44284960 bss...The following is sample output from the show memory debug references dangling command:
Router# show memory debug references danglingAddress Reference Free_block Cont_block Cont_block_name442D5774 458CE5EC 458CE5BC 44284960 bss442D578C 46602998 46602958 44284960 bss442D58A0 465F9BC4 465F9B94 44284960 bss442D58B8 4656785C 4656781C 44284960 bss442D5954 45901E7C 45901E4C 44284960 bss...Table 86 describes the significant fields shown in the displays.
show memory debug unused
To display the list of memory blocks which have been allocated but not used, use the show memory debug unused command in user EXEC or privileged EXEC mode.
show memory debug unused
Syntax Description
This command has no arguments or keywords.
Command Modes
User EXEC
Privileged EXECCommand History
Examples
The following is sample output from the show memory debug unused command:
Router# show memory debug unusedAddress Alloc_pc PID size Name654894B8 62BF31DC -2 44 *Init*6549A074 601F7A84 -2 4464 XDI data6549B218 601F7274 -2 4500 XDI data6549DFB0 6089DDA4 42 84 Init65509160 6089DDA4 1 84 *Init*6550A260 6089DDA4 2 84 *Init*6551FDB4 6089DDA4 4 84 *Init*6551FF34 627EFA2C -2 24 *Init*65520B3C 6078B1A4 -2 24 Parser Mode Q165520B88 6078B1C8 -2 24 Parser Mode Q265520C40 6078B1A4 -2 24 Parser Mode Q165520C8C 6078B1C8 -2 24 Parser Mode Q265520D44 6078B1A4 -2 24 Parser Mode Q165520D90 6078B1C8 -2 24 Parser Mode Q265520E48 6078B1A4 -2 24 Parser Mode Q165520E94 6078B1C8 -2 24 Parser Mode Q265520F4C 6078B1A4 -2 24 Parser Mode Q165520F98 6078B1C8 -2 24 Parser Mode Q265521050 6078B1A4 -2 24 Parser Mode Q16552109C 6078B1C8 -2 24 Parser Mode Q265521154 6078B1A4 -2 24 Parser Mode Q1655211A0 6078B1C8 -2 24 Parser Mode Q2...Table 92 describes the significant fields shown in the display.
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 86 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 memory failures alloc
To display statistics about failed memory allocation requests, use the show memory failures alloc command in the privileged EXEC mode.
show memory failures alloc
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the show memory failures alloc command:
Router# show memory failures allocCaller Pool Size Alignment When0x60394744 I/O 1684 32 00:10:030x60394744 I/O 1684 32 00:10:030x60394744 I/O 1684 32 00:10:030x60394744 I/O 1684 32 00:10:030x60394744 I/O 1684 32 00:10:030x60394744 I/O 1684 32 00:10:030x60394744 I/O 1684 32 00:10:030x60394744 I/O 1684 32 00:10:030x60394744 I/O 1684 32 00:10:040x60394744 I/O 1684 32 00:10:04Table 86 describes the significant fields shown in the display.
show memory fast
To display fast memory details for the router, use the show memory fast command.
show memory fast [ allocating-process [totals] | dead [totals] | free [totals] ]
Syntax Description
Command Modes
Exec
Command History
Usage Guidelines
The show memory fast command displays the statistics for the fast memory. "Fast memory" is another name for "processor memory," and is also known as "cache memory." Cache memory is called fast memory because the processor can generally access the local cache (traditionally stored on SRAM positioned close to the processor) much more quickly than main (primary) memory.
Cache = fast memory closest to processor = "processor memory"
Primary Memory = the main memory below cache.
Note
Examples
The following example shows sample output from the show memory fast and the show memory processor commands:
Router>show memory fastProcessor memoryAddress Bytes Prev Next Ref PrevF NextF Alloc PC what8404A580 0001493284 00000000 841B6ECC 000 0 84BADF88 815219D8 (coalesced)841B6ECC 0000020004 8404A580 841BBD18 001 -------- -------- 815DB094 Managed Chunk Queue Elements841BBD18 0000001504 841B6ECC 841BC320 001 -------- -------- 8159EAC4 List Elements841BC320 0000005004 841BBD18 841BD6D4 001 -------- -------- 8159EB04 List Headers841BD6D4 0000000048 841BC320 841BD72C 001 -------- -------- 81F2A614 *Init*841BD72C 0000001504 841BD6D4 841BDD34 001 -------- -------- 815A9514 messages841BDD34 0000001504 841BD72C 841BE33C 001 -------- -------- 815A9540 Watched messages841BE33C 0000001504 841BDD34 841BE944 001 -------- -------- 815A95E4 Watched Semaphore841BE944 0000000504 841BE33C 841BEB64 001 -------- -------- 815A9630 Watched Message Queue841BEB64 0000001504 841BE944 841BF16C 001 -------- -------- 815A9658 Watcher Message Queue841BF16C 0000001036 841BEB64 841BF5A0 001 -------- -------- 815A2B24 Process Array-- More --<Ctrl+z>Router>show memory processorProcessor memoryAddress Bytes Prev Next Ref PrevF NextF Alloc PC what8404A580 0001493284 00000000 841B6ECC 000 0 84BADF88 815219D8 (coalesced)841B6ECC 0000020004 8404A580 841BBD18 001 -------- -------- 815DB094 Managed Chunk Queue Elements841BBD18 0000001504 841B6ECC 841BC320 001 -------- -------- 8159EAC4 List Elements841BC320 0000005004 841BBD18 841BD6D4 001 -------- -------- 8159EB04 List Headers841BD6D4 0000000048 841BC320 841BD72C 001 -------- -------- 81F2A614 *Init*841BD72C 0000001504 841BD6D4 841BDD34 001 -------- -------- 815A9514 messages841BDD34 0000001504 841BD72C 841BE33C 001 -------- -------- 815A9540 Watched messages841BE33C 0000001504 841BDD34 841BE944 001 -------- -------- 815A95E4 Watched Semaphore841BE944 0000000504 841BE33C 841BEB64 001 -------- -------- 815A9630 Watched Message Queue841BEB64 0000001504 841BE944 841BF16C 001 -------- -------- 815A9658 Watcher Message Queue841BF16C 0000001036 841BEB64 841BF5A0 001 -------- -------- 815A2B24 Process Array-- More --<Ctrl+z>Router>The following example shows sample output from the show memory fast allocating-process command, followed by sample output from the show memory fast allocating-process totals command:
Router#show memory fast allocating-processProcessor memoryAddress Bytes Prev Next Ref Alloc Proc Alloc PC What8404A580 0001493284 00000000 841B6ECC 000 815219D8 (coalesced)841B6ECC 0000020004 8404A580 841BBD18 001 *Init* 815DB094 Managed Chunk Queue Elements841BBD18 0000001504 841B6ECC 841BC320 001 *Init* 8159EAC4 List Elements841BC320 0000005004 841BBD18 841BD6D4 001 *Init* 8159EB04 List Headers841BD6D4 0000000048 841BC320 841BD72C 001 *Init* 81F2A614 *Init*841BD72C 0000001504 841BD6D4 841BDD34 001 *Init* 815A9514 messages841BDD34 0000001504 841BD72C 841BE33C 001 *Init* 815A9540 Watched messages841BE33C 0000001504 841BDD34 841BE944 001 *Init* 815A95E4 Watched Semaphore841BE944 0000000504 841BE33C 841BEB64 001 *Init* 815A9630 Watched Message Queue841BEB64 0000001504 841BE944 841BF16C 001 *Init* 815A9658 Watcher Message Queue841BF16C 0000001036 841BEB64 841BF5A0 001 *Init* 815A2B24 Process Array--More--<Ctrl+z>c2600-1#show memory fast allocating-process totalsAllocator PC Summary for: ProcessorPC Total Count Name0x815C085C 1194600 150 Process Stack0x815B6C28 948680 5 pak subblock chunk0x819F1DE4 524640 8 BGP (0) update0x815C4FD4 393480 6 MallocLite0x815B5FDC 351528 30 TW Buckets0x819F14DC 327900 5 connected0x81A1E838 327900 5 IPv4 Unicast net-chunk(8)0x8153DFB8 248136 294 *Packet Header*0x82142438 133192 4 CEF: 16 path chunk pool0x82151E0C 131116 1 Init0x819F1C8C 118480 4 BGP (0) attr0x815A4858 100048 148 Process0x8083DA44 97248 17--More--<Ctrl+z>The following example shows sample output from the show memory fast dead command:
Router#show memory fast deadProcessor memoryAddress Bytes Prev Next Ref PrevF NextF Alloc PC what8498FC20 0000000028 8498FB90 8498FC64 001 -------- -------- 81472B24 AAA MI SG NAME-------68Router#show memory fast dead totalsDead Proc Summary for: ProcessorPC Total Count Name0x81472B24 68 1 AAA MI SG NAMERouter#show memory multibus
To display statistics about multibus memory, including memory-free pool statistics, use the show memory multibus command in user EXEC or privileged EXEC mode.
show memory multibus [allocating-process [totals]| dead [totals]| free [totals]]
Syntax Description
Command Modes
User EXEC
Privileged EXECCommand History
Examples
The following is sample output from the show memory multibus command:
Router# show memory multibusProcessor memoryAddress Bytes Prev Next Ref PrevF NextF Alloc PC what6540BBA0 0000016388 00000000 6540FBD4 001 -------- -------- 60883984 TW Buckes6540FBD4 0000016388 6540BBA0 65413C08 001 -------- -------- 60883984 TW Buckes65413C08 0000016388 6540FBD4 65417C3C 001 -------- -------- 60883984 TW Buckes65417C3C 0000006004 65413C08 654193E0 001 -------- -------- 608A0D4C Process k654193E0 0000012004 65417C3C 6541C2F4 001 -------- -------- 608A0D4C Process k6541C2F4 0000411712 654193E0 65480B64 000 0 0 608A0D4C (fragmen)65480B64 0000020004 6541C2F4 654859B8 001 -------- -------- 608CF99C Managed s654859B8 0000010004 65480B64 654880FC 001 -------- -------- 6085C7F8 List Eles654880FC 0000005004 654859B8 654894B8 001 -------- -------- 6085C83C List Heas654894B8 0000000048 654880FC 65489518 001 -------- -------- 62BF31DC *Init*...Table 95 describes the significant fields shown in the display.
show memory pci
To display statistics about Peripheral Component Interconnect (PCI) memory, use the show memory pci command in user EXEC or privileged EXEC mode.
show memory pci
Syntax Description
This command has no arguments or keywords.
Command Modes
User EXEC
Privileged EXECCommand History
Examples
The following is sample output from the show memory pci command:
Router# show memory pciI/O memoryAddress Bytes Prev Next Ref PrevF NextF Alloc PC what0E000000 0000000032 00000000 0E000050 000 64F5EBF4 0 00000000 (fragmen)0E000050 0000000272 0E000000 0E000190 001 -------- -------- 607E2EC0 *Packet *0E000190 0000000272 0E000050 0E0002D0 001 -------- -------- 607E2EC0 *Packet *0E0002D0 0000000272 0E000190 0E000410 001 -------- -------- 607E2EC0 *Packet *0E000410 0000000272 0E0002D0 0E000550 001 -------- -------- 607E2EC0 *Packet *0E000550 0000000272 0E000410 0E000690 001 -------- -------- 607E2EC0 *Packet *0E000690 0000000272 0E000550 0E0007D0 001 -------- -------- 607E2EC0 *Packet *0E0007D0 0000000272 0E000690 0E000910 001 -------- -------- 607E2EC0 *Packet *0E000910 0000000272 0E0007D0 0E000A50 001 -------- -------- 607E2EC0 *Packet *0E000A50 0000000272 0E000910 0E000B90 001 -------- -------- 607E2EC0 *Packet *0E000B90 0000000272 0E000A50 0E000CD0 001 -------- -------- 607E2EC0 *Packet *Address Bytes Prev Next Ref PrevF NextF Alloc PC what0E000CD0 0000000272 0E000B90 0E000E10 001 -------- -------- 607E2EC0 *Packet *0E000E10 0000000272 0E000CD0 0E000F50 001 -------- -------- 607E2EC0 *Packet *Table 86 describes the significant fields shown in the display.
show memory processor
To display statistics on the router processor memory, use the show memory processor command in user EXEC or privileged EXEC mode.
show memory processor [fragment | free | statistics]
Syntax Description
Command Modes
User EXEC
Privileged EXECCommand History
Examples
The following is sample output from the show memory processor commands:
Router# show memory processorProcessor memoryAddress Bytes Prev Next Ref PrevF NextF Alloc PC what6540BBA0 0000016388 00000000 6540FBD4 001 -------- -------- 60883984 TW Buckes6540FBD4 0000016388 6540BBA0 65413C08 001 -------- -------- 60883984 TW Buckes65413C08 0000016388 6540FBD4 65417C3C 001 -------- -------- 60883984 TW Buckes65417C3C 0000006004 65413C08 654193E0 001 -------- -------- 608A0D4C Process k654193E0 0000012004 65417C3C 6541C2F4 001 -------- -------- 608A0D4C Process k6541C2F4 0000411712 654193E0 65480B64 000 0 0 608A0D4C (fragmen)65480B64 0000020004 6541C2F4 654859B8 001 -------- -------- 608CF99C Managed s654859B8 0000010004 65480B64 654880FC 001 -------- -------- 6085C7F8 List Eles654880FC 0000005004 654859B8 654894B8 001 -------- -------- 6085C83C List Heas654894B8 0000000048 654880FC 65489518 001 -------- -------- 62BF31DC *Init*Table 97 describes the significant fields shown in the display.
The following is sample output from the show memory processor fragment command:
Router# show memory processor fragmentProcessor memoryFree memory size : 3144348 Number of free blocks: 96Allocator PC Summary for allocated blocks in pool: ProcessorPC Total Count Name0x6069A038 262196 1 TACL FLT0x62224AA8 219188 1 QOS_MODULE_MAIN0x61648840 131124 1 Init0x6218DAA4 73780 1 CCSIP_UDP_SOCKET0x61649288 65588 1 CEF: loadinfo chunk0x61BFD4B8 65588 1 PPTP mgd timer chunk0x61EE1050 65588 1 eddri_self_event0x607C13C4 49204 1 Exec0x608A0D4C 35208 4 Process Stack0x6069D804 32052 1 TACL hist0x61631A90 21444 2 CEF: IPv4 Unicast RPF subblock0x62BA5DD8 20432 1 Init0x6086F858 20052 1 RMI-RO_RU Chun0x608CF99C 20052 1 Managed Chunk Queue ElementsTable 98 describes the significant fields shown in the display.
The following is sample output from the show memory processor free command:
Router# show memory processor freeProcessor memoryAddress Bytes Prev Next Ref PrevF NextF Alloc PC what24 Free list 166994680 0000000072 66994618 669946FC 000 0 6698FFC8 60699114 Turbo ACr6698FFC8 0000000072 6698FF60 66990044 000 66994680 659CF6B0 60699114 Turbo ACr659CF6B0 0000000024 659CF678 659CF6FC 000 6698FFC8 659CF86C 6078A2CC Init659CF86C 0000000024 659CF710 659CF8B8 000 659CF6B0 65ADB53C 6078A2CC Init65ADB53C 0000000024 65ADB504 65ADB588 000 659CF86C 65ADFC38 6078A2CC Init65ADFC38 0000000024 65ADFC00 65ADFC84 000 65ADB53C 65B6C504 6078A2CC Init65B6C504 0000000024 65B6C4B8 65B6C550 000 65ADFC38 6593E924 6078A2CC Init6593E924 0000000028 6593E8E8 6593E974 000 65B6C504 65CCB054 6078A2CC Init65CCB054 0000000024 65CCB01C 65CCB0A0 000 6593E924 65CCBD98 6078A2CC Init65CCBD98 0000000028 65CCBD60 65CCBDE8 000 65CCB054 65CCFB70 6078A2CC Init65CCFB70 0000000024 65CCFB38 65CCFBBC 000 65CCBD98 65D0BB58 6078A2CC Init65D0BB58 0000000024 65D0BB20 65D0BBA4 000 65CCFB70 65D0C5F0 6078A2CC Init65D0C5F0 0000000024 65D0C5B8 65D0C63C 000 65D0BB58 65CFF2F4 6078A2CC Init65CFF2F4 0000000024 65CFF2BC 65CFF340 000 65D0C5F0 6609B7B8 6078A2CC Init6609B7B8 0000000036 6609AFC8 6609B810 000 65CFF2F4 660A0BD4 6078A2CC InitTable 92 describes the significant fields shown in the display.
The following is sample output from the show memory processor statistics command:
Router# show memory processor statisticsHead Total(b) Used(b) Free(b) Lowest(b) Largest(b)Processor 6540BBA0 415187836 27216968 387970868 385755044 381633404I/O E000000 33554432 6226336 27328096 27328096 27317852...Table 86 describes the significant fields shown in the display.
show memory scan
To monitor the number and type of parity (memory) errors on your system, use the show memory scan command in Exec mode.
show memory scan
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Usage Guidelines
For the show memory scan command to function, the memory scan feature must be enabled on the RSP using the memory scan global configuraiton mode command.
Examples
The following example shows a result with no memory errors:
Router# show memory scanMemory scan is on.No parity error has been detected.If errors are detected in the system, the show memory scan command generates an error report. In the following example, memory scan detected a parity error:
Router# show memory scanMemory scan is on.Total Parity Errors 1.Address BlockPtr BlckSize Disposit Region Timestamp6115ABCD 60D5D090 9517A4 Scrubed Local 16:57:09 UTC Thu Mar 18Table 101 describes the fields contained in the error report.
Related Commands
show memory statistics history table
To display the history of memory consumption, use the show memory statistics history table command in user EXEC or privileged EXEC mode.
show memory statistics history table
Syntax Description
This command has no arguments or keywords.
Command Modes
User EXEC
Privileged EXECCommand History
Usage Guidelines
The show memory statistics history table command displays a histogram of memory usage. The quantity on the x-axis is percentage of memory free and on the y-axis is time. The height of the histogram at any given point in time indicates the percentage of free memory in the pool.
Examples
The following is sample output from the show memory statistics history table command:
Router# show memory statistics history tableHistory for Processor memoryTime: 15:48:56.806Used(b): 422748036 Largest(b): 381064952 Free blocks :291Maximum memory users for this periodProcess Name Holding Num AllocVirtual Exec 26992 37TCP Protocols 14460 6IP Input 1212 1Time: 14:42:54.506Used(b): 422705876 Largest(b): 381064952 Free blocks :296Maximum memory users for this periodProcess Name Holding Num AllocExec 400012740 24Dead 1753456 90Pool Manager 212796 257Time: 13:37:26.918Used(b): 20700520 Largest(b): 381064952 Free blocks :196Maximum memory users for this periodProcess Name Holding Num AllocExec 8372 5Time: 12:39:44.422Used(b): 20701436 Largest(b): 381064952 Free blocks :193Time: 11:46:25.135Used(b): 20701436 Largest(b): 381064952 Free blocks :193Maximum memory users for this periodProcess Name Holding Num AllocCDP Protocol 3752 25Time: 10:44:24.342Used(b): 20701400 Largest(b): 381064952 Free blocks :194Time: 09:38:53.038Used(b): 20701400 Largest(b): 381064952 Free blocks :194Time: 08:33:35.154Used(b): 20701400 Largest(b): 381064952 Free blocks :194Time: 07:28:05.987Used(b): 20701400 Largest(b): 381064952 Free blocks :194Time: 06:35:22.878Used(b): 20701400 Largest(b): 381064952 Free blocks :194Time: 05:42:14.286Used(b): 20701400 Largest(b): 381064952 Free blocks :194Time: 04:41:53.486Used(b): 20701400 Largest(b): 381064952 Free blocks :194Time: 03:48:47.891Used(b): 20701400 Largest(b): 381064952 Free blocks :194Time: 02:46:32.391Used(b): 20701400 Largest(b): 381064952 Free blocks :194Time: 01:54:27.931Used(b): 20717804 Largest(b): 381064952 Free blocks :189Time: 01:02:05.535Used(b): 20717804 Largest(b): 381064952 Free blocks :189Maximum memory users for this periodProcess Name Holding Num AllocEntity MIB API 67784 16TTY Background 12928 4Exec 7704 3Time: 00:00:17.936Used(b): 21011192 Largest(b): 381064952 Free blocks :186Maximum memory users for this periodProcess Name Holding Num AllocInit 18653520 6600CCPROXY_CT 599068 57Proxy Session Applic 275424 21History for I/O memoryTime: 15:48:56.809Used(b): 7455520 Largest(b): 59370080 Free blocks :164Time: 14:42:54.508Used(b): 7458064 Largest(b): 59370080 Free blocks :165Maximum memory users for this periodProcess Name Holding Num AllocPool Manager 141584 257Time: 13:37:26.920Used(b): 7297744 Largest(b): 59797664 Free blocks :25Time: 12:39:44.424Used(b): 7297744 Largest(b): 59797664 Free blocks :25Time: 11:46:25.137Used(b): 7297744 Largest(b): 59797664 Free blocks :25Time: 10:44:24.344Used(b): 7297744 Largest(b): 59797664 Free blocks :25Time: 09:38:53.040Used(b): 7297744 Largest(b): 59797664 Free blocks :25Time: 08:33:35.156Used(b): 7297744 Largest(b): 59797664 Free blocks :25Time: 07:28:05.985Used(b): 7297744 Largest(b): 59797664 Free blocks :25Time: 06:35:22.877Used(b): 7297744 Largest(b): 59797664 Free blocks :25Time: 05:42:14.285Used(b): 7297744 Largest(b): 59797664 Free blocks :25Time: 04:41:53.485Used(b): 7297744 Largest(b): 59797664 Free blocks :25Time: 03:48:47.889Used(b): 7297744 Largest(b): 59797664 Free blocks :25Time: 02:46:32.389Used(b): 7297744 Largest(b): 59797664 Free blocks :25Time: 01:54:27.929Used(b): 7308336 Largest(b): 59797664 Free blocks :23Time: 01:02:05.533Used(b): 7308336 Largest(b): 59797664 Free blocks :23Time: 00:00:17.937Used(b): 7308336 Largest(b): 59797664 Free blocks :23Maximum memory users for this periodProcess Name Holding Num AllocInit 7296000 214Pool Manager 816 3Table 102 describes the significant fields shown in the display.
Related Commands
show memory transient
To display statistics about transient memory, use the show memory transient command in user EXEC or privileged EXEC mode.
show memory transient [allocating-process [totals]| dead [totals]| fragment [detail]| free [totals]| statistics [history]]
Syntax Description
Command Modes
User EXEC
Privileged EXECCommand History
Examples
The following is sample output from the show memory transient command:
Router# show memory transientProcessor memoryAddress Bytes Prev Next Ref PrevF NextF Alloc PC what81F99C00 0002236408 00000000 821BBC28 000 829C8104 82776FD0 8060B6D0 (coalesc)821BBC28 0000020004 81F99C00 821C0A7C 001 -------- -------- 8002D5C0 Managed s821C0A7C 0000010004 821BBC28 821C31C0 001 -------- -------- 811604C0 List Eles821C31C0 0000005004 821C0A7C 821C457C 001 -------- -------- 81160500 List HeasTable 86 describes the significant fields shown in the display.
show pci
To display information about the peripheral component interconnect (PCI) hardware registers or bridge registers for the Cisco 7200 series routers, use the show pci EXEC command.
show pci {hardware | bridge [register]}
Syntax Description
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 EXEC command.
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 104 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 105 describes the significant fields shown in the displays.
Note
For a list of process descriptions, see http://www.cisco.com/warp/public/63/showproc_cpu.html .
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 106 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 107 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 the configured protocols, use the show protocols EXEC command.
This command shows the global and interface-specific status of any configured Level 3 protocol; for example, IP, DECnet, IPX, AppleTalk, and so on.
show protocols
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
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, Part 1, Network Protocols Configuration Guide, Part 2, and Network Protocols Configuration Guide, Part 3.
show slot
To display information about the PCMCIA flash memory cards file system, use the show slot command in user EXEC or privileged EXEC mode.
show slot [all | chips | filesys]
Syntax Description
Command Modes
User EXEC
Privileged EXECCommand History
Usage Guidelines
Use the show slot command to display details about the files in a particular linear PCMCIA flash memory card of less than 20 MB and some 32 MB linear PCMCIA cards.
Note
For more information regarding file systems and flash cards, access the PCMCIA Filesystem Compatibility Matrix and Filesystem Information document at the following URL:
http://www.cisco.com/en/US/partner/products/hw/routers/ps341/products_tech_note09186a00800a7515.shtml
To see which flash cards are used in your router, use the show version command and look at the bottom portion of the output.
The following display indicates an ATA PCMCIA flash disk.
Router# show version...46976K bytes of ATA PCMCIA card at slot 0 (Sector size 512 bytes).The following display indicates a linear PCMCIA flash card with 20480K bytes of flash memory in card at slot 1 with a sector size of 128K.
Router# show version...20480K bytes of Flash PCMCIA card at slot 1 (Sector size 128K).
Note
Examples
The following example displays information about slot 0. The output is self-explanatory.
Router# show slotPCMCIA Slot0 flash directory:File Length Name/status1 11081464 c3660-bin-mz.123-9.3.PI5b[11081528 bytes used, 9627844 available, 20709372 total]20480K bytes of processor board PCMCIA Slot0 flash (Read/Write)The following example shows all possible flash system information for all PCMCIA flash cards in the system.
Router# show slot allPartition Size Used Free Bank-Size State Copy Mode1 20223K 10821K 9402K 4096K Read/Write DirectPCMCIA Slot0 flash directory:File Length Name/statusaddr fcksum ccksum1 11081464 c3660-bin-mz.123-9.3.PI5b0x40 0x5EA3 0x5EA3[11081528 bytes used, 9627844 available, 20709372 total]20480K bytes of processor board PCMCIA Slot0 flash (Read/Write)Chip Bank Code Size Name1 1 89A0 2048KB INTEL 28F016SA2 1 89A0 2048KB INTEL 28F016SA1 2 89A0 2048KB INTEL 28F016SA2 2 89A0 2048KB INTEL 28F016SA1 3 89A0 2048KB INTEL 28F016SA2 3 89A0 2048KB INTEL 28F016SA1 4 89A0 2048KB INTEL 28F016SA2 4 89A0 2048KB INTEL 28F016SA1 5 89A0 2048KB INTEL 28F016SA2 5 89A0 2048KB INTEL 28F016SAThe following example shows flash chip informationRouter# show slot chips20480K bytes of processor board PCMCIA Slot0 flash (Read/Write)Chip Bank Code Size Name1 1 89A0 2048KB INTEL 28F016SA2 1 89A0 2048KB INTEL 28F016SA1 2 89A0 2048KB INTEL 28F016SA2 2 89A0 2048KB INTEL 28F016SA1 3 89A0 2048KB INTEL 28F016SA2 3 89A0 2048KB INTEL 28F016SA1 4 89A0 2048KB INTEL 28F016SA2 4 89A0 2048KB INTEL 28F016SA1 5 89A0 2048KB INTEL 28F016SA2 5 89A0 2048KB INTEL 28F016SARelated Commands
show slot0:
To display information about the PCMCIA flash memory card's file system located in slot 0, use the show slot0: command in user EXEC or privileged EXEC mode.
show slot0: [all | chips | filesys]
Syntax Description
Command Modes
User EXEC
Privileged EXECCommand History
Usage Guidelines
Use the show slot0: command to display details about the files in a particular linear PCMCIA flash memory card of less than 20 MB and some 32 MB linear PCMCIA cards.
Note
For more information regarding file systems and flash cards, access the PCMCIA Filesystem Compatibility Matrix and Filesystem Information document at the following URL:
http://www.cisco.com/en/US/partner/products/hw/routers/ps341/products_tech_note09186a00800a7515.shtml
To see which flash cards are used in your router, use the show version command and look at the bottom portion of the output.
The following display indicates an ATA PCMCIA flash disk.
Router# show version...46976K bytes of ATA PCMCIA card at slot 0 (Sector size 512 bytes).The following display indicates a linear PCMCIA flash card with 20480K bytes of flash memory in card at slot 1 with a sector size of 128K.
Router# show version...20480K bytes of Flash PCMCIA card at slot 1 (Sector size 128K).Examples
The following example displays information about slot 0. The output is self-explanatory.
Router# show slot0:PCMCIA Slot0 flash directory:File Length Name/status1 11081464 c3660-bin-mz.123-9.3.PI5b[11081528 bytes used, 9627844 available, 20709372 total]20480K bytes of processor board PCMCIA Slot0 flash (Read/Write)Router# show slot0: allPartition Size Used Free Bank-Size State Copy Mode1 20223K 10821K 9402K 4096K Read/Write DirectPCMCIA Slot0 flash directory:File Length Name/statusaddr fcksum ccksum1 11081464 c3660-bin-mz.123-9.3.PI5b0x40 0x5EA3 0x5EA3[11081528 bytes used, 9627844 available, 20709372 total]20480K bytes of processor board PCMCIA Slot0 flash (Read/Write)Chip Bank Code Size Name1 1 89A0 2048KB INTEL 28F016SA2 1 89A0 2048KB INTEL 28F016SA1 2 89A0 2048KB INTEL 28F016SA2 2 89A0 2048KB INTEL 28F016SA1 3 89A0 2048KB INTEL 28F016SA2 3 89A0 2048KB INTEL 28F016SA1 4 89A0 2048KB INTEL 28F016SA2 4 89A0 2048KB INTEL 28F016SA1 5 89A0 2048KB INTEL 28F016SA2 5 89A0 2048KB INTEL 28F016SAThe following example shows flash chip information.Router# show slot0: chips20480K bytes of processor board PCMCIA Slot0 flash (Read/Write)Chip Bank Code Size Name1 1 89A0 2048KB INTEL 28F016SA2 1 89A0 2048KB INTEL 28F016SA1 2 89A0 2048KB INTEL 28F016SA2 2 89A0 2048KB INTEL 28F016SA1 3 89A0 2048KB INTEL 28F016SA2 3 89A0 2048KB INTEL 28F016SA1 4 89A0 2048KB INTEL 28F016SA2 4 89A0 2048KB INTEL 28F016SA1 5 89A0 2048KB INTEL 28F016SA2 5 89A0 2048KB INTEL 28F016SARelated Commands
show slot1:
To display information about the PCMCIA flash memory card's file system located in slot 1, use the show slot1: command in user EXEC or privileged EXEC mode.
show slot1: [all | chips | filesys]
Syntax Description
all
(Optional) Shows all possible flash system information for all PCMCIA flash cards in the system.
chips
(Optional) Shows flash chip information.
filesys
(Optional) Shows file system information.
Command Modes
User EXEC
Privileged EXECCommand History
Usage Guidelines
Use the show slot1: command to display details about the files in a particular linear PCMCIA flash memory card of less than 20 MB and some 32 MB linear PCMCIA cards located in slot 1.
Note
For more information regarding file systems and flash cards, access the PCMCIA Filesystem Compatibility Matrix and Filesystem Information document at the following URL:
http://www.cisco.com/en/US/partner/products/hw/routers/ps341/products_tech_note09186a00800a7515.shtml
To see which flash cards are used in your router, use the show version command and look at the bottom portion of the output.
The following display indicates an ATA PCMCIA flash disk.
Router# show version...46976K bytes of ATA PCMCIA card at slot 0 (Sector size 512 bytes).The following display indicates a linear PCMCIA flash card with 20480K bytes of flash memory in card at slot 1 with a sector size of 128K.
Router# show version...20480K bytes of Flash PCMCIA card at slot 1 (Sector size 128K).Examples
The following example displays information about slot 0 using the slot0: command form. The output is self-explanatory.Router# show slot1:PCMCIA Slot1 flash directory:File Length Name/status1 10907068 c3660-bin-mz.123-7.9.PI4[10907132 bytes used, 5739008 available, 16646140 total]16384K bytes of processor board PCMCIA Slot1 flash (Read/Write)Router# show slot1: allPartition Size Used Free Bank-Size State Copy Mode1 20223K 10821K 9402K 4096K Read/Write DirectPCMCIA Slot0 flash directory:File Length Name/statusaddr fcksum ccksum1 11081464 c3660-bin-mz.123-9.3.PI5b0x40 0x5EA3 0x5EA3[11081528 bytes used, 9627844 available, 20709372 total]20480K bytes of processor board PCMCIA Slot0 flash (Read/Write)Chip Bank Code Size Name1 1 89A0 2048KB INTEL 28F016SA2 1 89A0 2048KB INTEL 28F016SA1 2 89A0 2048KB INTEL 28F016SA2 2 89A0 2048KB INTEL 28F016SA1 3 89A0 2048KB INTEL 28F016SA2 3 89A0 2048KB INTEL 28F016SA1 4 89A0 2048KB INTEL 28F016SA2 4 89A0 2048KB INTEL 28F016SA1 5 89A0 2048KB INTEL 28F016SA2 5 89A0 2048KB INTEL 28F016SAThe following example shows flash chip information.Router# show slot1: chips20480K bytes of processor board PCMCIA Slot0 flash (Read/Write)Chip Bank Code Size Name1 1 89A0 2048KB INTEL 28F016SA2 1 89A0 2048KB INTEL 28F016SA1 2 89A0 2048KB INTEL 28F016SA2 2 89A0 2048KB INTEL 28F016SA1 3 89A0 2048KB INTEL 28F016SA2 3 89A0 2048KB INTEL 28F016SA1 4 89A0 2048KB INTEL 28F016SA2 4 89A0 2048KB INTEL 28F016SA1 5 89A0 2048KB INTEL 28F016SA2 5 89A0 2048KB INTEL 28F016SARelated Commands
show stacks
To monitor the stack usage of processes and interrupt routines, use the show stacks EXEC command.
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 privileged EXEC command.
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 108 describes the significant fields shown in the display.
show tcp
To display the status of TCP connections, use the show tcp EXEC command.
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 109 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 110 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 111 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 112 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 113 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 EXEC command.
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 114 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 EXEC command.
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 EXEC command.
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, use the show tech-support privileged EXEC command.
show tech-support [page] [password] [cef | ipmulticast | isis | mpls | ospf [process-ID | detail] | rsvp]
Syntax Description
Defaults
The output scrolls without page breaks.
Passwords and other security information are removed from the output.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:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Use of the optional cef, ipmulticast, ipc, isis, mpls , ospf, or rsvp keywords provides a way to display a number of show commands specific to a particular protocol or process in addition to the show commands listed previously.
For example, if your TAC support representative suspects that you may have a problem in your Cisco Express Forwarding (CEF) configuration, you may be asked to provide the output of the show tech-support cef command. The show tech-support [page] [password] cef command will display the output from the following commands in addition to the output for the standard show tech-support command:
•
•
•
•
•
•
•
•
•
•
Examples
For a sample display of the output from the show tech-support command, refer to the documentation for the show commands listed in the "Usage Guidelines" section.
Related Commands
test flash
To test Flash memory on MCI and envm Flash EPROM interfaces, use the test flash EXEC command.
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 EXEC command.
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 EXEC command. 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 privileged EXEC command.
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 115 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 116 describes the fields that are unique to the extended trace sequence, as shown in the display.
Table 117describes 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 EXEC command.
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 a system message. The trace command sends several probes at each TTL level and displays the round-trip time for each.
The trace command sends out one probe at a time. Each outgoing packet may result in one or two system messages. A "time exceeded" system message indicates that an intermediate router has seen and discarded the probe. A "destination unreachable" system message indicates that the destination node has received the probe and discarded it because it could not deliver the packet. If the timer goes off before a response comes in, trace prints an asterisk (*).
The trace command terminates when the destination responds, when the maximum TTL is exceeded, or when the user interrupts the trace with the escape sequence. By default, to invoke the escape sequence, type Ctrl-^ X by simultaneously pressing and releasing the Ctrl, Shift, and 6 keys, and then pressing the X key.
Common Trace Problems
Due to bugs in the IP implementation of various hosts and routers, the IP trace command may behave in unexpected ways.
Not all destinations will respond correctly to a probe message by sending back an "ICMP port unreachable" message. A long sequence of TTL levels with only asterisks, terminating only when the maximum TTL has been reached, may indicate this problem.
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 118 describes the significant fields shown in the display.
Table 119 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.
