Table Of Contents
Troubleshooting Commands
attach
clear logging
diag
exception core-file
exception dump
exception linecard
exception memory
exception protocol
exception region-size
exception spurious-interrupt
execute-on
logging
logging buffered
logging console
logging facility
logging history
logging history size
logging linecard
logging monitor
logging on
logging source-interface
logging synchronous
logging trap
ping (privileged)
ping (user)
service slave-log
service tcp-keepalives-in
service tcp-keepalives-out
service timestamps
show c2600 (Cisco 2600 series)
show c7200 (Cisco 7200 series)
show cls
show context (2600)
show context
show controllers (GRP image)
show controllers (line card image)
show controllers logging
show controllers tech-support
show debugging
show diag
show environment
show gsr
show gt64010 (Cisco 7200 series)
show logging
show logging history
show memory
show pci
show pci hardware
show processes
show processes memory
show protocols
show stacks
show subsys
show tcp
show tcp brief
show tdm connections
show tdm data
show tech-support
test flash
test interfaces
test memory
trace (privileged)
trace (user)
Troubleshooting Commands
This chapter describes the commands used to troubleshoot your router. To troubleshoot, you need to discover, isolate, and resolve the problems. You can discover problems with the system's monitoring commands, isolate problems with the system's test commands, and resolve problems with other commands, including debug.
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 the Router" chapter in the Cisco IOS Configuration Fundamentals Configuration Guide.
attach
To connect to a specific line card for the purpose of executing monitoring and maintenance commands on that line card only, use the attach privileged EXEC command. To exit from the Cisco IOS software image on the line card and return to the Cisco IOS image on the GRP card, use the exit command.
attach slot-number
Syntax Description
slot-number
|
Slot number of the line card you want to connect to. Slot numbers range from 0 to 11 for the Cisco 12012 and 0 to 7 for the Cisco 12008. If the slot number is omitted, you are prompted for the slot number.
|
Defaults
None
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
11.2 GS
|
This command was added to support the Cisco 12000 series Gigabit Switch Routers.
|
Usage Guidelines
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 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 command from the Cisco IOS software image on the line card.
Examples
The following example 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:
Entering Console for 4 Port Packet Over SONET OC-3c/STM-1 in Slot: 9
Type exit to end this session
Press RETURN to get started!
cef Cisco Express Forwarding
clock Display the system clock
context Show context information about recent crash(s)
history Display the session command history
hosts IP domain-name, lookup style, nameservers, and host table
ipc Interprocess communications commands
location Display the system location
sessions Information about Telnet connections
terminal Display terminal configuration parameters
users Display information about terminal lines
version System hardware and software status
Disconnecting from slot 9.
Connection Duration: 00:01:04
Note
Because not all statistics are maintained on the line cards, the output from some of the show commands might not be consistent.
Related Commands
Command
|
Description
|
attach shelf
|
Connects you to a specific (managed) shelf for the purpose of remotely executing commands on that shelf only.
|
execute-on slot
|
Executes commands remotely on a specific line card, or on all line card simultaneously.
|
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
Release
|
Modification
|
11.2
|
This command was introduced.
|
Examples
The following example clears the logging buffer:
Clear logging buffer [confirm]
Related Commands
Command
|
Description
|
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 (SFC), and on the Clock Scheduler Card (CSC) in Cisco 12000 series Gigabit Switch Routers, use the diag privileged EXEC command. To disable field diagnostics on a line card, use the no form of this command.
diag slot-number [halt | previous | post | verbose [wait] | wait]
no diag slot-number
Syntax Description
slot-number
|
Slot number of the line card you want to test. Slot numbers range from 0 to 11 for the Cisco 12012 and 0 to 7 for the Cisco 12008. Slot numbers for the CSC are 16 and 17 and for the FSC are18, 19, and 20.
|
halt
|
(Optional) Stops the field diagnostic testing on the line card.
|
previous
|
(Optional) Displays previous test results (if any) for the line card.
|
post
|
(Optional) Initiates a EPROM-based extended power-on self-test (EPOST) only. The EPOST test suite is not as comprehensive as the field diagnostics, and a pass/fail message is the only message displayed on the console.
|
verbose [wait]
|
(Optional) Enables the maximum status messages to be displayed on the console. By default, only the minimum status messages are displayed on the console. If you specify the optional wait keyword, the Cisco IOS software is not be automatically reloaded on the line card after the test completes successfully.
|
wait
|
(Optional) Stops the automatic reloading of the Cisco IOS software on the line card after the successful completion of the field diagnostic testing. If you use this keyword, you must use the microcode reload slot global configuration command, or manually remove and insert the line card (to power it up) in the slot so that the GRP will recognize the line card and download the Cisco IOS software image to the line card.
|
Defaults
No field diagnostics tests are performed on the line card.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
11.2 GS
|
This command was added to support the Cisco 12000 series Gigabit Switch Routers.
|
Usage Guidelines
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 quarter bandwidth. Bandwidth is not affected by GRP or line card diagnostics.
The field diagnostic software image is bundled with the Cisco IOS software and is downloaded automatically from the GRP to the target line card prior to testing.
Caution 
Performing field diagnostics on a line card stops all activity on the line card. Before the
diag EXEC command begins running diagnostics, you are prompted to confirm the request to perform field diagnostics on the line card.
In normal mode, if a test fails, the title of the failed test is displayed on the console. However, not all tests that are performed are displayed. To view all the tests that are performed, use the verbose keyword.
After all diagnostic tests are completed on the line card, a PASSED or TEST FAILURE message is displayed. If the line card sends a PASSED message, the Cisco IOS software image on the line card is automatically reloaded unless the wait keyword is specified. If the line card sends a TEST FAILURE message, the Cisco IOS software image on the line card is not automatically reloaded.
If you want to reload the line card after it fails diagnostic testing, use the microcode reload slot global configuration command.
Note
When you stop the field diagnostic test, the line card remains down (that is, in an unbooted state). In most cases, you stopped the testing because you need to remove the line card or replace the line card. If that is not the case, and you want to bring the line card back up (that is, online), you must use the microcode reload global configuration command or power cycle the line card.
If the line card fails the test, the line card is defective and should be replaced. In future releases this might not be the case because DRAM and SDRAM SIMM modules might be field replaceable units. For example, if the DRAM test failed you might only need to replace the DRAM on the line card.
For more information, refer to the Cisco 12000 series installation and configuration guides.
Examples
The following example shows 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.
Running Diags will halt ALL activity on the requested slot. [confirm]
Launching a Field Diagnostic for slot 3
Running DIAG config check
RUNNING DIAG download to slot 3 (timeout set to 400 sec.)
sending cmd FDIAG-DO ALL to fdiag in slot 3
(total/indiv. timeout set to 600/220 sec.)
Field Diagnostic ****PASSED**** for slot 3
Field Diag eeprom values: run 159 fial mode 0 (PASS) slot 3
last test failed was 0, error code 0
sending SHUTDOWN FDIAG_QUIT to fdiag in slot 3
The following example shows the output when field diagnostics are performed on the line card in slot 3 in verbose mode:
Running Diags will halt ALL activity on the requested slot. [confirm]
Launching a Field Diagnostic for slot 3
Running DIAG config check
RUNNING DIAG download to slot 3 (timeout set to 400 sec.)
sending cmd FDIAG-DO ALL to fdiag in slot 3
(total/indiv. timeout set to 600/220 sec.)
FDIAG_STAT_IN_PROGRESS: test #1 R5K Internal Cache
FDIAG_STAT_PASS test_num 1
FDIAG_STAT_IN_PROGRESS: test #2 Sunblock Ordering
FDIAG_STAT_PASS test_num 2
FDIAG_STAT_IN_PROGRESS: test #3 Dram Datapins
FDIAG_STAT_PASS test_num 3
Field Diags: FDIAG_STAT_DONE
Field Diagnostic ****PASSED**** for slot 3
Field Diag eeprom values: run 159 fial mode 0 (PASS) slot 3
last test failed was 0, error code 0
sending SHUTDOWN FDIAG_QUIT to fdiag in slot 3
Related Commands
Command
|
Description
|
microcode reload
|
Reloads the Cisco IOS image on a line card on the Cisco 7000 series with RSP7000, Cisco 7500 series, or Cisco 12000 series routers after all microcode configuration commands have been entered.
|
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 name
no exception core-file
Syntax Description
name
|
Name of the core dump file saved on the server.
|
Defaults
The core file is named hostname-core, where hostname is the name of the router.
Command Modes
Global configuration
Command History
Release
|
Modification
|
10.2
|
This command was introduced.
|
Usage Guidelines
Caution 
Use the
exception commands only under the direction of a technical support representative. Creating a core dump while the router is functioning in a network can disrupt network operation. The resulting binary file, which is very large, must be transferred to a TFTP, FTP, or rcp server and subsequently interpreted by technical personnel who have access to source code and detailed memory maps.
If you use TFTP to dump the core file to a server, the router will only dump the first 16 MB of the core file. If the 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
The following example 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:
exception dump 172.17.92.2
exception core-file dumpfile
Related Commands
Command
|
Description
|
exception dump
|
Causes the router to dump a core file to a particular server when the router crashes.
|
exception memory
|
Causes the router to create a core dump and reboot when certain memory size parameters are violated.
|
exception spurious-interrupt
|
Causes the router to create a core dump and reload after a specified number of spurious interrupts.
|
exception protocol
|
Configures the protocol used for core dumps.
|
ip ftp password
|
Specifies the password to be used for FTP connections.
|
ip ftp username
|
Configures the username for FTP connections.
|
exception dump
To configure the router to dump a core file to a particular server when the router crashes, use the exception dump global configuration command. To disable core dumps, use the no form of this command.
exception dump ip-address
no exception dump
Syntax Description
ip-address
|
IP address of the server that stores the core dump file.
|
Defaults
Disabled
Command Modes
Global configuration
Command History
Release
|
Modification
|
10.3
|
This command was introduced.
|
Usage Guidelines
Caution 
Use the
exception commands only under the direction of a technical support representative. Creating a core dump while the router is functioning in a network can disrupt network operation. The resulting binary file, which is very large, must be transferred to a TFTP, FTP, or rcp server and subsequently interpreted by technical personnel who have access to source code and detailed memory maps.
If you use TFTP to dump the core file to a server, the router will only dump the first 16 MB of the core file. If the 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
The following example configures a router to use FTP to dump a core file to the FTP server at 172.17.92.2 when it crashes:
exception dump 172.17.92.2
Related Commands
Command
|
Description
|
exception core-file
|
Specifies the name of the core dump file.
|
exception memory
|
Causes the router to create a core dump and reboot when certain memory size parameters are violated.
|
exception spurious-interrupt
|
Causes the router to create a core dump and reload after a specified number of spurious interrupts.
|
exception protocol
|
Configures the protocol used for core dumps.
|
ip ftp password
|
Specifies the password to be used for FTP connections.
|
ip ftp username
|
Configures the username for FTP connections.
|
ip rcmd remote-username
|
Configures the remote username to be used when requesting a remote copy using rcp.
|
exception linecard
To enable storing of crash information for a line card and optionally specify the type and amount of information stored, use the exception linecard global configuration command. To disable the storing of crash information for the line card, use the no form of this command.
exception linecard {all | slot slot-number} [corefile filename | main-memory size [k | m] |
queue-ram size [k | m] | rx-buffer size [k | m] | sqe-register-rx | sqe-register-tx | tx-buffer
size [k | m]]
no exception linecard
Syntax Description
all
|
Stores crash information for all line cards.
|
slot slot- number
|
Stores crash information for the line card in the specified slot. Slot numbers range from 0 to 11 for the Cisco 12012 and 0 to 7 for the Cisco 12008.
|
corefile filename
|
(Optional) Stores the crash information in the specified file in NVRAM. The default file name is hostname-core-slot-number (for example, c12012-core-8).
|
main-memory size
|
(Optional) Stores the crash information for the main memory on the line card and specify the size of the crash information. Size of the memory to store is 0 to 268435456.
|
queue-ram size
|
(Optional) Stores the crash information for the queue RAM memory on the line card and specify the size of the crash information. Size of the memory to store can be from 0 to 1048576.
|
rx-buffer size
tx-buffer size
|
(Optional) Stores the crash information for the receive and transmit buffer on the line card and specify the size of the crash information. Size of the memory to store can be from 0 to 67108864.
|
sqe-register-rx
sqe-register-tx
|
(Optional) Stores crash information for the receive or transmit silicon queueing engine registers on the line card.
|
k
m
|
(Optional) The k option multiplies the specified size by 1K (1024), and the m option multiplies the specified size by 1M (1024*1024).
|
Defaults
No crash information is stored for the line card.
If enabled with no options, the default is to store 256 MB of main memory.
Command Modes
Global configuration
Command History
Release
|
Modification
|
11.2 GS
|
This command was introduced.
|
Usage Guidelines
This command is currently supported only on Cisco 12000 series Gigabit Switch Routers.
Use the exception linecard global configuration command only when directed by a technical support representative and 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 
Use caution when enabling the
exception linecard global configuration command. Enabling all options could cause a large amount (150 to 250 MB) of crash information to be sent to the server.
Examples
The following example enables the storing of crash information for line card 8. By default, 256 MB of main memory is stored.
exception linecard slot 8
exception memory
To cause the router to create a core dump and reboot when certain memory size parameters are violated, use the exception memory global configuration command. To disable the rebooting and core dump, use the no form of this command.
exception memory {fragment size | minimum size}
no exception memory {fragment | minimum}
Syntax Description
fragment size
|
The minimum contiguous block of memory in the free pool, in bytes.
|
minimum size
|
The minimum size of the free memory pool, in bytes.
|
Defaults
Disabled
Command Modes
Global configuration
Command History
Release
|
Modification
|
10.3
|
This command was introduced.
|
Usage Guidelines
Caution 
Use the
exception commands only under the direction of a technical support representative. Creating a core dump while the router is functioning in a network can disrupt network operation. The resulting binary file, which is very large, must be transferred to a TFTP, FTP, or rcp server and subsequently interpreted by technical personnel who have access to source code and detailed memory maps.
This command is useful to troubleshoot memory leaks.
The size is checked every 60 seconds. If you enter a size that is greater than the free memory, a core dump and router reload is generated after 60 seconds.
The exception dump command must be configured in order to generate a core dump file. If the exception dump command is not configured, the router reloads without generating a core dump.
Examples
The following example configures the router to monitor the free memory. If the amount of free memory falls below 250,000 bytes, the router will dump the core file and reload.
exception dump 131.108.92.2
exception core-file memory.overrun
exception memory minimum 250000
Related Commands
Command
|
Description
|
exception core-file
|
Specifies the name of the core dump file.
|
exception dump
|
Configures the router to dump a core file to a particular server when the router crashes.
|
exception protocol
|
Configures the protocol used for core dumps.
|
exception region-size
|
Specifies the size of the region for exception-time memory pool
|
ip ftp password
|
Specifies the password to be used for FTP connections.
|
ip ftp username
|
Configures the username for FTP connections.
|
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
|
Use FTP for core dumps.
|
rcp
|
Use rcp for core dumps.
|
tftp
|
Use TFTP for core dumps. This is the default.
|
Defaults
TFTP
Command Modes
Global configuration
Command History
Release
|
Modification
|
10.3
|
This command was introduced.
|
Usage Guidelines
Caution 
Use the
exception commands only under the direction of a technical support representative. Creating a core dump while the router is functioning in a network can disrupt network operation. The resulting binary file, which is very large, must be transferred to a TFTP, FTP, or rcp server and subsequently interpreted by technical personnel who have access to source code and detailed memory maps.
If you use TFTP to dump the core file to a server, the router will only dump the first 16 MB of the core file. If the 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
The following example configures a router to use FTP to dump a core file to the FTP server at 172.17.92.2 when it crashes:
exception dump 172.17.92.2
Related Commands
Command
|
Description
|
exception core-file
|
Specifies the name of the core dump file.
|
exception dump
|
Causes the router to dump a core file to a particular server when the router crashes.
|
exception memory
|
Causes the router to create a core dump and reboot when certain memory size parameters are violated.
|
exception spurious-interrupt
|
Causes the router to create a core dump and reload after a specified number of spurious interrupts.
|
ip ftp password
|
Specifies the password to be used for FTP connections.
|
ip ftp username
|
Configures the username for FTP connections.
|
exception region-size
To specify the size of the region for exception-time memory pool, use the exception region-size global configuration command. To use the default region size, use the no form of this command.
exception region-size size
no exception region-size
Syntax Description
size
|
(Required) The size of the region for exception-time memory pool.
|
Defaults
16384 bytes.
Command Modes
Global configuration
Command History
Release
|
Modification
|
10.3
|
This command was introduced.
|
Usage Guidelines
Caution 
Use the
exception commands only under the direction of a technical support representative. Creating a core dump while the router is functioning in a network can disrupt network operation. The resulting binary file, which is very large, must be transferred to a TFTP, FTP, or rcp server and subsequently interpreted by technical personnel who have access to source code and detailed memory maps.
The exception region-size command is used to define a small amount of memory to serve as a fallback pool when the processor memory pool is marked corrupt. The exception memory command must be used to allocate memory to perform a core dump.
Examples
The following example sets the region size at 1024:
Router# exception region-size 1024
Related Commands
Command
|
Description
|
exception core-file
|
Specifies the name of the core dump file.
|
exception dump
|
Configures the router to dump a core file to a particular server when the router crashes.
|
exception memory
|
Causes the router to create a core dump and reboot when certain memory size parameters are violated.
|
exception protocol
|
Configures the protocol used for core dumps.
|
ip ftp password
|
Specifies the password to be used for FTP connections.
|
ip ftp username
|
Configures the username for FTP connections.
|
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
|
Number from 1 to 4294967295 that indicates the maximum number of spurious interrupts to include in the core dump before reloading.
|
Defaults
Disabled
Command Modes
Global configuration
Command History
Release
|
Modification
|
10.3
|
This command was introduced.
|
Usage Guidelines
Caution 
Use the
exception commands only under the direction of a technical support representative. Creating a core dump while the router is functioning in a network can disrupt network operation. The resulting binary file, which is very large, must be transferred to a TFTP, FTP, or rcp server and subsequently interpreted by technical personnel who have access to source code and detailed memory maps.
If you use TFTP to dump the core dump file to a server, the router will only dump the first 16 MB of the file. If the 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
The following example configures a router to create a core dump with a limit of 2 spurious interrupts:
Router# exception spurious-interrupt 2
Related Commands
Command
|
Description
|
exception core-file
|
Specifies the name of the core dump file.
|
ip ftp password
|
Specifies the password to be used for FTP connections.
|
ip ftp username
|
Configures the user name for FTP connections.
|
execute-on
To execute commands on a line card, use the execute-on privileged EXEC command.
execute-on {slot slot-number | all | master} command
Syntax Description
slot slot-number
|
Executes the command on the line card in the specified slot. Slot numbers can be chosen from the following ranges:
• Cisco 12012: 0 to 11
• Cisco 12008: 0 to 7
• Cisco AS5800: 0 to 13
|
all
|
Executes the command on all line cards.
|
master
|
(AS5800 only) Executes the designated command on a Dial Shelf Controller (DSC). Do not use this option; it is used for technical support troubleshooting only.
|
command
|
Cisco IOS command to remotely execute on the line card.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
11.2 GS
|
This command was introduced to support Cisco 12000 series Gigabit Switch Routers.
|
11.3(2)AA
|
Support for this command was added to the Cisco AS58000 Universal Access Server.
|
Usage Guidelines
Use this command to execute a command on one or all line cards to monitor and maintain information on one or more line cards (for example, a line card in a specified slot on a dial shelf). This allows you to issue commands remotely; that is, to issue commands without having to log on 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 on to each on 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.
Note
This command is useful when used with show commands (such as show version), as you can verify and troubleshoot the features found only on a specific line card. Please note, however, that because not all statistics are maintained on the line cards, the output from some of the show commands might not be consistent.
Cisco 12000 GSR Guidelines and Restrictions
You can use the execute-on privileged EXEC command only from Cisco IOS software running on the GRP card.
Timesaver
Though you can use the attach privileged EXEC command to execute commands on a specific line card, using the execute-on slot command saves you some steps. For example, first you must use the attach command to connect you to the Cisco IOS software running on the line card, next you must issue the command, and finally you must disconnect from the line card to return to the Cisco IOS software running on the GRP card. With the execute-on slot command, you can perform three steps with one command. In addition, the execute-on all command allows you to perform the same command on all line cards simultaneously.
Cisco AS5800 Guidelines and Restrictions
The purpose of the command is to conveniently enable certain commands to be remotely executed on the dial shelf cards from the router without connecting to each line card. This is the recommended procedure, because it avoids the possibility of adversely affecting a good configuration of a line card in the process. The command execute-on does not give access to every IOS command available on the Cisco AS5800. 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.
Note
Do not use this command to change configurations on dial shelf cards, since such changes will not be reflected in the router shelf.
Using this command makes it possible to accumulate inputs for inclusion in the show tech-support command.
The master form of the command can run a designated command remotely on the router from the DSC card. However, using the console on the DSC is not recommended. It is used for technical support troubleshooting only.
The show tech-support command for each dial shelf card is bundled into the router shelf's show tech-support command via the execute-on facility.
The execute-on command also support interactive commands such as:
router: execute-on slave slot slot ping
The execute-on command has the same limitations/restrictions as a vty telnet client has, that is, it cannot reload DSC using:
router: execute-on slave slot slot reload
You can use the execute-on command to enable remote execution of the following partial list of commands:
•
debug dsc clock
•
show context
•
show diag
•
show environment
•
show dsc clock
•
show dsi
•
show dsip
•
show tech-support
Examples
The following example 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) =======
lcpos_instance struct 6033A6E0
RX POS ASIC addr space 12000000
TX POS ASIC addr space 12000100
SUNI framer addr space 12000400
CRC16 enabled, HDLC enc, int clock
lcpos_instance struct 6033CEC0
RX POS ASIC addr space 12000000
TX POS ASIC addr space 12000100
SUNI framer addr space 12000600
CRC32 enabled, HDLC enc, int clock
lcpos_instance struct 6033F6A0
RX POS ASIC addr space 12000000
TX POS ASIC addr space 12000100
SUNI framer addr space 12000800
CRC32 enabled, HDLC enc, int clock
lcpos_instance struct 60341E80
RX POS ASIC addr space 12000000
TX POS ASIC addr space 12000100
SUNI framer addr space 12000A00
CRC32 enabled, HDLC enc, ext clock
Related Commands
Command
|
Description
|
attach
|
Connects you to a specific line card for the purpose of executing commands using the Cisco IOS software image on that line card.
|
logging
To log messages to a syslog server host, use the logging global configuration command. The no form of this command deletes the syslog server with the specified address from the list of syslogs.
logging host
no logging host
Syntax Description
host
|
Name or IP address of the host to be used as a syslog server.
|
Defaults
No messages are logged to a syslog server host.
Command Modes
Global configuration
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
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
The following example logs messages to a host named johnson:
Related Commands
Command
|
Description
|
logging trap
|
Limits messages logged to the syslog servers based on severity. The command limits the logging of error messages sent to syslog servers to only those messages at the specified level.
|
logging buffered
To limit messages logged to an internal buffer based on severity, use the logging buffered global configuration command. The no form of this command cancels the use of the buffer. The default form of this command returns the buffer size to the default size.
logging buffered [size | level]
no logging buffered
default logging buffered
Syntax Description
size
|
(Optional) Size of the buffer from 4096 to 4294967295 bytes. The default size varies by platform.
|
level
|
Limits the logging of messages to the buffer to a specified level. You can enter the level number or level name. See Table 63 for a list of the level arguments.
|
Defaults
For most platforms, the Cisco IOS software logs messages to the internal buffer.
Command Modes
Global configuration
Command History
Release
|
Modification
|
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 63 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 command default logging buffered resets the buffer size to the default for the platform.
To display the messages that are logged in the buffer, use the EXEC command show logging. The first message displayed is the oldest message in the buffer.
The EXEC command show logging displays the addresses and levels associated with the current logging setup, as well as any other logging statistics.
Table 63 Logging Buffered Error Message Logging Priorities
Level Arguments
|
Level
|
Description
|
Syslog Definition
|
emergencies
|
0
|
System unusable
|
LOG_EMERG
|
alerts
|
1
|
Immediate action needed
|
LOG_ALERT
|
critical
|
2
|
Critical conditions
|
LOG_CRIT
|
errors
|
3
|
Error conditions
|
LOG_ERR
|
warnings
|
4
|
Warning conditions
|
LOG_WARNING
|
notifications
|
5
|
Normal but significant condition
|
LOG_NOTICE
|
informational
|
6
|
Informational messages only
|
LOG_INFO
|
debugging
|
7
|
Debugging messages
|
LOG_DEBUG
|
The following example enables logging to an internal buffer:
Related Commands
Command
|
Description
|
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. The no form of this command disables logging to the console terminal.
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 64 for a list of the level arguments.
|
Defaults
debugging
Command Modes
Global configuration
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
Usage Guidelines
Specifying a level causes messages at that level and numerically lower levels to be displayed at the console terminal.
The EXEC command show logging displays the addresses and levels associated with the current logging setup, as well as any other logging statistics. Table 64 shows descriptions for the various logging levels.
Table 64 Logging Console Error Message Logging Priorities
Level Arguments
|
Level
|
Description
|
Syslog Definition
|
emergencies
|
0
|
System unusable
|
LOG_EMERG
|
alerts
|
1
|
Immediate action needed
|
LOG_ALERT
|
critical
|
2
|
Critical conditions
|
LOG_CRIT
|
errors
|
3
|
Error conditions
|
LOG_ERR
|
warnings
|
4
|
Warning conditions
|
LOG_WARNING
|
notifications
|
5
|
Normal but significant condition
|
LOG_NOTICE
|
informational
|
6
|
Informational messages only
|
LOG_INFO
|
debugging
|
7
|
Debugging messages
|
LOG_DEBUG
|
The effect of the log keyword with the IP access list (extended) 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
The following example changes the level of messages displayed to the console terminal to alerts, which means alerts and emergencies are displayed:
Related Commands
Command
|
Description
|
logging facility
|
Configures the syslog facility in which error messages are sent.
|
access-list (extended)
|
Defines an extended XNS access list.
|
logging facility
To configure the syslog facility in which error 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 Table 56 for the facility-type arguments.
|
Defaults
local7
Command Modes
Global configuration
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
Usage Guidelines
Table 65 describes the acceptable options for the facility-type arguments.
Table 65 logging facility facility-type Arguments
Arguments
|
Description
|
auth
|
Authorization system
|
cron
|
Cron facility
|
daemon
|
System daemon
|
kern
|
Kernel
|
local0-7
|
Reserved for locally defined messages
|
lpr
|
Line printer system
|
mail
|
Mail system
|
news
|
USENET news
|
sys9
|
System use
|
sys10
|
System use
|
sys11
|
System use
|
sys12
|
System use
|
sys13
|
System use
|
sys14
|
System use
|
syslog
|
System log
|
user
|
User process
|
uucp
|
UNIX-to-UNIX copy system
|
Examples
The following example configures the syslog facility to the kernel facility type:
Related Commands
Command
|
Description
|
logging console
|
Limits messages logged to the console based on severity.
|
logging history
To limit syslog messages sent to the router's history table and the Simple Network Management Protocol network management station based on severity, use the logging history global configuration command. The no form of this command returns the logging of syslog messages to the default level.
logging history [level]
no logging history
Syntax Description
level
|
Limits the messages saved in the history table and sent to the SNMP network management station to the specified set of levels. You can enter the level number or level name. See Table 66 for a list of the level arguments.
|
Defaults
Logging of error messages of severity levels 0 through 4 (emergency, alert, critical, error, and warning levels)
Command Modes
Global configuration
Command History
Release
|
Modification
|
11.2
|
This command was introduced.
|
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 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 critical (3), alerts (2), and emergencies (1) messages to be stored to the history table and sent to the SNMP network management station.. Table 66 provides a description of logging severity levels, and the arguments used in logging history command syntax. Note that you can use the level name or the level number as the level argument in this command.
Table 66 Error Message Logging Priorities for History Table and SNMP Server
Severity Level Name
|
Severity Level Number
|
Description
|
Syslog Definition
|
emergencies
|
0
|
System unusable
|
LOG_EMERG
|
alerts
|
1
|
Immediate action needed
|
LOG_ALERT
|
critical
|
2
|
Critical conditions
|
LOG_CRIT
|
errors
|
3
|
Error conditions
|
LOG_ERR
|
warnings
|
4
|
Warning conditions
|
LOG_WARNING
|
notifications
|
5
|
Normal but significant condition
|
LOG_NOTICE
|
informational
|
6
|
Informational messages only
|
LOG_INFO
|
debugging
|
7
|
Debugging messages
|
LOG_DEBUG
|
Examples
In the following example, the system is initially configured to the default of saving severity level 4 or higher. The logging history 1 command is used to configure the system to save only level 1 (alert) and level 0 (emergency) messages to the logging history table. The configuration is then confirmed using the show logging history command.
Router#show logging history
Syslog History Table:10 maximum table entries,
! The following line shows that system-error-message-logging is set to the
! default level of "warnings" (4).
saving level warnings or higher
23 messages ignored, 0 dropped, 0 recursion drops
SNMP notifications not enabled
entry number 2 : LINK-3-UPDOWN
Interface FastEthernet0, changed state to up
Router#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Router(config)#logging history 1
4w0d: %SYS-5-CONFIG_I: Configured from console by console
Router#show logging history
Syslog History Table:1 maximum table entries,
! The following line indicates that `logging history level 1' is configured.
saving level alerts or higher
18 messages ignored, 0 dropped, 0 recursion drops
SNMP notifications not enabled
entry number 2 : LINK-3-UPDOWN
Interface FastEthernet0, changed state to up
Related Commands
Command
|
Description
|
logging history size
|
Changes the number of syslog messages stored in the router's history table.
|
show logging history
|
Displays the contents of syslog history table.
|
snmp-server host
|
Specifies the recipient of an SNMP notification operation.
|
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. The no form of this command returns the number of messages to the default value.
logging history size number
no logging history size
Syntax Description
number
|
Number from 1 to 500 that indicates the maximum number of messages stored in the history table.
|
Defaults
One message
Command Modes
Global configuration
Command History
Release
|
Modification
|
11.2
|
This command was introduced.
|
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
The following example sets the number of messages stored in the history table to 20:
Router(config)# logging history size 20
Related Commands
Command
|
Description
|
logging history
|
Limits syslog messages sent to the router's history table and the SNMP network management station based on severity.
|
show logging
|
Displays the state of logging (syslog).
|
logging linecard
To log messages to an internal buffer on a line card, use the logging linecard global configuration command. To cancel the use of the internal buffer on the line cards, use the no form of this command.
logging linecard [size | level]
no logging linecard
Syntax Description
size
|
(Optional) Size of the buffer used for each line card. The range is 4096 to 65536 bytes. The default is 8 KB.
|
level
|
(Optional) 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 67 for a list of the level arguments.
|
Defaults
The Cisco IOS software logs messages to the internal buffer on the GRP card.
Command Modes
Global configuration
Command History
Release
|
Modification
|
11.2 GS
|
This command was added to support the Cisco 12000 series Gigabit Switch Routers.
|
Usage Guidelines
Specifying a message level causes messages at that level and numerically lower levels to be stored in the internal buffer on the line cards.
Table 67 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 67 Error Levels: Name/Number CLI Arguments
Severity Level Name
|
Severity Level Number
|
Description
|
Syslog Definition
|
emergencies
|
0
|
System unusable
|
LOG_EMERG
|
alerts
|
1
|
Immediate action needed
|
LOG_ALERT
|
critical
|
2
|
Critical conditions
|
LOG_CRIT
|
errors
|
3
|
Error conditions
|
LOG_ERR
|
warnings
|
4
|
Warning conditions
|
LOG_WARNING
|
notifications
|
5
|
Normal but significant condition
|
LOG_NOTICE
|
informational
|
6
|
Informational messages only
|
LOG_INFO
|
debugging
|
7
|
Debugging messages
|
LOG_DEBUG
|
To display the messages that are logged in the buffer, use the EXEC command show logging slot. 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. Error messages at the warning, error, critical, alert, and emergency level will be logged.
Router(config)# logging linecard warnings
Related Commands
Command
|
Description
|
clear logging
|
Clears messages from the logging buffer.
|
show logging
|
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. The no form of this command disables logging to terminal lines other than the console line.
logging monitor level
no logging monitor
Syntax Description
level
|
Limits the logging of messages logged to the terminal lines (monitors) to a specified level. You can enter the level number or level name. See Table 68 for a list of the level arguments.
|
Defaults
debugging
Command Modes
Global configuration
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
Usage Guidelines
Specifying a level causes messages at that level and numerically lower levels to be displayed to the monitor.
Table 68 Logging Monitor Error Message Logging Priorities
Level Arguments
|
Level
|
Description
|
Syslog Definition
|
emergencies
|
0
|
System unusable
|
LOG_EMERG
|
alerts
|
1
|
Immediate action needed
|
LOG_ALERT
|
critical
|
2
|
Critical conditions
|
LOG_CRIT
|
errors
|
3
|
Error conditions
|
LOG_ERR
|
warnings
|
4
|
Warning conditions
|
LOG_WARNING
|
notifications
|
5
|
Normal but significant condition
|
LOG_NOTICE
|
informational
|
6
|
Informational messages only
|
LOG_INFO
|
debugging
|
7
|
Debugging messages
|
LOG_DEBUG
|
The following example specifies that only messages of the levels errors, critical, alerts, and emergencies be displayed on terminals:
Related Commands
Command
|
Description
|
terminal monitor
|
Displays debug command output and system error messages for the current terminal and session.
|
logging on
To control logging of error messages, use the logging on global configuration command. This command sends debug or error messages to a logging process, which logs messages to designated locations asynchronously to the processes that generated the messages. The no form of this command disables the logging process.
logging on
no logging on
Syntax Description
This command has no arguments or keywords.
Defaults
The Cisco IOS software sends messages to the asynchronous logging process.
Command Modes
Global configuration
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
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 commands. However, if the logging on command is disabled (using the no longing on form of this command), no messages will be sent to these destinations. Only the console will receive messages.
Additionally, the logging process logs messages to the console and the various destinations after the processes that generated them have completed. When the logging process is disabled, messages are displayed on the console as soon as they are produced, often appearing in the middle of command output.
Caution 
Disabling the logging on command will significantly slow down the router. Any process generating debug or error messages will wait until the messages have been displayed on the console before continuing.
The logging synchronous command also affects the displaying of messages to the console. When the logging synchronous command is enabled, messages will only appear after the user types a carriage return.
Examples
The following example shows command output and message output when logging is enabled. The ping process finishes before any of the logging information is printed to the console (or any other destination).
Router(config)# logging on
%SYS-5-CONFIG_I: Configured from console by console
Type 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 ms
IP: s=172.21.96.41 (local), d=172.16.1.129 (Ethernet1/0), len 100, sending
IP: s=171.69.1.129 (Ethernet1/0), d=172.21.96.41, len 114, rcvd 1
IP: s=172.21.96.41 (local), d=172.16.1.129 (Ethernet1/0), len 100, sending
IP: s=171.69.1.129 (Ethernet1/0), d=172.21.96.41, len 114, rcvd 1
IP: s=172.21.96.41 (local), d=172.16.1.129 (Ethernet1/0), len 100, sending
IP: s=171.69.1.129 (Ethernet1/0), d=172.21.96.41, len 114, rcvd 1
IP: s=172.21.96.41 (local), d=172.16.1.129 (Ethernet1/0), len 100, sending
IP: s=171.69.1.129 (Ethernet1/0), d=172.21.96.41, len 114, rcvd 1
IP: s=172.21.96.41 (local), d=172.16.1.129 (Ethernet1/0), len 100, sending
IP: s=171.69.1.129 (Ethernet1/0), d=172.21.96.41, len 114, rcvd 1
In the next example, logging is disabled. The message output is displayed as messages are generated, causing the debug messages to be interspersed with the message "Type escape sequence to abort."
Router(config)# no logging on
%SYS-5-CONFIG_I: Configured from console by console
IP: s=172.21.96.41 (local), d=172.16.1.129 (Ethernet1/0), len 100, sendingTyp
IP: s=171.69.1.129 (Ethernet1/0), d=172.21.96.41, len 114, rcvd 1e
IP: s=172.21.96.41 (local), d=172.16.1.129 (Ethernet1/0), len 100, sending esc
IP: s=171.69.1.129 (Ethernet1/0), d=172.21.96.41, len 114, rcvd 1
IP: s=172.21.96.41 (local), d=172.16.1.129 (Ethernet1/0), len 100, sendingape
IP: s=171.69.1.129 (Ethernet1/0), d=172.21.96.41, len 114, rcvd 1
IP: s=172.21.96.41 (local), d=172.16.1.129 (Ethernet1/0), len 100, sendingse
IP: s=171.69.1.129 (Ethernet1/0), d=172.21.96.41, len 114, rcvd 1
IP: s=172.21.96.41 (local), d=172.16.1.129 (Ethernet1/0), len 100, sendingquen
IP: s=171.69.1.129 (Ethernet1/0), d=172.21.96.41, len 114, rcvd 1ce to abort.
Sending 5, 100-byte ICMP Echos to 172.16.1.129, timeout is 2 seconds:
Success rate is 100 percent (5/5), round-trip min/avg/max = 152/152/156 ms
Related Commands
Command
|
Description
|
logging
|
Logs messages to a syslog server host.
|
logging buffered
|
Logs messages to an internal buffer.
|
logging monitor
|
Limits messages logged to the terminal lines (monitors) based on severity.
|
logging synchronous
|
Synchronizes unsolicited messages and debug output with solicited Cisco IOS software output and prompts for a specific console port line, auxiliary port line, or virtual terminal line.
|
logging source-interface
To specify the source IP address of syslog packets, use the logging source-interface global configuration command. Use the no form of this command to remove the source designation.
logging source-interface type number
no logging source-interface
Syntax Description
type
|
Interface type.
|
number
|
Interface number.
|
Defaults
No interface is specified.
Command Modes
Global configuration
Command History
Release
|
Modification
|
11.2
|
This command was introduced.
|
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
The following example specifies that the IP address for Ethernet interface 0 is the source IP address for all syslog messages:
logging source-interface ethernet 0
The following example specifies that the IP address for Ethernet interface 2/1 on a Cisco 7000 series router is the source IP address for all syslog messages:
logging source-interface ethernet 2/1
Related Commands
Command
|
Description
|
logging
|
Logs messages to a syslog server host.
|
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 virtual terminal line, use the logging synchronous line configuration command. Use the no form of this command to disable synchronization of unsolicited messages and debug output.
logging synchronous [level severity-level | all] [limit number-of-buffers]
no logging synchronous [level severity-level | all] [limit number-of-buffers]
Syntax Description
level severity-level
|
(Optional) Specifies the message severity level. Messages with a severity level equal to or higher than this value are printed asynchronously. Low numbers indicate greater severity and high numbers indicate lesser severity. The default value is 2.
|
all
|
(Optional) Specifies that all messages are printed asynchronously, regardless of the severity level.
|
limit number-of-buffers
|
(Optional) Specifies the number of buffers to be queued for the terminal after which new messages are dropped. The default value is 20.
|
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
Release
|
Modification
|
10.0
|
This command was introduced.
|
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. This is 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 
By configuring abnormally large message-queue limits and setting the terminal to "terminal monitor" on a terminal that is accessible to intruders, you expose yourself to "denial of service" attacks. An intruder could carry out the attack by putting the terminal in synchronous output mode, making a Telnet connection to a remote host, and leaving the connection idle. This could cause large numbers of messages to be generated and queued, and these messages would consume all available RAM. Although unlikely to occur, you should guard against this type of attack through proper configuration.
Examples
The following example identifies line 4 and enables synchronous logging for line 4 with a severity level of 6. Then the example identifies another line, line 2, and enables synchronous logging for line 2 with a severity level of 7 and specifies a maximum number of buffers to be 70000.
line 4
logging synchronous level 6
logging synchronous level 7 limit 70000
Related Commands
Command
|
Description
|
line
|
Identifies a specific line for configuration and starts the line configuration command collection mode.
|
logging on
|
Controls logging of error messages. This command sends debug or error messages to a logging process, which logs messages to designated locations asynchronously to the processes that generated the messages.
|
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 error messages sent to syslog servers to only those messages at the specified level. Use the no form of this command to disable logging to syslog servers.
logging trap level
no logging trap
Syntax Description
level
|
Limits the logging of messages to the syslog servers to a specified level. You can enter the level number or level name. See Table 69 for a list of the level arguments.
|
Defaults
Informational
Command Modes
Global configuration
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
Usage Guidelines
The EXEC command show logging 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, there are four categories of messages generated by the software, as follows:
•
Error messages about software or hardware malfunctions at the LOG_ERR level.
•
Output for the debug commands at the LOG_WARNING level.
•
Interface up/down transitions and system restarts at the LOG_NOTICE level.
•
Reload requests and low process stacks are at the LOG_INFO level.
Use the logging and logging trap commands to send messages to a UNIX syslog server.
Table 69 Logging Trap Error Message Logging Priorities
Level Arguments
|
Level
|
Description
|
Syslog Definition
|
emergencies
|
0
|
System unusable
|
LOG_EMERG
|
alerts
|
1
|
Immediate action needed
|
LOG_ALERT
|
critical
|
2
|
Critical conditions
|
LOG_CRIT
|
errors
|
3
|
Error conditions
|
LOG_ERR
|
warnings
|
4
|
Warning conditions
|
LOG_WARNING
|
notifications
|
5
|
Normal but significant condition
|
LOG_NOTICE
|
informational
|
6
|
Informational messages only
|
LOG_INFO
|
debugging
|
7
|
Debugging messages
|
LOG_DEBUG
|
The following example logs messages to a host named johnson:
logging johnson
logging trap notifications
Related Commands
Command
|
Description
|
logging
|
Logs messages to a syslog server host.
|
ping (privileged)
To diagnose basic network connectivity on Apollo, AppleTalk, Connectionless Network Service (CLNS), DECnet, IP, Novell IPX, VINES, or XNS networks, use the ping privileged EXEC command.
ping [protocol | tag] {host-name | system-address} [data [hex-data-pattern] | df-bit | repeat
[repeat-count] | size [datagram-size] | source [source-address | async | bvi | ctunnel | dialer |
ethernet | fastEthernet | lex | loopback | multilink | null | port-channel | tunnel | vif |
virtual-template | virtual-tokenring | xtagatm] | timeout [seconds] | validate]
Syntax Description
protocol
|
(Optional) Protocol keyword, one of apollo, appletalk, clns, decnet, ip, ipx, srb, vines, or xns.
|
tag
|
(Optional) Specifies a tag encapsulated IP ping.
|
host-name
|
Host name of the system to ping.
|
system-address
|
Address of the system to ping.
|
data
|
(Optional) Specifies the data pattern.
|
hex-data-pattern
|
(Optional) Range is from 0 to FFFF.
|
df-bit
|
(Optional) Enables the "do-not-fragment" bit in the IP header.
|
repeat
|
(Optional) Specifies the number of pings sent. The default is 5.
|
repeat-count
|
(Optional) Range is from 1 to 2147483647.
|
size
|
(Optional) Specifies the datagram size. Datagram size is the number of bytes in each ping.
|
datagram-size
|
(Optional) Range is from 40 to 18024.
|
source
|
(Optional) Specifies the source address or name.
|
source-address
|
(Optional)Source address or name.
|
async
|
(Optional) Asynchronous interface.
|
bvi
|
(Optional) Bridge-Group Virtual Interface.
|
ctunnel
|
(Optional) CTunnel interface.
|
dialer
|
(Optional) Dialer interface.
|
ethernet
|
(Optional) Ethernet IEEE 802.3.
|
fastEthernet
|
(Optional) FastEthernet IEEE 802.3.
|
lex
|
(Optional) Lex interface.
|
loopback
|
(Optional) Loopback interface.
|
multilink
|
(Optional) Multilink-group interface.
|
null
|
(Optional) Null interface.
|
port-channel
|
(Optional) Ethernet channel of interfaces.
|
tunnel
|
(Optional) Tunnel interface.
|
vif
|
(Optional) PGM Multicast Host interface.
|
virtual-template
|
(Optional) Virtual Template interface.
|
virtual-tokenring
|
(Optional) Virtual TokenRing.
|
xtagatm
|
(Optional) Extended Tag ATM interface.
|
timeout
|
(Optional) Specifies the timeout interval in seconds. The default is 2 seconds.
|
seconds
|
(Optional) Range is from 0 to 3600.
|
validate
|
(Optional) Validates the reply data.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
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 70 describes the test characters that the ping facility sends.
Table 70 ping Test Characters
Character
|
Description
|
!
|
Each exclamation point indicates receipt of a reply.
|
.
|
Each period indicates that the network server timed out while waiting for a reply.
|
U
|
A destination unreachable error protocol data unit (PDU) was received.
|
C
|
A congestion experienced packet was received.
|
I
|
User interrupted test.
|
?
|
Unknown packet type.
|
&
|
Packet lifetime exceeded.
|
Note
Not all protocols require hosts to support pings. For some protocols, the pings are Cisco-defined and are only answered by another Cisco router.
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:
Target IP address: 192.168.7.27
Sweep range of sizes [n]:
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 192.168.7.27, timeout is 2 seconds:
Success rate is 100 percent, round-trip min/avg/max = 1/2/4 ms
Table 71 describes the default ping fields shown in the display.
Table 71 ping Field Descriptions
Field
|
Description
|
Protocol [ip]:
|
Prompts for a supported protocol. Enter appletalk, clns, ip, novell, apollo, vines, decnet, or xns. The default is IP.
|
Target IP address:
|
Prompts for the IP address or host name of the destination node you plan to ping. If you have specified a supported protocol other than IP, enter an appropriate address for that protocol here. The default is none.
|
Repeat count [5]:
|
Prompts for the number of ping packets that will be sent to the destination address. The default is 5 packets.
|
Datagram size [100]:
|
Prompts for the size of the ping packet (in bytes). The default is 100 bytes.
|
Timeout in seconds [2]:
|
Prompts for the timeout interval. The default is 2 seconds.
|
Extended commands [n]:
|
Specifies whether a series of additional commands appears.
|
Sweep range of sizes [n]:
|
Allows you to vary the sizes of the echo packets being sent. This capability is useful for determining the minimum sizes of the MTUs configured on the nodes along the path to the destination address. Packet fragmentation contributing to performance problems can then be reduced.
|
!!!!!
|
Each exclamation point (!) indicates receipt of a reply. A period (.) indicates that the network server timed out while waiting for a reply. Other characters may appear in the ping output display, depending on the protocol type.
|
Success rate is 100 percent
|
Indicates the percentage of packets successfully echoed back to the router. Anything less than 80 percent is usually considered problematic.
|
round-trip min/avg/max = 1/2/4 ms
|
Indicates the round-trip travel time intervals for the protocol echo packets, including minimum/average/maximum (in milliseconds).
|
Related Commands
Command
|
Description
|
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, CLNS, IP, Novell, Apollo, VINES, DECnet, or XNS networks, use the ping (packet internet groper) user EXEC command.
ping [protocol] {host | address}
Syntax Description
protocol
|
(Optional) Protocol keyword, one of apollo, appletalk, clns, decnet, ip, ipx, vines, or xns.
|
host
|
Host name of system to ping.
|
address
|
Address of system to ping.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
Usage Guidelines
The user-level ping feature provides a basic ping facility for users who 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 72 describes the test characters that the ping facility sends.
Table 72 ping Test Characters
Character
|
Description
|
!
|
Each exclamation point indicates receipt of a reply.
|
.
|
Each period indicates the network server timed out while waiting for a reply.
|
U
|
A destination unreachable error PDU was received.
|
C
|
A congestion experienced packet was received.
|
I
|
User interrupted test.
|
?
|
Unknown packet type.
|
&
|
Packet lifetime exceeded.
|
Examples
The following display shows sample ping output when you ping the IP host named donald:
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/3/4 ms
Related Commands
Command
|
Description
|
ping (privileged)
|
Checks host reachability and network connectivity.
|
service slave-log
To allow slave Versatile Interface Processor (VIP) cards to log important error messages to the console, use the service slave-log global configuration command. Use the no form of this command to disable slave logging.
service slave-log
no service slave-log
Syntax Description
This command has no arguments or keywords.
Defaults
This command is enabled by default.
Command Modes
Global configuration
Command History
Release
|
Modification
|
11.1
|
This command was introduced.
|
Usage Guidelines
This command allows slave slots to log error messages of level 2 or higher (critical, alerts, and emergencies).
Examples
The following example logs important messages from the slave cards to the console:
The following example illustrates sample output when this command is enabled:
%IPC-5-SLAVELOG: VIP-SLOT2:
IPC-2-NOMEM: No memory available for IPC system initialization
The first line indicates which slot sent the message. The second line contains the error message.
service tcp-keepalives-in
To generate keepalive packets on idle incoming network connections (initiated by the remote host), use the service tcp-keepalives-in global configuration command. The no form of this command with the appropriate keyword disables the keepalives.
service tcp-keepalives-in
no service tcp-keepalives-in
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Global configuration
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
Examples
The following example generates keepalives on incoming TCP connections:
service tcp-keepalives-in
Related Commands
Command
|
Description
|
service tcp-keepalives-out
|
Generates keepalive packets on idle outgoing network connections (initiated by a user).
|
service tcp-keepalives-out
To generate keepalive packets on idle outgoing network connections (initiated by a user), use the service tcp-keepalives-out global configuration command. The no form of this command with the appropriate keyword disables the keepalives.
service tcp-keepalives-out
no service tcp-keepalives-out
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Global configuration
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
Examples
The following example generates keepalives on outgoing TCP connections:
service tcp-keepalives-out
Related Commands
Command
|
Description
|
service tcp-keepalives-in
|
Generates keepalive packets on idle incoming network connections (initiated by the remote host).
|
service timestamps
To configure the system to time-stamp debugging or logging messages, use one of the service timestamps global configuration commands. Use the no form of this command to disable this service.
service timestamps type [uptime]
service timestamps type datetime [msec] [localtime] [show-timezone]
no service timestamps type
Syntax Description
type
|
Type of message to time stamp: debug or log.
|
uptime
|
(Optional) Time stamp with time since the system was rebooted.
|
datetime
|
Time stamp with the date and time.
|
msec
|
(Optional) Include milliseconds in the date and time stamp.
|
localtime
|
(Optional) Time stamp relative to the local time zone.
|
show-timezone
|
(Optional) Include the time zone name in the time stamp.
|
Defaults
No time-stamping.
If service timestamps is specified with no arguments or keywords, default is service timestamps debug uptime.
The default for service timestamps type datetime is to format the time in UTC, with no milliseconds and no time zone name.
The command no service timestamps by itself disables time stamps for both debug and log messages.
Command Modes
Global configuration
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
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
The following example enables time stamps on debugging messages, showing the time since reboot:
service timestamps debug uptime
The following example enables time stamps on logging messages, showing the current time and date relative to the local time zone, with the time zone name included:
service timestamps log datetime localtime show-timezone
Related Commands
Command
|
Description
|
clock set
|
Manually set the system clock.
|
ntp
|
Controls access to the system's NTP services.
|
show c2600 (Cisco 2600 series)
To display information for troubleshooting the Cisco 2600 series router, enter the show c2600 EXEC command.
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC and privileged EXEC
Command History
Release
|
Modification
|
11.3 XA
|
This command was introduced.
|
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
The following example shows sample display output for the show c2600 EXEC command. See Table 73 for a description of the output display fields.
C2600 Platform Information:
Vect Handler # of Ints Name
00 801F224C 00000000 Xilinx bridge error interrupt
01 801DE768 0D3EE155 MPC860 TIMER INTERRUPT
02 801E94E0 0000119E 16552 Con/Aux Interrupt
04 801F0D94 00000000 PA Network Management Int Handler
05 801E6C34 00000000 Timebase Reference Interrupt
06 801F0DE4 00002C1A PA Network IO Int Handler
07 801F0EA0 0000015D MPC860 CPM INTERRUPT
14 801F224C 00000000 Xilinx bridge error interrupt
SIU_IRQ_MASK = FFFFFFFF SIEN = EF02xxxx Current Level = 00
Spurious IRQs = 00000000 SIPEND = 0000xxxx
Throttle Count = 00000000 Timer Count = 00000000
Netint usec = 00000000 Netint Mask usec = 000003E8
Active = 0 Configured = 0
Requests = 00000349 Drops = 00000000
Complete = 00000349 Post Coalesce Frames = 00000349
Available Blocks = 256/256
Version string burned in chip: "A986122997"
New version after next program operation: "B018020998"
Table 73 show c2600 Field Descriptions
Field
|
Description
|
Interrupts
|
Denotes that the next section describes the status of the interrupt services.
|
Assigned Handlers
|
Denotes a subsection of the Interrupt section which displays data about the interrupt handlers.
|
Vect
|
The processor vector number.
|
Handler
|
The execution address of the handler assigned to this vector.
|
# of Ints
|
The number of times this handler has been called.
|
Name
|
The name of the handler assigned to this vector.
|
IOS Priority Masks
|
Denotes the subsection of the Interrupt section which displays internal Cisco IOS priorities. Each item in this subsection indicates a Cisco IOS interrupt level and the bit mask used to mask out interrupt sources when that Cisco IOS level is being processed. Used exclusively for debugging.
|
SIU_IRQ_MASK
|
For engineering level debug only.
|
Spurious IRQs
|
For engineering level debug only.
|
Interrupt Throttling:
|
This subsection describes the behavior of the Interrupt Throttling mechanism on the platform.
|
Throttle Count
|
Number of times throttle has become active.
|
Timer Count
|
Number of times throttle has deactivated because the maximum masked out time for network interrupt level has been reached.
|
Netint usec
|
Maximum time network level is allowed to run, in microseconds.
|
Netint Mask usec
|
Maximum time network level interrupt is masked out to allow process level code to run, in microseconds
|
Active
|
Indicates that the network level interrupt is masked or the router is in interrupt throttle state.
|
Configured
|
Indicates throttling is enabled or configured when set to 1.
|
Longest IRQ
|
Duration of longest network level interrupt, in microseconds.
|
IDMA Status
|
Monitors the activity of the Internal Direct Memory Access (IDMA) hardware and software. Used to coalesce packets (turn particalized packets into non-particalized packets) for transfer to the process level switching mechanism.
|
Requests
|
Number of times the IDMA engine is asked to coalesce a packet.
|
Drops
|
Number of times the coalescing operation was aborted.
|
Complete
|
Number of times the operation was successful.
|
Post Coalesce Frames
|
Number of Frames completed post-coalesce processing.
|
Giant
|
Number of packets too large to coalesce.
|
Available Blocks
|
Indicates the status of the request queue, in the format N/M where N is the number of empty slots in queue and M is the total number of slots; e.g., 2/256 indicates that the queue has 256 entries and can accept two more requests before it is full.
|
ISP Status
|
Provides status of In-System-Programmable hardware.
|
Version string burned in chip
|
Current version of ISP hardware.
|
New version after next program operation
|
Version of ISP hardware after next ISP programming operation.
|
ISP family type
|
Device family number of ISP hardware.
|
ISP chip ID
|
Internal ID of ISP hardware as designated by chip manufacturer.
|
Device is programmable
|
"Yes" or "No." Indicates if an ISP operation is possible on this board.
|
Related Commands
Command
|
Description
|
show context
|
Displays information stored in NVRAM when the router crashes.
|
show c7200 (Cisco 7200 series)
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
Release
|
Modification
|
11.2
|
This command was introduced.
|
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:
C7200 Network IO Interrupt Throttling:
throttle count=0, timer count=0
netint usec=3999, netint mask usec=200
Hardware revision 1.2 Board revision A0
Serial number 2863311530 Part number 170-43690-170
Test history 0xAA RMA number 170-170-170
MAC=0060.3e28.ee00, MAC Size=1024
EEPROM format version 1, Model=0x6
0x20: 01 06 01 02 AA AA AA AA AA AA AA AA 00 60 3E 28
0x30: EE 00 04 00 AA AA AA AA AA AA AA 50 AA AA AA AA
Hardware revision 2.0 Board revision A0
Serial number 3509953 Part number 73-1536-02
Test history 0x0 RMA number 00-00-00
0x20: 01 15 02 00 00 35 8E C1 49 06 00 02 00 00 00 00
0x30: 50 00 00 00 FF FF FF FF FF FF FF FF FF FF FF FF
show cls
To display the current status of all Cisco link services (CLS) sessions on the router, use the show cls command.
show cls [brief]
Syntax Description
brief
|
Displays a brief version of the output.
|
Defaults
Without the brief argument, displays complete output.
Command Modes
Exec
Command History
Release
|
Modification
|
11.0
|
This command was introduced in a release prior to 11.0.
|
Usage Guidelines
The Cisco link service (CLS) is used as the interface between data link users (DLUs), such as DLSw, LNM, DSPU, and SNASw, and their corresponding data link circuits (DLCs) such as LLC, VDLC, and QLLC. Each DLU registers a particular SAP with CLS, and establishes circuits through CLS over the DLC.
The show cls command displays the service access point (SAP) values associated with the DLU and the circuits established through CLS.
Examples
The following is sample output from the show cls command:
DTE:1234.4000.0001 1234.4000.0002 04 04
T1 timer:0 T2 timer:0 Inact timer:0
max out:0 max in:0 retry count:10
XID retry:10 XID timer:5000 I-Frame:0
flow:0 DataIndQ:0 DataReqQ:0
The following is sample output from the show cls brief command:
DTE:1234.4000.0001 1234.4000.0002 04 04
Bridging 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 (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 and Privileged EXEC
Command History
Release
|
Modification
|
10.3
|
This command was introduced.
|
Usage Guidelines
Context information is specific to processors and architectures, whereas software version and uptime information are 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:
•
Reason for the system reboot
•
Stack trace
•
Software version
•
The signal number, code, and router uptime information
•
All the register contents at the time of the crash
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 displays sample output from the show context command following a system failure on a Cisco 2600 series router. See Table 74 for a description of the fields in this output.
S/W Version: Cisco Internetwork Operating System Software
IOS (tm) c2600 Software (c2600-JS-M), Released Version 11.3(19980115:184921]
Copyright (c) 1986-1998 by cisco Systems, Inc.
Compiled Thu 15-Jan-98 13:49 by mmagno
Exception occurred at: 00:02:26 UTC Mon Mar 1 1993
Exception type: Data TLB Miss (0x1200)
PC = 0x80109964 MSR = 0x00009030 CR = 0x55FFFD35 LR = 0x80109958
CTR = 0x800154E4 XER = 0xC000BB6F DAR = 0x00000088 DSISR = 0x00000249
DEC = 0x7FFFDFCA TBU = 0x00000000 TBL = 0x15433FCF IMMR = 0x68010020
R0 = 0x80000000 R1 = 0x80E80BD0 R2 = 0x80000000 R3 = 0x00000000
R4 = 0x80E80BC0 R5 = 0x40800000 R6 = 0x00000001 R7 = 0x68010000
R8 = 0x00000000 R9 = 0x00000060 R10 = 0x00001030 R11 = 0xFFFFFFFF
R12 = 0x00007CE6 R13 = 0xFFF379E8 R14 = 0x80D50000 R15 = 0x00000000
R16 = 0x00000000 R17 = 0x00000000 R18 = 0x00000000 R19 = 0x00000000
R20 = 0x00000000 R21 = 0x00000001 R22 = 0x00000010 R23 = 0x00000000
R24 = 0x00000000 R25 = 0x80E91348 R26 = 0x01936010 R27 = 0x80E92A80
R28 = 0x00000001 R29 = 0x019BA920 R30 = 0x00000000 R31 = 0x00000018
Frame 00: SP = 0x80E80BD0 PC = 0x80109958
Frame 01: SP = 0x80E80C28 PC = 0x8010A720
Frame 02: SP = 0x80E80C40 PC = 0x80271010
Frame 03: SP = 0x80E80C50 PC = 0x8025EE64
Frame 04: SP = 0x80DEE548 PC = 0x8026702C
Frame 05: SP = 0x80DEE558 PC = 0x8026702C
Table 74 show context Field Descriptions
Field
|
Description
|
S/W Version
|
Standard Cisco IOS version string as displayed.
|
Exception occurred at
|
Router real time when exception occurred. The router must have the clock time properly configured for this to be accurate.
|
Exception type
|
Technical reason for exception. For engineering analysis.
|
CPU Register Context
|
Technical processor state information. For engineering analysis.
|
Stack trace
|
Technical processor state information. For engineering analysis.
|
Related Commands
Command
|
Description
|
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
summary
|
Displays a summary of all the crashes recorded.
|
all
|
Displays all crashes for all the slots. When optionally used with the slot keyword, displays crash information for the specified slot.
|
slot slot-number [crash-index]
|
Displays information for a particular line card. Slot numbers range from 0 to 11 for the Cisco 12012 and 0 to 7 for the Cisco 12008. Index number allows you to look at previous crash contexts. Contexts from the last 24 line card crashes are saved on the GRP card. If the GRP reloads, the last 24 line card crash contexts are lost. For example, show context slot 3 2 shows the second most recent crash for line card in slot 3. Index numbers are displayed by the show context summary command
|
debug
|
(Optional) Displays crash information as hex record dump in addition to one of the options listed.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
11.2 GS
|
This command was modified to add the all, debug, slot, and summary keywords.
|
Usage Guidelines
The display from the show context command includes the following information:
•
Reason for the system reboot
•
Stack trace
•
Software version
•
The signal number, code, and router uptime information
•
All the register contents at the time of the crash
Note
This information is of use only to technical support representatives in analyzing crashes in the field. It is included here in case you need to read the displayed statistics to an engineer over the phone.
Examples
The following is sample output from the show context command following a system failure:
System was restarted by error - a Software forced crash, PC 0x60189354
GS Software (RSP-PV-M), Experimental Version 11.1(2033) [ganesh 111]
Compiled Mon 31-Mar-97 13:21 by ganesh
Image text-base: 0x60010900, data-base: 0x6073E000
Stack trace from system failure:
FP: 0x60AEA798, RA: 0x60189354
FP: 0x60AEA798, RA: 0x601853CC
FP: 0x60AEA7C0, RA: 0x6015E98C
FP: 0x60AEA7F8, RA: 0x6011AB3C
FP: 0x60AEA828, RA: 0x601706CC
FP: 0x60AEA878, RA: 0x60116340
FP: 0x60AEA890, RA: 0x6011632C
GS Software (RSP-PV-M), Experimental Version 11.1(2033) [ganesh 111]
Compiled Mon 31-Mar-97 13:21 by ganesh
Signal = 23, Code = 0x24, Uptime 00:04:19
$0 : 00000000, AT : 60930120, v0 : 00000032, v1 : 00000120
a0 : 60170110, a1 : 6097F22C, a2 : 00000000, a3 : 00000000
t0 : 60AE02A0, t1 : 8000FD80, t2 : 34008F00, t3 : FFFF00FF
t4 : 00000083, t5 : 3E840024, t6 : 00000000, t7 : 11010132
s0 : 00000006, s1 : 607A25F8, s2 : 00000001, s3 : 00000000
s4 : 00000000, s5 : 00000000, s6 : 00000000, s7 : 6097F755
t8 : 600FABBC, t9 : 00000000, k0 : 30408401, k1 : 30410000
gp : 608B9860, sp : 60AEA798, s8 : 00000000, ra : 601853CC
EPC : 60189354, SREG : 3400EF03, Cause : 00000024
The following is sample output from the show context summary command on a Cisco 12012 router. The show context summary command displays a summary of all the crashes recorded.
Router# show context summary
1 - crash at 18:06:41 UTC Tue Nov 5 1996
2 - crash at 12:14:55 UTC Mon Nov 4 1996
Related Commands
Command
|
Description
|
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 number | clock | csar [register] | csc-fpga | dp83800 | fab-clk | fia
[register] | pos [number] [details] | queues [slot-number] | sca | xbar]
Syntax Description
atm number
|
(Optional) Displays the ATM controllers. Number is slot-number/ port-number (for example, 4/0). Slot numbers range from 0 to 11 for the Cisco 12012 and 0 to 7 for the Cisco 12008.
|
clock
|
(Optional) Displays the clock card configuration.
|
csar [register]
|
(Optional) Displays the Cisco Cell Segmentation and Reassembly (CSAR) information. CSAR is the name of the chip on the card that handles traffic between the GRP and the switch fabric interface ASICs.
|
csc-fpga
|
(Optional) Displays the clock and scheduler card register information in the field programmable gate array (FPGA).
|
dp83800
|
(Optional) Displays the Ethernet information on the GRP card.
|
fab-clk
|
(Optional) Display the switch fabric clock register information. The switch fabric clock FPGA is a chip that monitors the incoming fabric clock generated by the switch fabric. This clock is needed by each card connecting to the switch fabric to properly communicate with it. There are two switch fabric clocks arriving at each card; only one can be used. The FPGA monitors both clocks and selects which one to use if only one of them is running.
|
fia [register]
|
(Optional) Displays the fabric interface ASIC information and optionally display the register information.
|
pos [number] [details]
|
(Optional) Displays the POS framer state and optionally displays all the details for the interface. Number is slot-number/ port-number (for example, 4/0). Slot numbers range from 0 to 11 for the Cisco 12012 and 0 to 7 for the Cisco 12008.
|
queues [slot-number]
|
(Optional) Displays the SDRAM buffer carve information and optionally displays the information for a specific line card. The SDRAM buffer carve information displayed is suggested carve information from the GRP card to the line card. Line cards might change the shown percentages based on SDRAM available. Slot numbers range from 0 to 11 for the Cisco 12012 and 0 to 7 for the Cisco 12008.
|
sca
|
(Optional) Displays the SCA register information. The SCA is an ASIC that arbitrates among the line cards requests to use the switch fabric.
|
xbar
|
(Optional) Displays the crossbar register information. The XBAR is an ASIC that switches the data as it passes through the switch fabric.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
11.2 GS
|
This command was added to support the Cisco 12000 series Gigabit Switch Routers.
|
Usage Guidelines
Note
This information is of use only to technical support representatives in analyzing system failures in the field. It is included here in case you need to read the displayed statistics to an engineer over the phone.
Examples
The following is sample output from the show controllers pos command for a Cisco 12012:
Router# show controllers pos 7/0
LOF = 2 LOS = 0 BIP(B1) = 5889
AIS = 2 RDI = 2 FEBE = 146 BIP(B2) = 2106453
AIS = 2 RDI = 4 FEBE = 63 BIP(B3) = 3216
LOP = 0 PSE = 8 NSE = 3 NEWPTR = 2
State: PSBF_state = False
Rx(K1/K2): F0/15 Tx(K1/K2): 00/00
PATH TRACE BUFFER : STABLE
Remote interface: POS10/0
Remote IP addr : 10.201.101.2
Remote Rx(K1/K2): F0/15 Tx(K1/K2): 00/00
Related Commands
Command
|
Description
|
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
atm
|
Displays the ATM controller information.
|
port-number
|
(Optional) Displays request for the physical interface on the ATM card. The range of choices is 0-3.
|
all
|
(Optional) Lists all details.
|
sar
|
(Optional) Lists SAR interactive command.
|
summary
|
(Optional) Lists SAR status summary.
|
fia
|
Displays the fabric interface ASIC information.
|
register
|
(Optional) Displays the register information.
|
frfab
|
(Optional) Displays the from fabric (transmit).
|
tofab
|
(Optional) Displays the to fabric (receive) information.
|
bma
|
For the frfab or tofab keywords, displays microcode, micro-sequencer, or register information for the silicon queuing engine (SQE), also known as the buffer management ASIC (BMA).
|
microcode
|
Displays silicon queuing engine (SQE) information for the microcode bundled in the line card and currently running version.
|
mis-inst
|
Displays silicon queuing engine (SQE) information for the micro sequencer instruction.
|
register
|
Displays silicon queuing engine (SQE) information for the register.
|
qelem
|
For the frfab or tofab keywords, displays the SDRAM buffer pool queue element summary information.
|
start-queue-element
|
Specifies the start queue element number (0 to 65535).
|
end-queue-element
|
(Optional) Specifies the end queue element number (0 to 65535).
|
qnum
|
For the frfab or tofab keywords, displays the SDRAM buffer pool queue detail information.
|
start-queue-number
|
Specifies the start free queue number (0 to 127).
|
end-queue-number
|
(Optional) Specifies the end free queue number (0 to 127).
|
queues
|
For the frfab or tofab keywords, displays the SDRAM buffer pool information.
|
statistics
|
For the frfab or tofab keywords, displays the BMA counters.
|
io
|
Displays input/output registers.
|
l3
|
Displays Layer 3 ASIC information.
|
pos
|
Displays packet-over-sonic (POS) information for framer registers, framer queues, and ASIC registers.
|
framers
|
Displays the POS framer registers.
|
queues
|
Displays the POS framer queue information.
|
registers
|
Displays the ASIC registers.
|
rxsram
|
Displays the receive queue SRAM.
|
port-number
|
Specifies a port number (valid range is 0 to 3).
|
queue-start-address
|
Specifies the queue SRAM logical starting address.
|
queue-length
|
(Optional) Specifies the queue SRAM length.
|
txsram
|
Displays the transmit queue SRAM.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
11.2 GS
|
This command was added to support the Cisco 12000 series Gigabit Switch Routers.
|
Usage Guidelines
Note
This information is of use only to technical support representatives in analyzing crashes in the field. It is included here in case you need to read the displayed statistics to an engineer over the phone.
Examples
Because you are executing this command on the line card, you must use the execute-on command to perform the show command, or you must connect to the card using the attach command. All examples in this section use the execute-on command
The following is partial sample output from the show controllers atm command:
Router# execute-on slot 4 show controllers atm 0
TX SAR (Beta 1.0.0) is Operational;
RX SAR (Beta 1.0.0) is Operational;
Interface Configuration Mode:
Active Maker Channels: total # 6
VCID ChnnlID Type OutputInfo InPkts InOAMs MacString
1 0888 UBR 0C010010 0 0 08882000AAAA030000000800
2 0988 VBR 04010020 0 0 09882000
3 8BC8 UBR 0C010030 0 0 8BC82000AAAA030000000800
4 0E08 UBR 0C010040 0 0 0E082000AAAA030000000800
10 1288 VBR 040100A0 0 0 12882000
11 8BE8 VBR 0C0100B0 0 0 8BE82000AAAA030000000800
total_tx_idle_cells 215267 total_tx_paks 0 total_tx_abort_paks 0
total_rx_paks 0 total_rx_drop_paks 0 total_rx_discard_cells 15
total_rx_crc_err_paks 0 total_rx_giant_paks 0
total_rx_abort_paks 0 total_rx_crc10_cells 0
total_rx_tmout_paks 0 total_rx_unknown_paks 0
total_rx_out_buf_paks 0 total_rx_unknown_vc_paks 0
BATMAN 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): 0x10
Master Configuration Reg (#0x1): 0x1F
Master Interrupt Status Reg (#0x2): 0x00
PISO Interrupt Reg (#0x3): 0x04
Master Auto Alarm Reg (#0x4): 0x03
Master Auto Alarm Reg (#0x5): 0x07
Parallel Output Port Reg (#0x6): 0x02
BERM Line BIP Threshold LSB Reg (#0x74): 0x00
BERM Line BIP Threshold MSB Reg (#0x75): 0x00
The following is partial sample output from the show controllers command:
Router# execute-on slot 6 show controllers
lcpos_instance struct 60311B40
RX POS ASIC addr space 12000000
TX POS ASIC addr space 12000100
SUNI framer addr space 12000400
CRC32 enabled, HDLC enc, int clock
lcpos_instance struct 603142E0
RX POS ASIC addr space 12000000
TX POS ASIC addr space 12000100
SUNI framer addr space 12000600
CRC32 enabled, HDLC enc, int clock
The following is partial sample output from the show controllers pos framers command:
Router# execute-on slot 6 show controllers pos framers
Framer 0, addr=0x12000400:
master config 1F rrate sts3c trate sts3c fixptr
TACP control status 04 hcsadd
RSOP cntrl intr enable 00
TPOP path sig lbl (c2) 13
Framer 1, addr=0x12000600:
master config 1F rrate sts3c trate sts3c fixptr
TACP control status 04 hcsadd
RSOP cntrl intr enable 00
TPOP path sig lbl (c2) 13
Framer 2, addr=0x12000800:
master config 1F rrate sts3c trate sts3c fixptr
TACP control status 04 hcsadd
RSOP cntrl intr enable 00
TPOP path sig lbl (c2) 13
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 redundant
Master Scheduler: Slot 17
redund fifo parity 0 redund overflow 0 cell drops 0
crc32 lkup parity 0 cell parity 0 crc32 0
-------- -------- -------- -------- --------
sca not pres 0 req error 0 uni fifo overflow 0
grant parity 0 multi req 0 uni fifo undrflow 0
cntrl parity 0 uni req 0 crc32 lkup parity 0
multi fifo 0 empty dst req 0 handshake error 0
Related Commands
Command
|
Description
|
clear controllers
|
Resets the T1 or E1 controller.
|
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
vip slot-number
|
VIP slot number.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
11.2
|
This command was introduced.
|
Usage Guidelines
This command displays the state of syslog error and event logging, including host addresses, and whether console logging is enabled.
Examples
The following is sample output from the show controllers logging command:
Router# show controllers vip 4 logging
Console logging: disabled
Monitor logging: level debugging, 266 messages logged.
Trap logging: level informational, 266 messages logged.
Table 75 describes significant fields shown in the display.
Table 75 show controllers logging Field Descriptions
Field
|
Description
|
Syslog logging
|
When enabled, system logging messages are sent to a UNIX host that acts as a syslog server; that is, it captures and saves the messages.
|
Console logging
|
If enabled, states the level; otherwise, this field displays disabled.
|
Monitor logging
|
Minimum level of severity required for a log message to be sent to a monitor terminal (not the console).
|
Trap logging
|
Minimum level of severity required for a log message to be sent to a syslog server.
|
Related Commands
Command
|
Description
|
show logging
|
Displays the state of logging (syslog).
|
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
vip slot-number
|
VIP slot number.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
11.2
|
This command was introduced.
|
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:
•
show version
•
more system:running-config
•
show controllers
•
show stacks
•
show interfaces
•
show buffers
•
show processes memory
•
show processes cpu
For a sample display of the show controllers tech-support command output, refer to these show commands.
Related Commands
Command
|
Description
|
more system:running-config
|
Displays the running configuration.
|
show buffers
|
Displays statistics for the buffer pools on the network server.
|
show controllers
|
Displays information that is specific to the hardware.
|
show interfaces
|
Use the show interfaces EXEC command to display ALC information.
|
show processes
|
Displays information about the active processes.
|
show processes memory
|
Displays memory used.
|
show stacks
|
Monitors the stack usage of processes and interrupt routines.
|
show tech-support
|
Displays general information about the router when reporting a problem.
|
show version
|
Displays the configuration of the system hardware, the software version, the names and sources of configuration files, and the boot images.
|
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
Release
|
Modification
|
11.1
|
This command was introduced.
|
Examples
The following is sample output from the show debugging command. In this example, three types of CDP debugging are enabled.
CDP packet info debugging is on
CDP events debugging is on
CDP neighbor info debugging is on
Related Commands
Command
|
Description
|
debug
|
|
show diag
To display hardware information including DRAM and Static RAM (SRAM) on line cards, use the show diag command in privileged EXEC mode.
show diag [slot-number] [details] [summary]
Syntax Description
slot-number
|
(Optional) Slot number of the interface.
|
details
|
(Optional) Displays more details than the normal show diag output.
|
summary
|
(Optional) Displays a summary (one line per slot) of the chassis.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
11.1 CA, 11.2
|
This command was introduced.
|
11.2 P
|
This command was modified to show information for PA-12E/2FE, PA-E3, and PA-T3 port adapters.
|
11.2 GS
|
This command was made available on Cisco 12000 series Gigabit Switch Routers.
|
11.3 XA
|
This command integrated in Cisco IOS Release 11.3 XA.
|
12.0(5)XQ
|
This command was enhanced and made available on Cisco 1750 routers.
|
12.0(7)T
|
This command was integrated in Cisco IOS Release 12.0 T.
|
Usage Guidelines
Use this command to determine the type of hardware installed in your router. This command applies towards line cards in Cisco Universal Access Servers, Cisco 1750, 7200, and 7500 series routers, and Cisco 12000 series GSRs.
Examples
The following is sample output from the show diag command on a 12000 series GSR:
SLOT 3 (RP/LC 3 ): 4 Port Packet Over SONET OC-3c/STM-1 Multi Mode
MAIN: type 33, 00-0000-00 rev 70 dev 0
HW config: 0x01 SW key: 00-00-00
PCA: 73-2147-02 rev 94 ver 2
HW version 1.0 S/N 04499695
MBUS: MBUS Agent (1) 73-2146-05 rev 73 dev 0
HW version 1.1 S/N 04494882
Test hist: 0x00 RMA#: 00-00-00 RMA hist: 0x00
DIAG: Test count: 0x05000001 Test results: 0x00000000
MBUS Agent Software version 01.27 (RAM) using CAN Bus A
ROM Monitor version 00.0D
Fabric Downloader version used 00.0D (ROM version is 00.0D)
Board State is Line Card Enabled (IOS RUN )
Insertion time: 00:00:10 (00:04:51 ago)
DRAM size: 33554432 bytes
FrFab SDRAM size: 67108864 bytes
ToFab SDRAM size: 16777216 bytes
The following is sample output from the show diag summary command:
Router# show diag summary
SLOT 0 (RP/LC 0 ): Route Processor
SLOT 2 (RP/LC 2 ): 4 Port Packet Over SONET OC-3c/STM-1 Single Mode
SLOT 4 (RP/LC 4 ): 4 Port Packet Over SONET OC-3c/STM-1 Single Mode
SLOT 7 (RP/LC 7 ): 4 Port Packet Over SONET OC-3c/STM-1 Single Mode
SLOT 9 (RP/LC 9 ): 4 Port Packet Over SONET OC-3c/STM-1 Single Mode
SLOT 11 (RP/LC 11): 4 Port Packet Over SONET OC-3c/STM-1 Single Mode
SLOT 16 (CSC 0 ): Clock Scheduler Card
SLOT 17 (CSC 1 ): Clock Scheduler Card
SLOT 18 (SFC 0 ): Switch Fabric Card
SLOT 19 (SFC 1 ): Switch Fabric Card
SLOT 20 (SFC 2 ): Switch Fabric Card
SLOT 24 (PS A1 ): AC Power Supply
SLOT 26 (PS B1 ): AC Power Supply
SLOT 28 (TOP FAN ): Blower Module
SLOT 29 (BOT FAN ): Blower Module
The following is sample output from the show diag details command:
Router# show diag 4 details
SLOT 4 (RP/LC 4): 4 Port Packet Over SONET OC-3c/STM-1 Single Mode
MAIN: type 33, 800-2389-01 rev 71 dev 16777215
HW config: 0x00 SW key: FF-FF-FF
PCA: 73-2275-03 rev 75 ver 3
HW version 1.1 S/N 04529465
MBUS: MBUS Agent (1) 73-2146-06 rev 73 dev 0
HW version 1.1 S/N 04541395
Test hist: 0xFF RMA#: FF-FF-FF RMA hist: 0xFF
DIAG: Test count: 0x05000001 Test results: 0x00000000
00: 01 00 01 00 49 00 08 62 06 03 00 00 00 FF FF FF
10: 30 34 35 34 31 33 39 35 FF FF FF FF FF FF FF FF
20: 01 01 00 00 00 00 00 FF FF FF FF FF FF FF FF FF
30: A5 FF A5 A5 A5 A5 FF A5 A5 A5 A5 A5 A5 A5 A5 A5
40: 00 21 01 01 00 49 00 08 E3 03 05 03 00 01 FF FF
50: 03 20 00 09 55 01 01 FF FF FF 00 FF FF FF FF FF
60: 30 34 35 32 39 34 36 35 FF FF FF FF FF FF FF FF
70: FF FF FF FF FF FF FF FF 05 00 00 01 00 00 00 00
MBUS Agent Software version 01.24 (RAM)
Fabric Downloader version 00.0D
Board State is Line Card Enabled (IOS RUN)
Insertion time: 00:00:10 (00:04:51 ago)
DRAM size: 33554432 bytes
FrFab SDRAM size: 67108864 bytes
ToFab SDRAM size: 16777216 bytes
The following is an example for the Cisco 7513 router with a VIP2 in slot 8. This card has two 4-port Token Ring port adapters located in port adapter bays 0 and 1.
Physical slot 8, ~physical slot 0x7, logical slot 8, CBus 0
Master Enable, LED, WCS Loaded
VIP2 controller, HW rev 2.2, board revision UNKNOWN
Serial number: 03341418 Part number: 73-1684-02
Test history: 0x00 RMA number: 00-00-00
Flags: cisco 7000 board; 7500 compatible
0x20: 01 15 02 02 00 32 FC 6A 49 06 94 02 00 00 00 00
0x30: 07 2B 00 2A 1A 00 00 00 00 00 00 00 00 00 00 00
Slot database information:
Flags: 0x4 Insertion time: 0x3188 (01:20:53 ago)
Controller Memory Size: 8 MBytes
HW rev 1.1, Board revision 0
Serial number: 02827613 Part number: 73-1390-04
HW rev 1.1, Board revision 88
Serial number: 02023786 Part number: 73-1390-04
The following is an example from the show diagbus command for the Ethernet interface in slot 2 on a Cisco 7200 series router:
Ethernet port adapter, 8 ports
Port adapter insertion time 1d18h ago
Hardware revision 1.0 Board revision K0
Serial number 2023387 Part number 73-1391-03
Test history 0x0 RMA number 00-00-00
0x20: 01 01 01 00 00 1E DF DB 49 05 6F 03 00 00 00 00
0x30: A0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
show environment
To display temperature, voltage, and blower information on the Cisco 7000 series, Cisco 7200 series, Cisco 7500 series routers, and Cisco 12000 series Gigabit Switch Routers (GSRs), use the show environment privileged EXEC command.
show environment [alarms | all | fans | hardware | last | leds | power-supply | table |
temperatures | voltages]
Syntax Description
alarms
|
(Optional) Displays the alarm contact information.
|
all
|
(Optional) Displays a detailed listing of the power supplies, temperature readings, voltage readings, and blower speeds.
|
fans
|
(Optional) Displays blower and fan information.
|
hardware
|
(Optional) Displays hardware-specific information.
|
last
|
(Optional) Displays information on the last measurement made.
|
leds
|
(Optional) Displays the status of the MBus LEDs on the clock and scheduler cards and switch fabric cards.
|
power-supply
|
(Optional) Displays power supply voltage and current information.
|
table
|
(Optional) Displays the temperature, voltage, and blower thresholds.
|
temperature
|
(Optional) Displays temperature information.
|
voltages
|
(Optional) Displays voltage information.
|
Defaults
If no options are specified, the current environmental parameters are displayed.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
11.2 GS
|
The alarms, fans, hardware, leds, power-supply, table temperature, and voltages keywords were added for Cisco 12000 series Gigabit Switch Routers.
|
Usage Guidelines
Once a minute a routine is run that gets environmental measurements from sensors and stores the output into a buffer. This buffer is displayed on the console when show environment is invoked.
If a measurement exceeds desired margins, but has not exceeded fatal margins, a warning message is printed to the system console. The system software queries the sensors for measurements once a minute, but warnings for a given test point are printed at most once every hour for sensor readings in the warning range and once every 5 minutes for sensor readings in the critical range. If a measurement is out of line within these time segments, an automatic warning message appears on the console. As noted, you can query the environmental status with the show environment command at any time to determine whether a measurement is at the warning or critical tolerance.
If a shutdown occurs because of detection of fatal environmental margins, the last measured value from each sensor is stored in internal nonvolatile memory.
For environmental specifications, refer to the hardware installation and configuration publication for your individual chassis.
If the Cisco 12000 series exceeds environmental conditions, a message similar to the following is displayed on the console:
%GSR_ENV-2-WARNING: Slot 3 Hot Sensor Temperature exceeds 40 deg C;
Note
Blower temperatures that exceed environmental conditions do not generate a warning message.
Examples
The following example shows the typical show environment display when there are no warning conditions in the system for the Cisco 7000 series and Cisco 7200 series. This information may vary slightly depending on the platform you are using. The date and time of the query are displayed, along with the data refresh information and a message indicating that there are no warning conditions.
Environmental status as of 13:17:39 UTC Thu Jun 6 1996
Data is 7 second(s) old, refresh in 53 second(s)
All Environmental Measurements are within specifications
Table 76 describes the fields shown in the display.
Table 76 show environment Field Descriptions
Field
|
Description
|
Environmental status as of...
|
Current date and time.
|
Data is..., refresh in...
|
Environmental measurements are output into a buffer every 60 seconds, unless other higher-priority processes are running.
|
Status message
|
If environmental measurements are not within specification, warning messages are displayed.
|
The Cisco 7000 Series
The following are examples of messages that display on the system console when a measurement has exceeded an acceptable margin:
ENVIRONMENTAL WARNING: Air flow appears marginal.
ENVIRONMENTAL WARNING: Internal temperature measured 41.3(C)
ENVIRONMENTAL WARNING: +5 volt testpoint measured 5.310(V)
The system displays the following message if voltage or temperature exceed maximum margins:
SHUTDOWN: air flow problem
In the following example, there have been two intermittent power failures since a router was turned on, and the lower power supply is not functioning. The last intermittent power failure occurred on Monday, June 10, 1996, at 11:07 p.m.
7000# show environment all
Environmental status as of 23:19:47 UTC Wed Jun 12 1996
Data is 6 second(s) old, refresh in 54 second(s)
WARNING: Lower Power Supply is NON-OPERATIONAL
Lower Power Supply:700W, OFF Upper Power Supply: 700W, ON
Intermittent Powerfail(s): 2 Last on 23:07:05 UTC Mon Jun 10 1996
+12 volts measured at 12.05(V)
+5 volts measured at 4.96(V)
-12 volts measured at -12.05(V)
+24 volts measured at 23.80(V)
Airflow temperature measured at 38(C)
Inlet temperature measured at 25(C)
Table 77 describes the fields shown in the display.
Table 77 show environment all Field Descriptions for the Cisco 7000
Field
|
Description
|
Environmental status as of...
|
Date and time of last query.
|
Data is..., refresh in...
|
Environmental measurements are output into a buffer every 60 seconds, unless other higher-priority processes are running.
|
WARNING:
|
If environmental measurements are not within specification, warning messages are displayed.
|
Lower Power Supply
|
Type of power supply installed and its status (On or Off).
|
Upper Power Supply
|
Type of power supply installed and its status (On or Off).
|
Intermittent Powerfail(s)
|
Number of power hits (not resulting in shutdown) since the system was last booted.
|
Voltage specifications
|
System voltage measurements.
|
Airflow and inlet temperature
|
Temperature of air coming in and going out.
|
The following example is for the Cisco 7000 series router. The router retrieves the environmental statistics at the time of the last shutdown. In this example, the last shutdown was Friday, May 19, 1995, at 12:40 p.m., so the environmental statistics at that time are displayed.
Router# show environment last
Environmental status as of 14:47:00 UTC Sun May 21 1995
Data is 6 second(s) old, refresh in 54 second(s)
WARNING: Upper Power Supply is NON-OPERATIONAL
LAST Environmental Statistics
Environmental status as of 12:40:00 UTC Fri May 19 1995
Lower Power Supply: 700W, ON Upper Power Supply: 700W, OFF
No Intermittent Powerfails
+12 volts measured at 12.05(V)
+5 volts measured at 4.98(V)
-12 volts measured at -12.00(V)
+24 volts measured at 23.80(V)
Airflow temperature measured at 30(C)
Inlet temperature measured at 23(C)
Table 78 describes the fields shown in the display.
Table 78 show environment last Field Descriptions for the Cisco 7000
Field
|
Description
|
Environmental status as of...
|
Current date and time.
|
Data is..., refresh in...
|
Environmental measurements are output into a buffer every 60 seconds, unless other higher-priority processes are running.
|
WARNING:
|
If environmental measurements are not within specification, warning messages are displayed.
|
LAST Environmental Statistics
|
Displays test point values at time of the last environmental shutdown.
|
Lower Power Supply:
Upper Power Supply:
|
For the Cisco 7000, indicates the status of the two 700W power supplies.
For the Cisco 7010, indicates the status of the single 600W power supply.
|
The following sample output shows the current environmental status in tables that list voltage and temperature parameters. There are three warning messages: one each about the lower power supply, the airflow temperature, and the inlet temperature. In this example, voltage parameters are shown to be in the normal range, airflow temperature is at a critical level, and inlet temperature is at the warning level.
Router> show environment table
Environmental status as of Mon 11-2-1992 17:43:36
Data is 52 second(s) old, refresh in 8 second(s)
WARNING: Lower Power Supply is NON-OPERATIONAL
WARNING: Airflow temperature has reached CRITICAL level at 73(C)
WARNING: Inlet temperature has reached WARNING level at 41(C)
SENSE CRITICAL NORMAL CRITICAL
-------|--------------------|------------------------|--------------------
+12(V) 10.20 12.05(V) 13.80
-12(V) -10.20 -12.05(V) -13.80
+24(V) 20.00 24.00(V) 28.00
SENSE WARNING NORMAL WARNING CRITICAL SHUTDOWN
-------|-------------|------------|-------------|--------------|-----------
Airflow 10 60 70 73(C) 88
Table 79 describes the fields shown in the display.
Table 79 show environment Field Descriptions for the Cisco 7000
Field
|
Description
|
SENSE (Voltage Parameters)
|
Voltage specification for DC line.
|
SENSE (Temperature Parameters)
|
Air being measured. Inlet measures the air coming in, and Airflow measures the temperature of the air inside the chassis.
|
WARNING
|
System is approaching an out-of-tolerance condition.
|
NORMAL
|
All monitored conditions meet normal requirements.
|
CRITICAL
|
Out-of-tolerance condition exists.
|
SHUTDOWN
|
Processor has detected condition that could cause physical damage to the system.
|
The Cisco 7200 Series
The system displays the following message if the voltage or temperature enters the "Warning" range:
%ENVM-4-ENVWARN: Chassis outlet 3 measured at 55C/131F
The system displays the following message if the voltage or temperature enters the "Critical" range:
%ENVM-2-ENVCRIT: +3.45 V measured at +3.65 V
The system displays the following message if the voltage or temperature exceeds the maximum margins:
%ENVM-0-SHUTDOWN: Environmental Monitor initiated shutdown
The following message is sent to the console if a power supply has been inserted or removed from the system. This message relates only to systems that have two power supplies.
%ENVM-6-PSCHANGE: Power Supply 1 changed from Zytek AC Power Supply to removed
The following message is sent to the console if a power supply has been powered on or off. In the case of the power supply being shut off, this message can be due to the user shutting off the power supply or to a failed power supply. This message relates only to systems that have two power supplies.
%ENVM-6-PSLEV: Power Supply 1 state changed from normal to shutdown
The following is sample output from the show environment all command on the Cisco 7200 series router when there is a voltage warning condition in the system:
7200# show environment all
Power supply 1 is unknown. Unit is off.
Power supply 2 is Zytek AC Power Supply. Unit is on.
chassis inlet measured at 25C/77F
chassis outlet 1 measured at 29C/84F
chassis outlet 2 measured at 36C/96F
chassis outlet 3 measured at 44C/111F
+3.45 V measured at +3.83 V:Voltage in Warning range!
+5.15 V measured at +5.09 V
+12.15 measured at +12.42 V
-11.95 measured at -12.10 V
Table 80 describes the fields shown in the display.
Table 80 show environment all Field Descriptions for the Cisco 7200
Field
|
Description
|
Power Supplies:
|
Current condition of the power supplies including the type and whether the power supply is on or off.
|
Temperature readings:
|
Current measurements of the chassis temperature at the inlet and outlet locations.
|
Voltage readings:
|
Current measurement of the power supply test points.
|
The following example is for the Cisco 7200 series router. This example shows the measurements immediately before the last shutdown and the reason for the last shutdown (if appropriate).
7200# show environment last
chassis inlet previously measured at 27C/80F
chassis outlet 1 previously measured at 31C/87F
chassis outlet 2 previously measured at 37C/98F
chassis outlet 3 previously measured at 45C/113F
+3.3 V previously measured at 4.02
+5.0 V previously measured at 4.92
+12.0 V previously measured at 12.65
-12.0 V previously measured at 11.71
last shutdown reason - power supply shutdown
Table 81 describes the fields shown in the display.
Table 81 show environment last Field Descriptions for the Cisco 7200
Field
|
Description
|
chassis inlet
|
Temperature measurements at the inlet area of the chassis.
|
chassis outlet
|
Temperature measurements at the outlet areas of the chassis.
|
voltages
|
Power supply test point measurements.
|
last shutdown reason
|
Possible shutdown reasons are power supply shutdown, critical temperature, and critical voltage.
|
The following example is for the Cisco 7200 series router. This information lists the temperature and voltage shutdown thresholds for each sensor.
7200# show environment table
Sample Point LowCritical LowWarning HighWarning HighCritical
chassis inlet 40C/104F 50C/122F
chassis outlet 1 43C/109F 53C/127F
chassis outlet 2 75C/167F 75C/167F
chassis outlet 3 55C/131F 65C/149F
+3.45 V +2.76 +3.10 +3.80 +4.14
+5.15 V +4.10 +4.61 +5.67 +6.17
+12.15 V +9.72 +10.91 +13.37 +14.60
-11.95 V -8.37 -9.57 -14.34 -15.53
Shutdown system at 70C/158F
Table 82 describes the fields shown in the display.
Table 82 show environment table Field Descriptions for the Cisco 7200
Field
|
Description
|
Sample Point
|
Area for which measurements are taken.
|
LowCritical
|
Level at which a critical message is issued for an out-of-tolerance voltage condition. The system continues to operate; however, the system is approaching shutdown.
|
LowWarning
|
Level at which a warning message is issued for an out-of-tolerance voltage condition. The system continues to operate, but operator action is recommended to bring the system back to a normal state.
|
HighWarning
|
Level at which a warning message is issued. The system continues to operate, but operator action is recommended to bring the system back to a normal state.
|
HighCritical
|
Level at which a critical message is issued. For the chassis, the router is shut down. For the power supply, the power supply is shut down.
|
Shutdown system at
|
The system is shut down if the specified temperature is met.
|
Cisco 7500 Series
The sample output for the Cisco 7500 series routers may vary depending on the specific model (for example, the Cisco 7513). The following is sample output from the show environment all command on the Cisco 7500 series router:
7500# show environment all
Arbiter type 1, backplane type 7513 (id 2)
Power supply #1 is 1200W AC (id 1), power supply #2 is removed (id 7)
Active fault conditions: none
Active trip points: Restart_Inhibit
15 of 15 soft shutdowns remaining before hard shutdown
card inlet hotpoint exhaust
RSP(6) 35C/95F 47C/116F 40C/104F
RSP(7) 35C/95F 43C/109F 39C/102F
Shutdown temperature source is `hotpoint' on RSP(6), requested RSP(6)
PS1 +5V Current measured at 59.61 A (capacity 200 A)
PS1 +12V Current measured at 5.08 A (capacity 35 A)
PS1 -12V Current measured at 0.42 A (capacity 3 A)
Table 83 describes the fields shown in the display.
Table 83 show environment all Field Descriptions for the Cisco 7500
Field
|
Description
|
Arbiter type 1
|
Numbers indicating the arbiter type and backplane type.
|
Power supply
|
Number and type of power supply installed in the chassis.
|
Active fault conditions:
|
If any fault conditions exist (such as power supply failure, fan failure, and temperature too high), they are listed here.
|
Fan transfer point:
|
Software controlled fan speed. If the router is operating below its automatic restart temperature, the transfer point is reduced by 10 percent of the full range each minute. If the router is at or above its automatic restart temperature, the transfer point is increased in the same way.
|
Active trip points:
|
Temperature sensor is compared against the values displayed at the bottom of the show environment table command output.
|
15 of 15 soft shutdowns remaining
|
When the temperature increases above the "board shutdown" level, a soft shutdown occurs (that is, the cards are shut down, and the power supplies, fans, and CI continue to operate). When the system cools to the restart level, the system restarts. The system counts the number of times this occurs and keeps the up/down cycle from continuing forever. When the counter reaches zero, the system performs a hard shutdown, which requires a power cycle to recover. The soft shutdown counter is reset to its maximum value after the system has been up for 6 hours.
|
Dbus slots:
|
Indicates which chassis slots are occupied.
|
card, inlet, hotpoint, exhaust
|
Temperature measurements at the inlet, hotpoint, and exhaust areas of the card. The (6) and (7) indicate the slot numbers. Dual-RSP chassis can show two RSPs.
|
Shutdown temperature source
|
Indicates which of the three temperature sources is selected for comparison against the "shutdown" levels listed with the show environment table command.
|
Voltages (+12V, +5V, -12V, +24V, +2.5)
|
Voltages measured on the backplane.
|
Power supply current (PS1)
|
Current measured on the power supply.
|
The following example is for the Cisco 7500 series router. This example shows the measurements immediately before the last shutdown.
7500# show environment last
RSP(4) Inlet previously measured at 37C/98F
RSP(4) Hotpoint previously measured at 46C/114F
RSP(4) Exhaust previously measured at 52C/125F
+12 Voltage previously measured at 12.26
+5 Voltage previously measured at 5.17
-12 Voltage previously measured at -12.03
+24 Voltage previously measured at 23.78
Table 84 describes the fields shown in the display.
Table 84 show environment last Field Descriptions for the Cisco 7500
Field
|
Description
|
RSP(4) Inlet, Hotpoint, Exhaust
|
Temperature measurements at the inlet, hotpoint, and exhaust areas of the card.
|
Voltages
|
Voltages measured on the backplane.
|
The following example is for the Cisco 7500 series router. This information lists the temperature and voltage thresholds for each sensor. These thresholds indicate when error messages occur. There are two level of messages: warning and critical.
7500# show environment table
Sample Point LowCritical LowWarning HighWarning HighCritical
RSP(4) Inlet 44C/111F 50C/122F
RSP(4) Hotpoint 54C/129F 60C/140F
+12 Voltage 10.90 11.61 12.82 13.38
+5 Voltage 4.61 4.94 5.46 5.70
-12 Voltage -10.15 -10.76 -13.25 -13.86
+24 Voltage 20.38 21.51 26.42 27.65
Shutdown boards at 70C/158F
Shutdown power supplies at 76C/168F
Restart after shutdown below 40C/104F
Table 85 describes the fields shown in the display.
Table 85 show environment table Field Descriptions for the Cisco 7500
Field
|
Description
|
Sample Point
|
Area for which measurements are taken.
|
LowCritical
|
Level at which a critical message is issued for an out-of-tolerance voltage condition. The system continues to operate; however, the system is approaching shutdown.
|
LowWarning
|
Level at which a warning message is issued for an out-of-tolerance voltage condition. The system continues to operate, but operator action is recommended to bring the system back to a normal state.
|
HighWarning
|
Level at which a warning message is issued. The system continues to operate, but operator action is recommended to bring the system back to a normal state.
|
HighCritical
|
Level at which a critical message is issued. For the chassis, the router is shut down. For the power supply, the power supply is shut down.
|
Shutdown boards at
|
The card is shut down if the specified temperature is met.
|
Shutdown power supplies at
|
The system is shut down if the specified temperature is met.
|
Restart after shutdown
|
The system will restart when the specified temperature is met.
|
Cisco 12000 Series GSR
The following examples are for the Cisco 12000 series Gigabit Switch Routers.
The following is sample output from the show environment command for a Cisco 12012. Slots 0 through 11 are the line cards, slots 16 and 17 are the clock and scheduler cards, slots 18 through 20 are the switch fabric cards, slots 24 through 26 are the power supplies, and slots 28 and 29 are the blowers. An "NA" in the table means that no values was returned. In some cases it is because the equipment is not supported for that environmental parameter (for example, the power supply and blowers in slots 24, 26, 28, and 29 do not have a 3V power supply so an NA is displayed).
Slot # 3V 5V MBUS 5V Hot Sensor Inlet Sensor
(mv) (mv) (mv) (deg C) (deg C)
0 3300 4992 5040 42.0 37.0
2 3296 4976 5136 40.0 33.0
4 3280 4992 5120 38.5 31.5
7 3280 4984 5136 42.0 32.0
9 3292 4968 5160 39.5 31.5
11 3288 4992 5152 40.0 30.5
16 3308 NA 5056 42.5 38.0
17 3292 NA 5056 40.5 36.5
18 3304 NA 5176 36.5 35.0
19 3300 NA 5184 37.5 33.5
20 3304 NA 5168 36.5 34.0
Table 86 describes the fields shown and lists the equipment supported by each environmental parameter. "NA" indicates the reading could not be obtained. Try the command again.
Table 86 show environment Field Descriptions for Cisco 12000
Field
|
Description
|
Slot #
|
Slot number of the equipment. On the Cisco 12012, slots 0 through 11 are the line cards, slots 16 and 17 are the clock and scheduler cards, slots 18 through 20 are the switch fabric cards, slots 24 through 27 are the power supplies, and slots 28 and 29 are the blowers.
|
3V (mv)
|
Measures the 3-volt power supply on the card. The 3-volt power supply is on the line cards, GRP card, clock and scheduler cards, and switch fabric cards.
|
5V (mv)
|
Measures the 5-volt power supply on the card. The 5-volt power supply is on the line cards, GRP card, and power supplies.
|
MBUS 5V (mv)
|
Measures the 5-volt MBus on the card. The 5-volt MBus is on all equipment.
|
Hot Sensor (deg C)
|
Measures the temperature at the hot sensor on the card. The hot sensor is on the line cards, GRP card, clock and scheduler cards, switch fabric cards, and blowers.
|
Inlet Sensor (deg C)
|
Measures the current inlet temperature on the card. The inlet sensor is on the line cards, GRP card, clock and scheduler cards, switch fabric cards, and power supplies.
|
48V (Volt)
|
Measures the DC power supplies.
|
AMP_48 (Amp)
|
Measures the AC power supplies.
|
Fan 0, Fan 1, Fan 2
|
Measures the fan speed in rotations per minute.
|
The following is sample output from the show environment all command for the Cisco 12008. Slots 0 through 7 are the line cards, slots 16 and 17 are the clock scheduler cards (the clock scheduler cards control the fans), slots 18 through 20 are the switch fabric cards, and slots 24 and 26 are the power supplies. The Cisco 12008 does not support slots 25, 27, 28, and 29. An "NA" in the table means that no values was returned. In some cases it is because the equipment is not supported for that environmental parameter (for example, the power supplies in slots 24 and 26 do not have a hot sensor, so an NA is displayed).
Router# show environment all
Slot # Hot Sensor Inlet Sensor
Slot # 5V MBUS 5V 48V AMP_48
16 Voltage 16V Speed slow: Main Fans Ok Power Supply fans Ok
Slot # Card Specific Leds
The following is sample output from the show environment table command for a Cisco 12012. The show environment table command lists the warning, critical, and shutdown limits on your system and includes the GRP card and line cards (slots 0-15), clock and scheduler cards (slots 16-17), switch fabric cards (slots 18-20), and blowers.
Router# show environment table
Hot Sensor Temperature Limits (deg C):
Warning Critical Shutdown
GRP/GLC (Slots 0-15) 40 46 57
CSC (Slots 16-17) 46 51 65
SFC (Slots 18-20) 41 46 60
Inlet Sensor Temperature Limits (deg C):
Warning Critical Shutdown
GRP/GLC (Slots 0-15) 35 40 52
CSC (Slots 16-17) 40 45 59
SFC (Slots 18-20) 37 42 54
Warning Critical Shutdown
Below Above Below Above Below Above
GRP/GLC (Slots 0-15) 3200 3400 3100 3500 3050 3550
CSC (Slots 16-17) 3200 3400 3100 3500 3050 3550
SFC (Slots 18-20) 3200 3400 3100 3500 3050 3550
Warning Critical Shutdown
Below Above Below Above Below Above
GRP/GLC (Slots 0-15) 4850 5150 4750 5250 4680 5320
Warning Critical Shutdown
Below Above Below Above Below Above
GRP/GLC (Slots 0-15) 5000 5250 4900 5350 4750 5450
CSC (Slots 16-17) 4820 5150 4720 5250 4750 5450
SFC (Slots 17-20) 5000 5250 4900 5350 4750 5450
Blower Operational Range (RPM):
The following is sample output from the show environment leds command for a Cisco 12012. The show environment leds command lists the status of the MBus LEDs on the clock, scheduler, and the switch fabric cards.
Router# show environment leds
show gsr
To display hardware information on the Cisco 12000 series Gigabit Switch Routers (GSRs), use the show gsr EXEC command.
show gsr [chassis-info [details]]
Syntax Description
chassis-info
|
(Optional) Displays backplane NVRAM information.
|
details
|
(Optional) In addition to the information displayed, this option includes hexadecimal output of the backplane NVRAM information.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
11.2 GS
|
This command was added to support the Cisco 12000 series Gigabit Switch Routers.
|
Usage Guidelines
Use this command to determine the type of hardware installed in your Cisco 12000 series GSR router.
Examples
The following is sample output from the show gsr command for a Cisco 12012. This command shows the type and state of the card installed in the slot.
Slot 0 type = Route Processor
state = IOS Running MASTER
Slot 7 type = 1 Port Packet Over SONET OC-12c/STM-4c
Slot 16 type = Clock Scheduler Card
state = Card Powered PRIMARY CLOCK
The following is sample output from the show gsr chassis-info command for a Cisco 12012:
Router# show gsr chassis-info
Backplane NVRAM [version 0x20] Contents -
Chassis: type 12012 Fab Ver: 1
Chassis S/N: ZQ24CS3WT86MGVHL
PCA: 800-3015-1 rev: A0 dev: 257 HW ver: 1.0
Backplane S/N: A109EXPR75FUNYJK
MAC Addr: base 0000.EAB2.34FF block size: 1024
RMA Number: 0x5F-0x2D-0x44 code: 0x01 hist: 0x1A
show gt64010 (Cisco 7200 series)
To display all GT64010 internal registers and interrupt status on the Cisco 7200 series routers, use the show gt64010 EXEC command.
show gt64010
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Release
|
Modification
|
11.2
|
This command was introduced.
|
Usage Guidelines
This command displays information about the CPU interface, DRAM/device address space, device parameters, DMA channels, timers and counters, and PCI internal registers. The information is generally useful for diagnostic tasks performed by technical support only.
Examples
The following is a partial sample output for the show gt64010 command:
dma_list=0x6088C3EC, dma_ring=0x4B018480, dma_entries=256
dma_free=0x6088CECC, dma_reqt=0x6088CECC, dma_done=0x6088CECC
thread=0x6088CEAC, thread_end=0x6088CEAC
backup_thread=0x0, backup_thread_end=0x0
dma_working=0, dma_complete=6231, post_coalesce_frames=6231
exhausted_dma_entries=0, post_coalesce_callback=6231
GT64010 Register Dump: Registers at 0xB4000000
cpu_interface_conf : 0x80030000 (b/s 0x00000380)
addr_decode_err : 0xFFFFFFFF (b/s 0xFFFFFFFF)
Processor Address Space :
ras10_low : 0x00000000 (b/s 0x00000000)
ras10_high : 0x07000000 (b/s 0x00000007)
ras32_low : 0x08000000 (b/s 0x00000008)
ras32_high : 0x0F000000 (b/s 0x0000000F)
cs20_low : 0xD0000000 (b/s 0x000000D0)
cs20_high : 0x74000000 (b/s 0x00000074)
cs3_boot_low : 0xF8000000 (b/s 0x000000F8)
cs3_boot_high : 0x7E000000 (b/s 0x0000007E)
pci_io_low : 0x00080000 (b/s 0x00000800)
pci_io_high : 0x00000000 (b/s 0x00000000)
pci_mem_low : 0x00020000 (b/s 0x00000200)
pci_mem_high : 0x7F000000 (b/s 0x0000007F)
internal_spc_decode : 0xA0000000 (b/s 0x000000A0)
bus_err_low : 0x00000000 (b/s 0x00000000)
bus_err_high : 0x00000000 (b/s 0x00000000)
show logging
To display the state of logging (syslog), use the show logging privileged EXEC command.
show logging [ slot slot-number | summary]
Syntax Description
slot slot-number
|
(Optional) Displays information in the syslog history table for a specific line card. Slot numbers range from 0 to 11 for the Cisco 12012 and 0 to 7 for the Cisco 12008.
|
summary
|
(Optional) Displays counts of messages by type for each line card.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
11.2 GS
|
The slot and summary keywords were added for Cisco 12000 Series platforms.
|
Usage Guidelines
This command displays the state of syslog error and event logging, including host addresses, and whether console logging is enabled. This command also displays Simple Network Management Protocol (SNMP) configuration parameters and protocol activity.
Examples
The following is sample output from the show logging command:
Console logging: disabled
Monitor logging: level debugging, 266 messages logged.
Trap logging: level informational, 266 messages logged.
SNMP logging: disabled, retransmission after 30 seconds
Table 87 describes significant fields shown in the display.
Table 87 show logging in Field Descriptions
Field
|
Description
|
Syslog logging
|
When enabled, system logging messages are sent to a UNIX host that acts as a syslog server; that is, it captures and saves the messages.
|
Console logging
|
If enabled, states the level; otherwise, this field displays disabled.
|
Monitor logging
|
Minimum level of severity required for a log message to be sent to a monitor terminal (not the console).
|
Trap logging
|
Minimum level of severity required for a log message to be sent to a syslog server.
|
SNMP logging
|
Shows whether SNMP logging is enabled and the number of messages logged, and the retransmission interval.
|
The following is sample output from the show logging summary command on a Cisco 12012. A number in the column indicates that the syslog contains that many messages for the line card. For example, line card in slot 9 has 1 error message, 4 warning messages, and 47 notification messages.
Router# show logging summary
+-----+-------+-------+-------+-------+-------+-------+-------+-------+
SLOT | EMERG | ALERT | CRIT | ERROR |WARNING| NOTICE| INFO | DEBUG |
+-----+-------+-------+-------+-------+-------+-------+-------+-------+
|* 0* | . | . | . | . | . | . | . | . |
| 2 | | | | 1 | 4 | 45 | | |
| 4 | | | | 5 | 4 | 54 | | |
| 7 | | | | 17 | 4 | 48 | | |
| 9 | | | | 1 | 4 | 47 | | |
| 11 | | | | 12 | 4 | 65 | | |
+-----+-------+-------+-------+-------+-------+-------+-------+-------+
Table 88 describes the logging level fields shown in the display.
Table 88 show logging summary Field Descriptions
Field
|
Description
|
SLOT
|
Indicates the slot number of the line card. An asterisk next to the slot number indicates the GRP card whose error message counts are not displayed. For information on the GRP card, use the show logging command.
|
EMERG
|
Indicates the system is unusable.
|
ALERT
|
Indicates immediate action is needed.
|
CRIT
|
Indicates a critical condition.
|
ERROR
|
Indicates an error condition.
|
WARNING
|
Indicates a warning condition.
|
NOTIFICE
|
Indicates a normal but significant condition.
|
INFO
|
Indicates an informational message only.
|
DEBUG
|
Indicates a debugging message.
|
Related Commands
Command
|
Description
|
clear logging
|
Clears messages from the logging buffer.
|
logging history size
|
Changes the number of syslog messages stored in the history table of the router.
|
logging linecard
|
Logs messages to an internal buffer on a line card. This command limits the logging messages displayed on terminal lines other than the console line to messages with a level at or above level.
|
show logging history
To display information about the state of the syslog history table, use the show logging history privileged EXEC command.
show logging history
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
Usage Guidelines
This command displays information about the syslog history table, such as the table size, the status of messages, and text of messages stored in the table. Messages stored in the table are governed by the logging history global configuration command.
Examples
The following example shows sample output from the show logging history command. In this example, notifications of severity level 5 (notifications) through severity level 0 (emergencies) are configured to be written to the logging history table.
Router# show logging history
Syslog History Table: 1 maximum table entries,
saving level notifications or higher
0 messages ignored, 0 dropped, 15 table entries flushed,
SNMP notifications not enabled
entry number 16: SYS-5-CONFIG_I
Configured from console by console
Table 88 describes the significant fields shown in the output.
Table 89 show logging history Field Descriptions
Field
|
Description
|
maximum table entry
|
Number of messages that can be stored in the history table. Set with the logging history size command.
|
saving level notifications <x> or higher
|
Level of messages that are stored in the history table and sent to the SNMP server (if SNMP notification is enabled). The severity level can be configured with the logging history command.
|
messages ignored
|
Number of messages not stored in the history table because the severity level is greater than that specified with the logging history command.
|
dropped
|
Number of messages that could not be processed due to lack of system resources. Dropped messages do not appear in the history table and are not sent to the SNMP server.
|
table entries flushed
|
Number of messages that have been removed from the history table to make room for newer messages.
|
SNMP notifications
|
Whether syslog traps of the appropriate level are sent to the SNMP server. The sending of syslog traps are enabled or disabled through the snmp-server enable traps syslog command.
|
entry number:
|
Number of the message entry in the history table. In the example above, the message "SYS-5-CONFIG_I Configured from console by console" indicates a syslog message consisting of the facility name (SYS), which indicates where the message came from, the severity level (5) of the message, the message name (CONFIG_I), and the message text.
|
timestamp
|
Time, based on the up time of the router, that the message was generated.
|
Related Commands
Command
|
Description
|
clear logging
|
Clears messages from the logging buffer.
|
logging history
|
Limits syslog messages sent to the router's history table to a specified severity level.
|
logging history size
|
Changes the number of syslog messages that can be stored in the history table.
|
logging linecard
|
Logs messages to an internal buffer on a line card. This command limits the logging messages displayed on terminal lines other than the console line to messages with a level at or above level.
|
snmp-server enable traps
|
The [no] snmp-server enable traps syslog form of this command controls (enables or disables) the sending of system-logging messages to a network management station.
|
show memory
To show statistics about memory, including memory-free pool statistics, use the show memory EXEC command.
show memory [memory-type] [free] [summary]
Syntax Description
memory-type
|
(Optional) Memory type to display (processor, multibus, io, sram). If type is not specified, statistics for all memory types present are displayed.
|
free
|
(Optional) Displays free memory statistics.
|
summary
|
(Optional) Displays a summary of memory usage including the size and number of blocks allocated for each address of the system call that allocated the block.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
Usage Guidelines
The show memory command displays information about memory available after the system image decompresses and loads.
Examples
The following is sample output from the show memory command:
Head Total(b) Used(b) Free(b) Lowest(b) Largest(b)
Processor B0EE38 5181896 2210036 2971860 2692456 2845368
Address Bytes Prev. Next Ref PrevF NextF Alloc PC What
B0EE38 1056 0 B0F280 1 18F132 List Elements
B0F280 2656 B0EE38 B0FD08 1 18F132 List Headers
B0FD08 2520 B0F280 B10708 1 141384 TTY data
B10708 2000 B0FD08 B10F00 1 14353C TTY Input Buf
B10F00 512 B10708 B11128 1 14356C TTY Output Buf
B11128 2000 B10F00 B11920 1 1A110E Interrupt Stack
B11920 44 B11128 B11974 1 970DE8 *Init*
B11974 1056 B11920 B11DBC 1 18F132 messages
B11DBC 84 B11974 B11E38 1 19ABCE Watched Boolean
B11E38 84 B11DBC B11EB4 1 19ABCE Watched Boolean
B11EB4 84 B11E38 B11F30 1 19ABCE Watched Boolean
B11F30 84 B11EB4 B11FAC 1 19ABCE Watched Boolean
The following is sample output from the show memory free command:
Head Total(b) Used(b) Free(b) Lowest(b) Largest(b)
Processor B0EE38 5181896 2210076 2971820 2692456 2845368
Address Bytes Prev. Next Ref PrevF NextF Alloc PC What
CEB844 32 CEB7A4 CEB88C 0 0 0 96B894 SSE Manager
D35ED4 80 D35E30 D35F4C 0 0 D27AE8 96B894 SSE Manager
D27AE8 80 D27A48 D27B60 0 D35ED4 0 22585E SSE Manager
D0A8F4 100 D0A8B0 D0A980 0 0 0 2258DA SSE Manager
B59EF0 108 B59E8C B59F84 0 0 0 2258DA (fragment)
The display of show memory free contains the same types of information as the show memory display, except that only free memory is displayed, and the information is displayed in order for each free list.
The first section of the display inc