|
|
This chapter describes the EXEC commands you use to monitor, manage, and troubleshoot general system processes and conditions on your network server. These processes and conditions include:
This chapter also provides a general overview of these system tasks:
See the chapters containing information about the interfaces and the protocols supported by Cisco software for descriptions of the interface-specific and protocol-specific debugging and monitoring commands.
Most of the network management commands are executed at the privileged-level prompt, although there is a subset of monitoring commands that you can enter at the user-level prompt.
At the end of the chapter is an alphabetically arranged summary of the commands it describes.
Use the EXEC show commands to display data structures, configuration parameters, and usage statistics for the network server. To list all the available show command options, enter this command at the EXEC prompt.
show ?Two different lists will be displayed, one at the user-level prompt, and one at the enabled, privileged-level prompt. The lists include a summary of the command function, for easy reference. See the "First-Time Startup and Basic Configuration" chapter of this manual for the procedure to enter the user and privileged levels.
The network server has one pool of queuing elements and five pools of packet buffers of different sizes. For each pool, the network server keeps counts of the number of buffers outstanding, the number of buffers in the free list, and the maximum number of buffers allowed in the free list. To display statistics for the buffer pools on the network server, use the show buffers command. Enter this command at the EXEC prompt:
show buffers [interface]The optional argument interface causes a search of all buffers that have been associated with that interface for longer than one minute. The contents of these buffers are printed to the screen. This option is useful in diagnosing problems where the input queue count on an interface is consistently nonzero.
Following is sample output without the optional interface argument. Table 1-1 describes the fields.
Buffer elements:
250 in free list (250 max allowed)
10816 hits, 0 misses, 0 created
Small buffers, 104 bytes (total 120, permanent 120):
120 in free list (0 min, 250 max allowed)
26665 hits, 0 misses, 0 trims, 0 created
Middle buffers, 600 bytes (total 90, permanent 90):
90 in free list (0 min, 200 max allowed)
5468 hits, 0 misses, 0 trims, 0 created
Big buffers, 1524 bytes (total 90, permanent 90):
90 in free list (0 min, 300 max allowed)
1447 hits, 0 misses, 0 trims, 0 created
Large buffers, 5024 bytes (total 0, permanent 0):
0 in free list (0 min, 100 max allowed)
0 hits, 0 misses, 0 trims, 0 created
Huge buffers, 12024 bytes (total 0, permanent 0):
0 in free list (0 min, 30 max allowed)
0 hits, 0 misses, 0 trims, 0 created
0 failures (0 no memory)
| Field | Description |
|---|---|
| Buffer elements | Blocks of memory used in internal operating system queues |
| Small buffers Middle buffers Big buffers Large buffers Huge buffers | Blocks of memory used to hold network packets |
| hits | Count of successful attempts to allocate a buffer when needed |
| misses | Count of allocation attempts that failed for lack of a free buffer in the pool |
| created | Count of new buffers created |
| trims | Count of buffers destroyed |
| in free list | Number of buffers of a given type that are not currently allocated and are available for use |
| max allowed | Maximum number of buffers of a given type allowed in the system |
| failures | Total number of allocation requests that have failed for lack of a free buffer |
| no memory | Number of failures due to a lack of memory to create a new buffer |
To show statistics about the memory, use the show memory command. Enter this command at the EXEC prompt:
show memoryThis command displays memory free pool statistics. These statistics include summary information about the activities of the system memory allocator and a block-by-block listing of memory use. Sample output follows. Table 1-2 describes the fields; Table 1-3 lists the characteristics of each block of memory in the system.
router> show memory
Head Free Start Total Bytes Used Bytes Free Bytes
Processor 6F1148 79071C 3206840 720468 2486372
Address Bytes Prev. Next Ref PrevF NextF Alloc PC What
6F1148 948 0 6F14FC 1 62FA9A *Init*
6F14FC 2032 6F1148 6F1CEC 1 60BF9C *Init*
6F1CEC 544 6F14FC 6F1F0C 1 60BFC6 *Init*
6F1F0C 2032 6F1CEC 6F26FC 1 602444 *Init*
6F26FC 52 6F1F0C 6F2730 1 63A3E0 *Init*
6F2730 80 6F26FC 6F2780 1 622DB0 *Init*
6F2780 52 6F2730 6F27B4 1 63A3E0 *Init*
6F27B4 112 6F2780 6F2824 1 606748 *Init*
6F2824 4032 6F27B4 6F37E4 1 60817A *Init*
| Field | Description |
|---|---|
| Head | Hexadecimal address of the head of the memory allocation chain |
| Free Start | Hexadecimal address of the base of the free list |
| Total Bytes | Total amount of system memory |
| Used Bytes | Amount of memory in use |
| Free Bytes | Amount of memory not in use |
| Field | Description |
|---|---|
| Address | Hexadecimal address of block |
| Bytes | Size of block in bytes |
| Prev | Address of previous block (should match address on previous line) |
| Next | Address of next block (should match address on next line) |
| Ref | Reference count for that block of memory, indicating how many different processes are using that block of memory |
| Free? | Tells whether the block is free |
| Alloc PC | Address of the system call that allocated the block |
| What | Name of process that owns the block |
The show memory io command displays the free IO memory blocks.On the IGS and Cisco 4000, this command quickly shows how much unused IO memory is available.
The show memory sram command displays the free SRAM memory blocks. For the Cisco 4000, this command supports the high-speed static RAM memory pool to make it easier to debug or diagnose problems with allocation or freeing of such memory.
With these changes, the show memory command on the Cisco 4000 now includes information about SRAM memory and IO memory, and appears as follows:
router# show memory
Head Free Start Total Bytes Used Bytes Free Bytes
SRAM 1000 7AE0 65538 27360 38178
Processor 20CFC4 23E178 2043964 282372 1761592
IO memory 6000000 6132DA0 4194656 1471412 2723244
Address Bytes Prev. Next Ref PrevF NextF Alloc PC What
1000 2032 0 17F0 1 3E73E *Init*
17F0 2032 1000 1FE0 1 3E73E *Init*
1FE0 544 17F0 2200 1 3276A *Init*
2200 52 1FE0 2234 1 31D68 *Init*
2234 52 2200 2268 1 31DAA *Init*
2268 52 2234 229C 1 31DF2 *Init*
72F0 2032 6E5C 7AE0 1 3E73E Init
7AE0 38178 72F0 0 0 0 0 0
The show memory io command, which shows free IO memory, appears as follows:
router# show memory io
Address Bytes Prev. Next Ref PrevF NextF Alloc PC What
6132DA0 59264 6132664 6141520 0 0 600DDEC 3FCF0 *Packet Buffer*
600DDEC 500 600DA4C 600DFE0 0 6132DA0 600FE68 0
600FE68 376 600FAC8 600FFE0 0 600DDEC 6011D54 0
6011D54 652 60119B4 6011FE0 0 600FE68 6013D54 0
614FCA0 832 614F564 614FFE0 0 601FD54 6177640 0
6177640 2657056 6172E90 0 0 614FCA0 0 0
Total: 2723244
The show memory sram command, which shows free SRAM memory, appears as follows:
router# show memory sram
Address Bytes Prev. Next Ref PrevF NextF Alloc PC What
7AE0 38178 72F0 0 0 0 0 0
Total: 38178
To see information about the active processes, use the show processes command. Enter this command at the EXEC prompt:
show processesFollowing is a partial display of the command output. Table 1-4 describes the fields.
CPU utilization for five seconds: 19%; one minute: 12%; five minutes: 12%
PID Q T PC Runtime (ms) Invoked uSecs Stacks TTY Process
1 M E 17518 40072 830 48279 606/800 0 Net Background
2 M E 5040 932 11 84727 486/800 0 Logger
32 M E 4C390 73012 6141 11889 480/800 0 IGRP Router
4 M E 22984 172 252 682 662/800 0 BOOTP Server
5 H E 5040 100324 66619 1505 606/900 0 IP Input
6 M E 21278 12188 22451 542 508/800 0 IP Protocols
7 M E 32F32 32 10926 2 592/800 0 TCP Timer
8 L E 33C1E 508 28 18142 576/800 0 TCP Protocols
9 L E 5040 1104 935 1180 666/800 0 ARP Input
10 L E 5040 352 458 768 674/800 0 Probe Input
11 H E 5040 2636 9077 290 710/800 0 Net Input
12 M T 2CF2 36976 49175 751 602/800 0 TTY Background
13 H E 5040 0 2 0 852/900 0 DECnet Input
14 M E 44AE4 21964 18029 1218 742/900 0 DECnet Routing
| Field | Description |
|---|---|
| CPU utilization | Ratio of current idle time over the longest idle time. Gives the user a general idea of how busy the processor is. |
| PID | Process ID |
| Q | Process queue priority (high, medium, low) |
| T | Scheduler test (Event, Time, Suspended) |
| PC | Current program counter |
| Runtime (ms) | CPU time the process has used, in milliseconds |
| Invoked | Number of times the process has been invoked |
| uSecs | Microseconds of CPU time for each invocation |
| Stacks | Low water mark/Total stack space available |
| TTY | Terminal that controls the process |
| Process | Name of process |
To show memory utilization, use the show processes memory command. Enter this command at the EXEC prompt:
show processes memoryThe show processes memory command monitors the memory utilization of processes. The following is a display of sample output. Table 1-5 describes the fields.
Total: 2416588, Used: 530908, Free: 1885680
PID TTY Allocated Freed Holding Process
0 0 462708 2048 460660 *Init*
0 0 76 4328 - 4252 *Sched*
0 0 82732 33696 49036 *Dead*
1 0 2616 0 2616 Net Background
2 0 0 0 0 Logger
21 0 20156 40 20116 IGRP Router
4 0 104 0 104 BOOTP Server
5 0 0 0 0 IP Input
6 0 0 0 0 TCP Timer
7 0 360 0 360 TCP Protocols
8 0 0 0 0 ARP Input
9 0 0 0 0 Probe Input
10 0 0 0 0 MOP Protocols
11 0 0 0 0 Timers
12 0 0 0 0 Net Input
530936 Total
| Field | Description |
|---|---|
| PID | Process ID |
| TTY | Terminal that controls the process |
| Allocated | Sum of all memory that process has requested from the system |
| Freed | Amount of memory a process has returned to the system |
| Holding | Allocated memory minus freed memory; can be negative when it has freed more than it was allocated |
| Process | Process name |
| *Init* | System initialization |
| *Sched* | The scheduler |
| *Dead* | Processes as a group that are now dead |
| Total | Total amount of memory held |
To show stack utilization, use the show stacks command. Enter this command at the EXEC prompt:
show stacksThe show stacks command monitors the stack utilization of processes and interrupt routines. Its display includes the reason for the last system reboot. If the system was reloaded because of a system failure, a saved system stack trace is displayed. This information can be useful for analyzing crashes in the field.
To display the contents of the nonvolatile memory, if present and valid, use the show configuration command. Enter this command at the EXEC prompt:
show configurationThe nonvolatile memory stores the configuration information in the network server in text form as configuration commands.
To show the state of logging (syslog), use the show logging command. Enter this command at the EXEC prompt:
show loggingThis command displays the state of syslog error and event logging, including host addresses, and whether console logging is enabled. This command also displays SNMP (Simple Network Management Protocol) configuration parameters and protocol activity. See the section "Redirecting System Error Messages" in the "Configuring the System" chapter of this manual for an explanation of how to configure message logging. Following is a sample output. Table 1-6 describes the fields.
Syslog logging: enabled
Console logging: disabled
Monitor logging: level debugging, 266 messages logged.
Trap logging: level informational, 266 messages logged.
Logging to 131.108.2.238
SNMP logging: disabled, retransmission after 30 seconds
0 messages logged
| 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 | The minimum level of severity required for a log message to be sent to a monitor terminal (not the console). |
| Trap logging | The minimum level of severity required for a log message to be sent to syslog server. |
| SNMP logging | Shows whether SNMP logging is enabled, the number of messages logged, and the retransmission interval. |
To display the configured protocols, use the show protocols command. Enter this command at the EXEC prompt:
show protocolsThe command shows the global and interface-specific status of any configured Level 3 protocol; for example, IP, DECnet, Novell, AppleTalk, and so forth. The following is sample output:
Global values: Internet Protocol routing is enabled DECNET routing is enabled XNS routing is enabled Appletalk routing is enabled X.25 routing is enabled Ethernet 0 is up, line protocol is up Internet address is 131.108.1.1, subnet mask is 255.255.255.0 Decnet cost is 5 XNS address is 2001.AA00.0400.06CC AppleTalk address is 4.129, zone Twilight Serial 0 is up, line protocol is up Internet address is 192.31.7.49, subnet mask is 255.255.255.240 Ethernet 1 is up, line protocol is up Internet address is 131.108.2.1, subnet mask is 255.255.255.0 Decnet cost is 5 XNS address is 2002.AA00.0400.06CC AppleTalk address is 254.132, zone Twilight Serial 1 is down, line protocol is down Internet address is 192.31.7.177, subnet mask is 255.255.255.240 AppleTalk address is 999.1, zone Magnolia Estates
Use the show environment command to display temperature and voltage information on the AGS+ console. The following is a sample of this command's usage and output:
show environment
Router# show environment
Environmental controller firmware version 2.0
Serial number is 00220846, calibrated on 2-14-92, by technician rma
Internal temperature measured 34.3(C), shuts down at 43.0(C)
Air flow appears good.
+5 volt line measured at 5.061(V)
+12 volt line measured at 12.120(V)
-12 volt line measured at -11.936(V)
-5 volt line measured at -4.986(V)
Router#
Once a minute a routine is run that gets environmental measurements from the CSC-ENVM card and stores the show environment 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 CSC-ENVM card for measurements once a minute, but warnings for a given testpoint are printed at most once every four hours. If a measurement is out of line within a four-hour period, an automatic warning message appears on the console. As noted, the user can query the CSC-ENVM using the show environment command at any time to determine whether a measurement is at the warning tolerance.
The following is an example of a message that displays on the system console when a measurement has exceeded an acceptable margin:
Router# ENVIRONMENTAL WARNING: Air flow appears marginal.
The following is an example of a message that displays on the system console when a measurement has exceeded an acceptable margin. In this example, the internal temperature reading is given.
Router# ENVIRONMENTAL WARNING: Internal temperature measured 41.3(C)
The following is an example of a message that displays on the system console when a voltage measurement has exceeded an acceptable margin:
Router# ENVIRONMENTAL WARNING: +5 volt testpoint measured 5.310(V)
If the CSC-ENVM card on the AGS+ chassis detects that any of its voltage or temperature testpoints has exceeded maximum margins, it does the following in this order:
Step 1: Saves the last measured values from each of the six testpoints to internal nonvolatile memory.
Step 2: Interrupts the system software and causes a shutdown message to be printed on the system console.
Step 3: Shuts off the power supply after a few milliseconds of delay.
The following is the message the system displays if voltage or temperature exceed maximum margins:
Router# SHUTDOWN: air flow problem
Refer to the hardware installation and maintenance publication for the specific chassis.
If a shutdown occurs due to detection of fatal environmental margins, the CSC-ENVM logs the last measured value from each of the six testpoints to internal nonvolatile memory. Only one set of measurements can be stored at any one time.
These testpoints can be displayed at any time with the show environment last command.
show environment last
Router# show environment last
Environmental controller firmware version 2.0
Serial number is 3232, calibrated on 2-14-92, by technician rma
Internal temperature measured 24.1(C), shuts down at 43.0(C)
Air flow appears good.
+5 volt line measured at 4.988(V)
+12 volt line measured at 12.044(V)
-12 volt line measured at -11.787(V)
-5 volt line measured at -4.939(V)
LAST Environmental Shutdown Measurements:
Internal temperature was 24.0(C)
Air flow sensor was good
+5 volt line was 4.990(V)
+12 volt line was 9.900(V)*
-12 volt line was -11.719(V)
-5 volt line was -4.926(V)
The first block of data is equivalent to show environment, in that it displays the current measurements. The second block shows all the testpoint values at the time of the LAST environmental shutdown. An asterisk suffixes the testpoint that caused the failure. In the preceding example, we see that the +12-volt testpoint dropped to 9.900(V) to cause the shutdown.
This section describes the EXEC commands you can use to perform the following tasks:
Use the following command to display temperature and voltage information on the Cisco 7000 console:
show environment [all|last|table]The keyword all displays voltage and temperature statistics. The keyword last displays the reasons for, and the environmental statistics at the time of, the last environmental shutdown The keyword table displays current environmental status along with a table of voltage and temperature parameters for the system.
Use the following command to display a message indicating whether an environmental warning condition currently exists:
show environmentThis example shows the typical show environment display when the optional all, last, and table keywords are not used and there are no warning conditions in the system. 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.
env-chassis> show env
Environmental Statistics
Environmental status as of Thu 10-22-1992 13:17:39
Data is 7 second(s) old, refresh in 53 second(s)
All Environmental Measurements are within specifications
Table 1-7 describes the show environment display fields.
| Field | Description |
|---|---|
| Environmental status as of... | Current date and time. |
| Data age and refresh | 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. |
Use the following command to display the environmental statistics for your router:
show environment allThis example shows the show environment all display when there are no warning conditions in the system.
env-chassis> show env all
Environmental Statistics
Environmental status as of Thu 10-22-1992 13:17:39
Data is 11 second(s) old, refresh in 49 second(s)
All Environmental Measurements are within specifications
Lower Power Supply: 700W, ON Upper Power Supply: Not Installed
No Intermittent Powerfails
+12 volt measured at 12.05(V)
+5 volt measured at 4.92(V)
-12 volt measured at -12.00(V)
+24 volt measured at 23.80(V)
Airflow temperature measured at 30(C)
Inlet temperature measured at 25(C)
In the following example, there have been two intermittent power failures since the router was turned on, and the lower power supply is not functioning. The last intermittent power failure occurred on Sunday, October 25, 1992, at 11:07 p.m.
env-chassis# show env all
Environmental Statistics
Environmental status as of Sun 10-25-1992 23:19:47
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 Sun 10-25-1992 23:07:05
+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 1-8 describes the show environment all display fields.
| Field | Description |
|---|---|
| Environmental status as of... | Date and time of last query. |
| Data age and refresh | Environmental measurements are output into buffer every 60 seconds unless other higher-priority processes are running. |
| Warning | Warning messages displayed if environmental measurements are not within specification. |
| Power Supply | Type of power supply installed and its status. |
| Intermittent Powerfails | Number of power hits (not resulting in shutdown) since system was last booted. |
| Voltage Specifications | System voltage measurements. |
| Airflow and Inlet temperature | Temperature of air coming in and going out. |
If a shutdown occurs because fatal environmental margins are detected, the route processor (RP) logs to internal nonvolatile memory the last measured value from each of the six test points. Only one set of measurements can be stored at any one time.
Use the following command to show environmental statistics at the time of the last shutdown:
show environment lastIn the following example, the last keyword is used. The router retrieves the environmental statistics at the time of the last shutdown. In this example, the last shutdown was Tuesday, May 19, 1992 at 12:40 p.m., so the environmental statistics at that time are displayed.
env-chassis# show env last
Environmental Statistics
Environmental status as of Thu 5-21-1992 14:47:00
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 Tues 5-19-1992 12:40:00
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)
+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 1-9 describes the show environment last display fields.
| Field | Description |
|---|---|
| Environmental status as of... | Current date and time. |
| Data age and refresh | Environmental measurements output into buffer every 60 seconds, unless other higher-priority processes are running. |
| Specifications | If environmental measurements are not within specification, warning messages are displayed. |
| LAST | Displays test point values at time of the last environmental shutdown. |
The environmental monitor is built into the route processor (RP). If a measurement exceeds acceptable margins, a warning message is printed to the system console. The system software queries the RP for measurements once every 60 seconds, but warnings for a given test point are printed at most once every four hours. If the temperature measurements are out of specification more than the shutdown margin, the software will shut the router down but the fan will stay on. The router has to be manually turned off and on after such a shutdown. As noted, the user can query the RP using the show environment command at any time to determine whether a measurement is out of tolerance.
See Chapter 11 of this publication for a description of environmental monitor warning messages.
If the RP detects that any of its temperature test points have exceeded maximum margins, it performs the following steps in this order:
Step 1: Saves the last measured values from each of the six test points to internal nonvolatile memory.
Step 2: Interrupts the system software and causes a shutdown message to be printed on the system console.
Step 3: Shuts off the power supplies after a few milliseconds of delay.
The following is the message the system displays if temperatures exceed maximum margins, along with a message indicating the reason for the shutdown:
Router# %ENVM-1-SHUTDOWN: Environmental Monitor initiated shutdown %ENVM-2-TEMP: Inlet temperature has reached SHUTDOWN level at 64(C)
Refer to the appropriate Hardware Installation and Maintenance publication for more information about environmental specifications.
Use the following command to display environmental measurements and a table that lists the ranges of environment measurement that are within specification:
show environment tableThe following example 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.
target> show env table
Environmental Statistics
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)
Voltage Parameters:
SENSE CRITICAL NORMAL CRITICAL
-------|--------------------|------------------------|--------------------
+12(V) 10.20 12.05(V) 13.80
+5(V) 4.74 4.98(V) 5.26
-12(V) -10.20 -12.05(V) -13.80
+24(V) 20.00 24.00(V) 28.00
Temperature Parameters:
SENSE WARNING NORMAL WARNING CRITICAL SHUTDOWN
-------|-------------|------------|-------------|--------------|--------------
Airflow 10 60 70 73(C) 88
Inlet 10 39 41(C) 46 64
Table 1-10 describes the show environment table display fields.
| 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. |
NORMAL
| All monitored conditions meet normal requirements. |
WARNING
| System is approaching an out-of-tolerance condition. |
CRITICAL
| Out-of-tolerance condition exists. |
PROCESSOR SHUTDOWN
| Processor has detected condition that could cause physical damage to the system. |
You can configure and display the current date and time on your Cisco 7000 series router. This information is displayed using the show date and show time commands and is included in the show environment command displays documented earlier in this chapter.
Use the following commands in privileged EXEC mode to set the date and time:
date timeIn the following example, the date and time are set using the EXEC date command in privileged mode.
env-chassis>enablePassword: env-chassis# env-chassis#dateThu 10-22-1992 13:33:09 Enter date (mm-dd-yyyy)10-24-1992env-chassis# env-chassis#show dateSat 10-24-1992 13:33:21
In the following example, an invalid date, 11/36/92, is entered. The user is informed that this date is invalid.
env-chassis#dateSat 10-24-1992 13:33:38 Enter date (mm-dd-yyyy)11-36-1992Invalid Date Enter date (mm-dd-yyyy)11-06-1992env-chassis# env-chassis#show dateFri 11-6-1992 13:34:12 env-chassis#
In the following example, an invalid time, 26 hours, is configured and the user is informed that this is an invalid time.
env-chassis#timeFri 11-6-1992 14:22:06 Enter time (hh:mm:ss)26:44:20Invalid Time Enter time (hh:mm:ss)13:36:00env-chassis# env-chassis#show timeFri 11-6-1992 13:36:02
Use the following EXEC commands to display the date and time:
show {date|time}In the following examples, the show date and show time commands are used to display the date and time.
env-chassis>show dateThu 10-22-1992 13:31:06 env-chassis#show timeFri 11-6-1992 12:45:09
To verify that the CSC-MCI card or the CSC-ENVM card is properly connected to the CSC-MC+ card, use the show flash or show flash all commands. The show flash command displays the total amount of Flash memory present on the Flash card, the type of card connected to the Flash card, any files that may currently exist in Flash memory, and the amounts of Flash memory used and remaining. The show flash all command displays all the above information, but also shows all the information about each Flash memory device.
show flashFull details on Flash memory are found in the "Configuring the System" chapter of this manual.
The network server includes software to aid in tracking down problems with the network server or with other hosts on the network. The privileged EXEC command debug enables the display of several classes of network events on the console terminal. The privileged undebug command turns off the display of these classes. The EXEC command show debugging displays the state of each debugging option.
show debuggingSee the section "Redirecting System Error Messages" in the "Configuring the System" chapter of the manual for an explanation of how to configure message logging.
To list and briefly describe all the debug command options, enter the debug ? command at the privileged-level EXEC prompt.
debug ?This section provides an overview of how to use the debugging commands. See the interface and protocol-specific chapters of this manual for the debug command descriptions.
To turn on all system diagnostics, enter this command at the EXEC prompt:
debug allIts converse, the undebug all command, turns off all diagnostic output.
Timestamping enhances real-time debugging by providing the relative timing of logged events. This information is especially useful when you send debugging output to Cisco for assistance.
To configure the system for timestamping, use the global command:
[no] service timestampsWhen debugging is enabled, the resulting messages are preceded by a timestamp when they are sent to monitor terminals. The timestamp is the format HHHH:MM:SS and indicates the time since the router was last rebooted.
This example shows the command to enter configuration mode and the configuration command that implements the timestamping of debugging events.
gw#configureConfiguring from terminal, memory, or network [terminal]? Enter configuration commands, one per line. Edit with DELETE, CTRL/W, and CTRL/U; end with CTRL/Zservice timestamps
In this example, debugging modem events is activated, events are logged, and timestamping occurs, indicating the relative time the event is logged based on the time since the router was last rebooted. The TTY4 asserting DTR event occurred 3 minutes and 48 seconds after the router was last rebooted
gw#debug modemRS-232 modem signal debugging is on cs# cs 4004 Trying RUBBLE.CISCO.COM (131.108.61.34, 4004)....Open TTY4: asserting DTR [Connection to cs closed by foreign host] cs# TTY4: timed out waiting for CTS TTY4: dropping DTR, hanging up cs#configureConfiguring from terminal, memory, or network [terminal]? Enter configuration commands, one per line. Edit with DELETE, CTRL/W, and CTRL/U; end with CTRL/Zservice timestamps%SYS-5-CONFIG_I: Configured from console by console () cs#cs 4004Trying RUBBLE.CISCO.COM (131.108.61.34, 4004)...Open 0:03:48: TTY4 asserting DTR [Connection to RUBBLE closed by foreign host] cs#
In the following example, the ARP events occurred 52 minutes and 51 seconds after reload.
gw#debug arpARP packet debugging is on IP ARP: sent req src 131.108.61.37 0000.0c01.f0fe, dst 131.108.19.40 0000.0000.0000 IP ARP: rcvd rep src 131.108.19.40 0000.0c01.0e3b, dst 131.108.61.37 ARP: (merge) Creating entry for IP addr: 131.108.19.40, hw: 0000.0c01.0e3bcs#configureEnter configuration commands, one per line. Edit with DELETE, CTRL/W, and CTRL/U; end with CTRL/Zservice timestamp^Zcs# %SYS-5-CONFIG_I: Configured from console by console () 0:52:51: IP ARP: sent req src 131.108.61.37 0000.0c01.f0fe, dst 131.108.19.33 0000.0000.0000 0:52:51: IP ARP: rcvd rep src 131.108.19.33 0000.0c01.0e3b, dst 131.108.61.37 0:52:51: ARP: (merge) Creating entry for IP addr: 131.108.19.33, hw: 0000.0c01.0e3b
As an aid to diagnosing basic network connectivity, many network protocols support the packet internet groper (ping) program, which sends an echo request packet to an address, then awaits a reply. Results from this echo protocol can help in evaluating the path-to-host reliability, delays over the path, and whether the host can be reached or is functioning.
To implement this program, use the privileged EXEC command ping. When the ping command is entered, the system issues a prompt for one of the following protocol keywords--appletalk, clns, ip, novell, pup, or xns.
The default protocol is IP. After determining the protocol type, the ping command prompts for an address or host name, repeat count (default is 5), datagram size (default is 100 bytes), time-out interval (default is 2 seconds), and extended commands (default is none). The precise dialog varies from protocol to protocol.
If a host name or address is typed on the same line as the EXEC ping command, the default action is taken as appropriate for the protocol type of that name or address.
The ping command uses the exclamation point (!) and period (.) in its display. 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. The output concludes with the success rate and minimum, average, and maximum round-trip times.
To abort a ping session, type the escape sequence (by default, Ctrl-^ X, which is done by simultaneously pressing the Ctrl, shift, and 6 keys, letting go, then pressing the X key).
Sample displays and tips for using these protocols are included in the chapters describing the protocols supported by the Cisco ping command.
The trace command is a useful debugging command that allows the network administrator to discover the routes that packets actually will take when traveling to their destinations. The trace command supports ip, clns, and vines route tracing.
trace [destination]To invoke a simple trace test, enter the destination address or host name on the command line. The default parameters for the appropriate protocol are assumed, and the tracing action begins.
To use nondefault parameters and invoke an extended trace test, enter the command without a destination argument. You will be stepped through a dialog to select the desired parameters.
Typing the escape sequence (by default, Ctrl-^ X, which is done by simultaneously pressing the Ctrl, shift, and 6 keys, letting go, then pressing the X key) terminates a trace command. See the "Routing IP," "Switching ISO CLSN," and "Routing VINES" chapters in this chapter for more information about using this command.
This section describes the privileged write commands used to manage the system configuration information.
To erase the configuration information, use the following EXEC command. This command erases the configuration information in the nonvolatile memory. This command does not affect the configuration in use.
write eraseTo copy the configuration to memory, use the following EXEC command. This command copies the current configuration information to the nonvolatile memory.
write memoryTo copy the configuration to the network, use the following EXEC command. This command sends a copy of the current configuration information to a server host. You are prompted for a destination host and a file name.
write networkTo write configuration on the terminal, use the following EXEC command. This command displays the current configuration information on the terminal.
write terminalIncluded as part of the EXEC command set are commands that allow testing of system interfaces and memory.
The following EXEC command is used to test the system interfaces:
test interfacesThe EXEC test interfaces command is intended for the factory checkout of network interfaces. It is not intended for diagnosing problems with an operational router. The test interfaces output does not report correct results if the router is attached to a "live" network. For each network interface that has an IP address that can be tested in loopback (MCI and cBus Ethernet and all serial interfaces), the test interface command sends a series of ICMP echoes. Error counters are examined to determine the operational status of the interface.
The following EXEC command is used to test system memory:
test memoryThe EXEC command test memory performs a test of Multibus memory, including the nonvolatile memory.
 | Caution The memory test overwrites memory. If you use the test memory command, you will need to rewrite nonvolatile memory. For example, if you test Multibus memory, which is the memory used by the CSC-R 4-Mbps Token Ring interfaces, you will need to reload the system before the network interfaces will operate properly. The test memory command is intended primarily for use by Cisco personnel. |
The test sbe EXEC command is used to test the CSC-R16 16-Mbps Token Ring cards. The command syntax is as follows:
test sbeThis test runs software diagnostics on 16-Mbps Token Ring interface cards. It can be useful when analyzing hardware failures and suspected hardware failures. The command is not designed to be used on a system while the system is in use. This test should be used only at the direction of your Cisco technical support representative.
This section lists all the EXEC system management and user commands in alphabetical order.
debug ?
Lists and briefly describes all the debug command options.
[un]debug all
Enables all diagnostic output. Its converse, the undebug all command, turns off all diagnostic output.
ping
Provides a diagnostic tool for testing connectivity. Results help evaluate path-to-host reliability, delays over the path, and whether the host is functioning.
Enhances real-time debugging by providing the relative timing of logged events. This information is especially useful when you send debugging output to Cisco technical support personnel for assistance.
show ?
Lists all the show command options. Two lists can be displayed: one at the user-level prompt and one at the enabled, privileged-level prompt.
show buffers [interface]
Displays statistics for the buffer pools on the network server. The network server has one pool of queuing elements and five pools of packet buffers of different sizes. For each pool, the network server keeps counts of the number of buffers outstanding, the number of buffers in the free list, and the maximum number of buffers allowed in the free list. With the optional argument interface, this command searches all buffers that have been associated with the interface for longer than one minute.
show configuration
Displays the contents of the nonvolatile memory, if present and valid. The nonvolatile memory stores the configuration information in the network server in text form as configuration commands.
show debugging
Displays the current settings of the debug command options.
show environment
Displays temperature and voltage information on the AGS+ console.
show environment last
Displays the last measured value from each of six testpoints if a system shutdown occurs due to detection of fatal environmental margins. The CSC-ENVM logs to internal nonvolatile memory. Only one set of measurements can be stored at any one time.
show flash
Displays the total amount of Flash memory present on the Flash card, the type of card connected to the Flash card, any files that may currently exist in Flash memory, and the amounts of Flash memory used and remaining.
show flash all
Displays all the output of show flash; also shows information about each Flash memory device.
show logging
Displays the state of syslog error and event logging, including host addresses and whether console logging is enabled. This command also displays SNMP configuration parameters and protocol activity.
show memory
Displays memory free pool statistics. These statistics include summary information about the activities of the system memory allocator and a block-by-block listing of memory use.
show processes
Displays information about all active processes.
show processes memory
Displays information about memory utilization.
show protocols
Displays the global and interface-specific status of any configured Level 3 protocol.
show stacks
Monitors the stack utilization of processes and interrupt routines. Its display includes the reason for the last system reboot. If the system was reloaded because of a system failure, a saved system stack trace is displayed. This information can be useful to support staff for analyzing crashes in the field.
test interfaces
Intended for the factory checkout of network interfaces. It is not intended for diagnosing problems with an operational router.
test memory
Performs a destructive test of Multibus memory, including the nonvolatile memory.
test sbe
Tests the CSC-R16 16-Mbps Token Ring card.
trace [destination]
Allows the network administrator to discover the routes that packets actually will take when traveling to their destinations. The trace command supports IP, CLNS, and VINES route tracing. Typing the escape sequence terminates trace.
write erase
Erases the configuration information in the nonvolatile memory. This command does not affect the configuration in use.
write memory
Copies the current configuration information to the nonvolatile memory.
write network
Sends a copy of the current configuration information to a server host. You are prompted for a destination host and a file name.
write terminal
Displays the current configuration information.
|
|