![Troubleshooting and Fault Management Commands [12.2]](http://www.cisco.com/swa/i/icon_pdf.gif){kind=icon}
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
