Table Of Contents
show context
show controllers (GRP image)
show controllers (line card image)
show controllers logging
show controllers tech-support
show debugging
show derived-config
show disk0:
show disk1:
show environment
show event manager directory user
show event manager environment
show event manager history events
show event manager history traps
show event manager policy available
show event manager policy pending
show event manager policy registered
show event manager session cli username
show file
show file descriptors
show file information
show file systems
show flh-log
show gsr
show gt64010 (7200)
show history
show idb
show inventory
show ip director default
show ip director dfp
show ip drp boomerang
show ip http client connection
show ip http client history
show ip http client session-module
show ip http server
show ip sla monitor apm cache
show ip sla monitor apm information
show ip sla monitor apm operation
show ip sla monitor apm results
show ip sla monitor application
show ip sla monitor authentication
show ip sla monitor collection-statistics
show ip sla monitor configuration
show ip sla monitor distributions-statistics
show ip sla monitor enhanced-history collection-statistics
show ip sla monitor enhanced-history distribution-statistics
show ip sla monitor group schedule
show ip sla monitor history
show ip sla monitor reaction-configuration
show ip sla monitor reaction-trigger
show ip sla monitor responder
show ip sla monitor statistics
show ip sla monitor totals-statistics
show context
To display information stored in NVRAM when an unexpected system reload (system exception) occurs, use the show context command in user EXEC or privileged EXEC mode.
show context [summary | 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 router and from 0 to 7 for the Cisco 12008. The 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 a hex record dump in addition to one of the options listed.
|
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
10.3
|
This command was introduced.
|
11.2 GS
|
The slot slot-number [crash-index] [all] [debug] syntax was added for Cisco 12000 series routers.
|
Usage Guidelines
The display from the show context command includes the following information:
•
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 command is primarily for use by Cisco technical support representatives for analyzing unexpected system reloads.
Output for this command will vary by platform. Context information is specific to processors and architectures. For example, context information for the Cisco 2600 series router differs from that for other router types because the Cisco 2600 runs with an M860 processor.
Examples
The following is sample output from the show context command following a system failure:
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 for each slot (line card).
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
The following is sample output from the show context command following an unexpected system reload on a Cisco 2600 series router.
S/W Version: Cisco IOS Software
Cisco IOS (tm) c2600 Software (c2600-JS-M), Released Version 11.3(19980115:184921]
Copyright (c) 1986-2003 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 76 describes the significant fields shown in the display.
Table 76 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 controllers (GRP image)
To display information that is specific to the hardware, use the show controllers command in privileged EXEC mode.
show controllers [atm slot-number | clock | csar [register] | csc-fpga | dp83800 | fab-clk | fia
[register] | pos [slot-number] [details] | queues [slot-number] | sca | xbar]
Syntax Description
atm slot-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 router and from 0 to 7 for the Cisco 12008 router.
|
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. Two switch fabric clocks arrive 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 displays the register information.
|
pos [slot-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 router and from 0 to 7 for the Cisco 12008 router.
|
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 router and from 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 introduced to support the Cisco 12000 series routers.
|
Usage Guidelines
This information provided by this command is intended for use only by technical support representatives in analyzing system failures in the field.
Examples
The following is sample output from the show controllers pos command for a Cisco 12012:
Router# show controllers pos 7/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 command in privileged EXEC mode to connect to the line card and then use the show controllers command in privileged EXEC mode or the execute-on command in privileged EXEC mode.
show controllers atm [[port-number] [all | sar | summary]]
show controllers fia [register]
show controllers {frfab | tofab} {bma {microcode | ms-inst | register} | qelem
start-queue-element [end-queue-element] | qnum start-queue-number [end-queue-number] |
queues | statistics}
show controllers io
show controllers l3
show controllers pos {framers | queues | registers | rxsram port-number queue-start-address
[queue-length] | txsram port-number queue-start-address [queue-length]}
Syntax Description
atm
|
Displays the ATM controller information.
|
port-number
|
(Optional) Displays request for the physical interface on the ATM card. The range of choices is from 0 to 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" (transmit) fabric information.
|
tofab
|
(Optional) Displays the "to" (receive) fabric 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 SQE information for the microcode bundled in the line card and currently running version.
|
mis-inst
|
Displays 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 from 0 to 65535.
|
end-queue-element
|
(Optional) Specifies the end queue element number from 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 (from 0 to 127).
|
end-queue-number
|
(Optional) Specifies the end free queue number (from 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 from 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
This information displayed by this command is of use only to technical support representatives in analyzing unexpected system failures in the field. It is documented here in case you need to provide the displayed statistics to an technical support engineer.
Examples
Because you are executing this command on the line card, you must use the execute-on command to use the show command, or you must connect to the card using the attach command. All examples in this section use the execute-on command
The following is partial sample output from the show controllers atm command:
Router# execute-on slot 4 show controllers atm 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 command in privileged EXEC mode.
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.
When enabled, "trap logging" allows messages to be sent to a remote host (a syslog server).
Examples
The following is sample output from the show controllers logging command:
Router# show controllers vip 1 logging
show logging from Slot 1:
Syslog logging:enabled (0 messages dropped, 1 messages rate-limited, 0 flushes, 0
overruns)
Console logging: disabled
Monitor logging: level debugging, 0 messages logged
Buffer logging: level debugging, 24 messages logged
Trap logging: level informational, 266 messages logged.
Logging to 209.165.202.129
Exception Logging size: 4096 bytes
Count and timestamp logging messages:disabled
smallest_local_pool_entries = 256, global particles = 5149
highest_local_visible_bandwidth = 155000
00:00:05:%SYS-5-RESTART:System restarted --
Table 77 describes the significant fields shown in the display.
Table 77 show controllers logging Field Descriptions
Field
|
Description
|
Syslog logging
|
Shows general state of system logging (enabled or disabled), and status of logged messages (number of messages dropped, rate-limited, or flushed).
|
Console logging
|
Logging to the console port. Shows "disabled" or, if enabled, the severity level limit and number of messages logged.
Enabled using the logging console command.
|
Monitor logging
|
Logging to the monitor (all TTY lines). Shows "disabled" or, if enabled, the severity level limit and number of messages logged.
Enabled using the logging monitor command.
|
Buffer logging
|
Logging to the standard syslog buffer. Shows "disabled" or, if enabled, the severity level limit and number of messages logged.
Enabled using the logging buffered command.
|
Trap logging
|
Logging to a remote host (syslog host). Shows "disabled" or, if enabled, the severity level limit and number of messages logged.
(The word "trap" means a trigger in the system software for sending error messages to a remote host.)
Enabled using the logging host command. The severity level limit is set using the logging trap command.
|
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 command in privileged EXEC mode.
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:
•
more system:running-config
•
show buffers
•
show controllers
•
show interfaces
•
show processes cpu
•
show processes memory
•
show stacks
•
show version
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
|
Uses 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 command in privileged EXEC mode.
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.
|
12.3(7)T
|
The output of this command was enhanced to show TCP Explicit Congestion Notification (ECN) configuration.
|
Examples
The following is sample output from the show debugging command. In this example, the remote host is not configured or connected.
TCP Packet debugging is on
Router# telnet 10.1.25.234
00:02:48: 10.1.25.31:11001 <---> 10.1.25.234:23 out ECN-setup SYN
00:02:48: tcp0: O CLOSED 10.1.25.234:11001 10.1.25.31:23 seq 1922220018
OPTS 4 ECE CWR SYN WIN 4128
00:02:50: 10.1.25.31:11001 <---> 10.1.25.234:23 congestion window changes
00:02:50: cwnd from 1460 to 1460, ssthresh from 65535 to 2920
00:02:50: tcp0: R SYNSENT 10.1.25.234:11001 10.1.25.31:23 seq 1922220018
OPTS 4 ECE CWR SYN WIN 4128
00:02:54: 10.1.25.31:11001 <---> 10.1.25.234:23 congestion window changes
00:02:54: cwnd from 1460 to 1460, ssthresh from 2920 to 2920
00:02:54: tcp0: R SYNSENT 10.1.25.234:11001 10.1.25.31:23 seq 1922220018
OPTS 4 ECE CWR SYN WIN 4128
00:03:02: 10.1.25.31:11001 <---> 10.1.25.234:23 congestion window changes
00:03:02: cwnd from 1460 to 1460, ssthresh from 2920 to 2920
00:03:02: tcp0: R SYNSENT 10.1.25.234:11001 10.1.25.31:23 seq 1922220018
OPTS 4 ECE CWR SYN WIN 4128
00:03:18: 10.1.25.31:11001 <---> 10.1.25.234:23 SYN with ECN disabled
00:03:18: 10.1.25.31:11001 <---> 10.1.25.234:23 congestion window changes
00:03:18: cwnd from 1460 to 1460, ssthresh from 2920 to 2920
00:03:18: tcp0: O SYNSENT 10.1.25.234:11001 10.1.25.31:23 seq 1922220018
00:03:20: 10.1.25.31:11001 <---> 10.1.25.234:23 congestion window changes
00:03:20: cwnd from 1460 to 1460, ssthresh from 2920 to 2920
00:03:20: tcp0: R SYNSENT 10.1.25.234:11001 10.1.25.31:23 seq 1922220018
00:03:24: 10.1.25.31:11001 <---> 10.1.25.234:23 congestion window changes
00:03:24: cwnd from 1460 to 1460, ssthresh from 2920 to 2920
00:03:24: tcp0: R SYNSENT 10.1.25.234:11001 10.1.25.31:23 seq 1922220018
00:03:32: 10.1.25.31:11001 <---> 10.1.25.234:23 congestion window changes
00:03:32: cwnd from 1460 to 1460, ssthresh from 2920 to 2920
00:03:32: tcp0: R SYNSENT 10.1.25.234:11001 10.1.25.31:23 seq 1922220018
!Connection timed out; remote host not responding
Table 78 describes the significant fields in the output.
Table 78 show debugging Field Descriptions
Field
|
Description
|
OPTS 4
|
Bytes of TCP expressed as a number. In this case, the bytes are 4.
|
ECE
|
Echo congestion experience.
|
CWR
|
Congestion window reduced.
|
SYN
|
Synchronize connections—Request to synchronize sequence numbers, used when a TCP connection is being opened.
|
WIN 4128
|
Advertised window size, in bytes. In this case, the bytes are 4128.
|
cwnd
|
Congestion window (cwnd)—Indicates that the window size has changed.
|
ssthresh
|
Slow-start threshold (ssthresh)—Variable used by TCP to determine whether or not to use slow-start or congestion avoidance.
|
show derived-config
To display the composite results of all the configuration commands that apply to an interface, including commands that come from sources such as static templates, dynamic templates, dialer interfaces, and authentication, authorization, and accounting (AAA) per-user attributes, use the show derived-config command in privileged EXEC mode.
show derived-config [interface type number]
Syntax Description
interface type number
|
(Optional) Displays the derived configuration for a specific interface. If you use the interface keyword, you must specify the interface type and the interface number (for example, interface ethernet 0).
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.1
|
This command was introduced.
|
Usage Guidelines
Configuration commands can be applied to an interface from sources such as static templates, dynamic templates bound by resource pooling, dialer interfaces, AAA per-user attributes and the configuration of the physical interface. The show derived-config command displays all the commands that apply to an interface.
The output for the show derived-config command is nearly identical to that of the show running-config command. It differs when the configuration for an interface is derived from a template, a dialer interface, or some per-user configuration. In those cases, the commands derived from the template, dialer interface, and so on, will be displayed for the affected interface.
If the same command is configured differently in two different sources that apply to the same interface, the command coming from the source that has the highest precedence will appear in the display.
Examples
The following examples show sample output for the show running-config and show derived-config commands for serial interface 0:23 and dialer interface 0. The output of the show running-config and show derived-config commands is the same for dialer interface 0 because none of the commands that apply to that interface are derived from any sources other than the configuration of the dialer interface. The output for the show running-config and show derived-config commands for serial interface 0:23 differs because some of the commands that apply to serial interface 0:23 come from dialer interface 0.
Router# show running-config interface Serial0:23
Building configuration...
Current configuration :296 bytes
description PRI to ADTRAN (#4444150)
isdn switch-type primary-dms100
isdn incoming-voice modem
isdn calling-number 4444150
peer default ip address pool old_pool
Router# show running-config interface Dialer0
Building configuration...
Current configuration :257 bytes
peer default ip address pool new_pool
ppp authentication pap chap callin
Router# show derived-config interface Serial0:23
Building configuration...
Derived configuration :332 bytes
description PRI to ADTRAN (#4444150)
isdn switch-type primary-dms100
isdn incoming-voice modem
isdn calling-number 4444150
peer default ip address pool new_pool
ppp authentication pap chap callin
Router# show derived-config interface Dialer0
Building configuration...
Derived configuration :257 bytes
peer default ip address pool new_pool
ppp authentication pap chap callin
Related Commands
Command
|
Description
|
show running-config
|
Displays the contents of the currently running configuration file or the configuration for a specific interface.
|
show disk0:
To display flash or file system information for a disk located in slot 0, use the show disk command in user EXEC or privileged EXEC mode.
show disk0: [all | filesys]
Syntax Description
all
|
(Optional) The all keyword displays complete information about flash memory, including information about the individual devices in flash memory and the names and sizes of all system image files stored in flash memory, including those that are invalid.
|
filesys
|
(Optional) Displays the device information block, the status information, and the usage information.
|
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
11.3AA
|
This command was introduced.
|
12.2
|
This command was incorporated into Cisco IOS Release 12.2.
|
12.3(7)T
|
This command was enhanced to display information about the ATA ROM monitor library (monlib) file.
|
12.2(25)S
|
This command was integrated into Cisco IOS Release 12.2(25)S.
|
Usage Guidelines
The show disk0: command is supported only on platforms that have a disk file system located in slot 0. Use the show disk0: command to display details about the files in a particular ATA PCMCIA flash disk memory card.
For more information regarding file systems and flash cards, access the PCMCIA Filesystem Compatibility Matrix and Filesystem Information document at the following URL:
http://www.cisco.com/en/US/partner/products/hw/routers/ps341/products_tech_note09186a00800a7515.shtml
Note
The name of the ATA monlib file may contain a platform name that does not match the platform that you are using. Different platforms may have a similar name or the same name for their ATA monlib file.
Examples
The following examples show displays of information about the flash disks or file system information for a disk. The output is self-explanatory.
-#- --length-- -----date/time------ path
1 29505176 Feb 27 2006 17:56:52 +00:00 c7200-jk9o3s-mz.124-6.T
2 32768 Feb 24 2006 13:30:30 +00:00 file1.log
34738176 bytes available (29540352 bytes used)
-#- --length-- -----date/time------ path
1 29505176 Feb 27 2006 17:56:52 +00:00 c7200-jk9o3s-mz.124-6.T
2 32768 Feb 24 2006 13:30:30 +00:00 file1.log
34738176 bytes available (29540352 bytes used)
******** ATA Flash Card Geometry/Format Info ********
Number of Data Sectors 125812
Image Monlib size = 73048
c7200# show disk0: filesys
******** ATA Flash Card Geometry/Format Info ********
Number of Data Sectors 125812
Image Monlib size = 73048
Related Commands
Command
|
Description
|
dir disk0:
|
Displays a directory listing of files on an ATA PCMCIA flash disk card located in slot 0.
|
dir disk1:
|
Displays a directory listing of files on an ATA PCMCIA flash disk card located in slot 1.
|
show disk1:
|
Displays flash or file system information for a disk located in slot 1.
|
show disk1:
To display flash or file system information for a disk located in slot 1, use the show disk1: command in user EXEC or privileged EXEC mode.
show disk1: [all | filesys]
Syntax Description
all
|
(Optional) The all keyword displays complete information about flash memory, including information about the individual devices in flash memory and the names and sizes of all system image files stored in flash memory, including those that are invalid.
|
filesys
|
(Optional) Displays the device information block, the status information, and the usage information.
|
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
11.3AA
|
This command was introduced.
|
12.2
|
This command was incorporated into Cisco IOS Release 12.2.
|
12.3(7)T
|
This command was enhanced to display information about the ATA ROM monitor library (monlib) file.
|
12.2(25)S
|
This command was integrated into Cisco IOS Release 12.2(25)S.
|
Usage Guidelines
The show disk1: command is supported only on platforms that have a disk file system. Use the show disk01: command to display details about the files in a particular ATA PCMCIA flash disk memory card located in slot 1.
For more information regarding file systems and flash cards, access the PCMCIA Filesystem Compatibility Matrix and Filesystem Information document at the following URL:
http://www.cisco.com/en/US/partner/products/hw/routers/ps341/products_tech_note09186a00800a7515.shtml
Note
The name of the ATA monlib file may contain a platform name that does not match the platform that you are using. Different platforms may have a similar name or the same name for their ATA monlib file.
Examples
The following examples show displays of information about the flash disks or file system information for a disk. The output is self-explanatory.
-#- --length-- -----date/time------ path
1 29505176 Feb 27 2006 17:56:52 +00:00 c7200-jk9o3s-mz.124-6.T
2 32768 Feb 24 2006 13:30:30 +00:00 file1.log
34738176 bytes available (29540352 bytes used)
-#- --length-- -----date/time------ path
1 29505176 Feb 27 2006 17:56:52 +00:00 c7200-jk9o3s-mz.124-6.T
2 32768 Feb 24 2006 13:30:30 +00:00 file1.log
34738176 bytes available (29540352 bytes used)
******** ATA Flash Card Geometry/Format Info ********
Number of Data Sectors 125812
Image Monlib size = 73048
c7200# show disk1: filesys
******** ATA Flash Card Geometry/Format Info ********
Number of Data Sectors 125812
Image Monlib size = 73048
Related Commands
Command
|
Description
|
dir disk0:
|
Displays a directory listing of files on an ATA PCMCIA flash disk card located in slot 0.
|
dir disk1:
|
Displays a directory listing of files on an ATA PCMCIA flash disk card located in slot 1.
|
show disk0:
|
Displays flash or file system information for a disk located in slot 0.
|
show environment
To display temperature, voltage, and blower information on the Cisco 7000 series, Cisco 7200 series, Cisco 7500 series routers, Cisco AS5300 series access servers, and Cisco 12000 series Gigabit Switch Routers (GSRs), use the show environment command in privileged EXEC mode.
show environment [alarms | all | fans | hardware | last | leds | power-supply | table | temperature
| voltages]
Syntax Description
alarms
|
(Optional) Displays the alarm contact information.
|
all
|
(Optional) Displays a detailed listing of all environmental monitor parameters (for example, the power supplies, temperature readings, voltage readings, and blower speeds). This is the default.
|
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. If applicable, displays the status of the redundant power supply.
|
table
|
(Optional) Displays the temperature, voltage, and blower ranges and thresholds.
|
temperature
|
(Optional) Displays temperature information.
|
voltages
|
(Optional) Displays voltage information.
|
Defaults
If no options are specified, the default is all.
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 GSRs.
|
11.3(6)AA
|
This command was expanded to monitor the RPS and board temperature for the Cisco AS5300 platform, Cisco 3600 Series routers, Cisco 7200 series routers, and the Cisco 12000 series routers.
|
Usage Guidelines
The availability of keywords will depend on your system.
Once a minute a routine is run that gets environmental measurements from sensors and stores the output into a buffer. This buffer is displayed on the console when the show environment command is entered.
If a measurement exceeds desired margins, but has not exceeded fatal margins, a warning message is printed to the system console. The system software queries the sensors for measurements once a minute, but warnings for a given test point are printed at most once every hour for sensor readings in the warning range and once every 5 minutes for sensor readings in the critical range. If a measurement is out of line within these time segments, an automatic warning message appears on the console. As noted, you can query the environmental status with the show environment command at any time to determine whether a measurement is at the warning or critical tolerance.
If a shutdown occurs because of detection of fatal environmental margins, the last measured value from each sensor is stored in internal nonvolatile memory.
For environmental specifications, refer to the hardware installation and configuration publication for your individual chassis.
If the Cisco 12000 series exceeds environmental conditions, a message similar to the following is displayed on the console:
%GSR_ENV-2-WARNING: Slot 3 Hot Sensor Temperature exceeds 40 deg C;
Note
Blower temperatures that exceed environmental conditions do not generate a warning message.
You can also enable Simple Network Management Protocol (SNMP) notifications (traps or informs) to alert a network management system (NMS) when environmental thresholds are reached using the snmp-server enable traps envmon and snmp-server host global configuration commands.
Whenever Cisco IOS software detects a failure or recovery event from the DRPS unit, it sends an SNMP trap to the configured SNMP server. Unlike console messages, only one SNMP trap is sent when the failure event is first detected. Another trap is sent when the recovery is detected.
Cisco AS5300 DRPS software reuses the MIB attributes and traps defined in CISCO-ENVMON-MIB and CISCO-ACCESS-ENVMON-MIB. CISCO-ENVMON-MIB is supported by all Cisco routers with RPS units, and CISCO-ACCESS-ENVMON-MIB is supported by the Cisco 3600 series routers.
A power supply trap defined in CISCO-ENVMON-MIB is sent when a failure is detected and when a failure recovery occurs for the following events: input voltage fail, DC output voltage fail, thermal fail, and multiple failure events.
A fan failure trap defined in CISCO-ENVMON-MIB is sent when a fan failure or recovery event is detected by Cisco IOS software.
A temperature trap defined in CISCO-ACCESS-ENVMON-MIB is sent when a board overtemperature condition is detected by Cisco IOS software.
CISCO-ACCESS-ENVMON-MIB also defines an overvoltage trap. A similar trap is defined in CISCO-ENVMON-MIB, but it requires the ciscoEnvMonVoltageStatusValue in varbinds. This value indicates the current value of the voltage in the RPS. With Cisco AS5300 RPS units, the current voltage value is not sent to the motherboard.
CISCO-ENVMON-MIB is extended to add a new enumerated value, internalRedundant(5), for MIB attribute ciscoEnvMonSupplySource. This is used to identify a RPS unit.
Examples
In the following example, the typical show environment display is shown when no warning conditions are in the system for the Cisco 7000 series and Cisco 7200 series routers. This information may vary slightly depending on the platform you are using. The date and time of the query are displayed, along with the data refresh information and a message indicating that there are no warning conditions.
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 79 describes the significant fields shown in the display.
Table 79 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.
|
Cisco 7000 Series Routers
The following are examples of messages that display on the system console when a measurement has exceeded an acceptable margin:
ENVIRONMENTAL WARNING: Air flow appears marginal.
ENVIRONMENTAL WARNING: Internal temperature measured 41.3(C)
ENVIRONMENTAL WARNING: +5 volt testpoint measured 5.310(V)
The system displays the following message if voltage or temperature exceed maximum margins:
SHUTDOWN: air flow 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 80 describes the significant fields shown in the display.
Table 80 show environment all Field Descriptions for the Cisco 7000 Series Routers
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 81 describes the significant fields shown in the display.
Table 81 show environment last Field Descriptions for the Cisco 7000 Series Routers
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 router, indicates the status of the two 700W power supplies.
For the Cisco 7010 router, indicates the status of the single 600W power supply.
|
The following example provides sample output for the current environmental status in tables that list voltage and temperature parameters. There are three warning messages: one each about the lower power supply, the airflow temperature, and the inlet temperature. In this example, voltage parameters are shown to be in the normal range, airflow temperature is at a critical level, and inlet temperature is at the warning level.
Router> show environment 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 82 describes the significant fields shown in the display.
Table 82 show environment Field Descriptions for the Cisco 7000 Series Router
Field
|
Description
|
SENSE (Voltage Parameters)
|
Voltage specification for a 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.
|
Cisco 7200 Series Routers
The system displays the following message if the voltage or temperature enters the "Warning" range:
%ENVM-4-ENVWARN: Chassis outlet 3 measured at 55C/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 83 describes the significant fields shown in the display.
Table 83 show environment all Field Descriptions for the Cisco 7200 Series Router
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 84 describes the significant fields shown in the display.
Table 84 show environment last Field Descriptions for the Cisco 7200 Series Router
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 85 describes the significant fields shown in the display.
Table 85 show environment table Field Descriptions for the Cisco 7200 Series Router
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 Router
The sample output for the Cisco 7500 series routers may vary depending on the specific model (for example, the Cisco 7513 router). The following is sample output from the show environment all command on the Cisco 7500 series router:
7500# show environment 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 86 describes the significant fields shown in the display.
Table 86 show environment all Field Descriptions for the Cisco 7500 Series Routers
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:
|
Lists any fault conditions that exist (such as power supply failure, fan failure, and temperature too high).
|
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:
|
Compares temperature sensor 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-Route/Switch Processor (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.
|
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 87 describes the significant fields shown in the display.
Table 87 show environment last Field Descriptions for the Cisco 7500 Series Router
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 88 describes the significant fields shown in the display.
Table 88 show environment table Field Descriptions for the Cisco 7500 Series Router
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 AS5300 Series Access Servers
In the following example, keywords and options are limited according to the physical characteristics of the system is shown:
as5300# show environment ?
all All environmental monitor parameters
last Last environmental monitor parameters
table Temperature and voltage ranges
as5300# show environment table
%This option not available on this platform
Cisco 12000 Series GSR
The following examples are for the Cisco 12000 series GSRs.
The following is sample output from the show environment command for a Cisco 12012 router. Slots 0 through 11 are the line cards, slots 16 and 17 are the clock and scheduler cards, slots 18 through 20 are the switch fabric cards, slots 24 through 26 are the power supplies, and slots 28 and 29 are the blowers. An "NA" in the table means that no values were returned. In some cases it is because the equipment is not supported for that environmental parameter (for example, the power supply and blowers in slots 24, 26, 28, and 29 do not have a 3V power supply, so an NA is displayed).
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 89 describes the significant fields shown and lists the equipment supported by each environmental parameter. "NA" indicates that the reading could not be obtained, so the command should be again.
Table 89 show environment Field Descriptions for the Cisco 12000 Series Routers
Field
|
Description
|
Slot #
|
Slot number of the equipment. On the Cisco 12012 router, slots 0 through 11 are the line cards, slots 16 and 17 are the clock and scheduler cards, slots 18 through 20 are the switch fabric cards, slots 24 through 27 are the power supplies, and slots 28 and 29 are the blowers.
|
3V (mv)
|
Measures the 3v power supply on the card. The 3v power supply is on the line cards, GRP card, clock and scheduler cards, and switch fabric cards.
|
5V (mv)
|
Measures the 5v power supply on the card. The 5v power supply is on the line cards, GRP card, and power supplies.
|
MBUS 5V (mv)
|
Measures the 5v MBus on the card. The 5v 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 router. Slots 0 through 7 are the line cards, slots 16 and 17 are the clock scheduler cards (the clock scheduler cards control the fans), slots 18 through 20 are the switch fabric cards, and slots 24 and 26 are the power supplies. The Cisco 12008 router does not support slots 25, 27, 28, and 29. An "NA" in the table means that no values were returned. In some cases it is because the equipment is not supported for that environmental parameter (for example, the power supplies in slots 24 and 26 do not have a hot sensor, so an NA is displayed).
Router# show environment 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 router. The show environment table command lists the warning, critical, and shutdown limits on your system and includes the GRP card and line cards (slots 0 to 15), clock and scheduler cards (slots 16 and 17), switch fabric cards (slots 18 to 20), and blowers.
Router# show environment 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 router. The show environment leds command lists the status of the MBus LEDs on the clock, scheduler, and the switch fabric cards.
Router# show environment leds
Related Commands
Command
|
Description
|
snmp-server enable traps envmon
|
Controls (enables or disables) environmental monitoring SNMP notifications.
|
snmp-server host
|
Specifies how SNMP notifications should be sent (as traps or informs), the version of SNMP to use, the security level of the notifications (for SNMPv3), and the recipient (host) of the notifications.
|
show event manager directory user
To display the directory to use for storing user library files or user-defined Embedded Event Manager (EEM) policies, use the show event manager directory user command in privileged EXEC mode.
show event manager directory user [library | policy]
Syntax Description
library
|
(Optional) User library files.
|
policy
|
(Optional) User-defined EEM policies.
|
Defaults
The directories for both user library and user policy files are displayed.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.3(14)T
|
This command was introduced.
|
Usage Guidelines
Use the event manager directory user command to specify the directory to use for storing user library or user policy files.
Examples
The following example shows the /usr/fm_policies folder on disk 0 as the directory to use for storing EEM user library files:
Router# show event manager directory user library
Related Commands
Command
|
Description
|
event manager directory user
|
Specifies a directory to use for storing user library files or user-defined EEM policies.
|
show event manager environment
To display the name and value of Embedded Event Manager (EEM) environment variables, use the show event manager environment command in privileged EXEC mode.
show event manager environment [all | variable-name]
Syntax Description
all
|
(Optional) Displays information for all environment variables. This is the default.
|
variable-name
|
(Optional) Displays information about the specified environment variable.
|
Defaults
If no argument or keyword is specified, information for all environment variables is displayed.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.2(25)S
|
This command was introduced.
|
12.3(14)T
|
This command was integrated into Cisco IOS Release 12.3(14)T.
|
Examples
The following is sample output from the show event manager environment command:
Router# show event manager environment
1 _cron_entry 0-59/1 0-23/1 * * 0-7
3 _syslog_pattern .*UPDOWN.*Ethernet1/0.*
4 _config_cmd1 interface Ethernet1/0
5 _config_cmd2 no shutdown
Table 90 describes the significant fields shown in the display.
Table 90 show event manager environment Field Descriptions
Field
|
Description
|
No.
|
The index number assigned to the EEM environment variable.
|
Name
|
The name given to the EEM environment variable when it was created.
|
Value
|
The text content defined for the EEM environment variable when it was created.
|
Related Commands
Command
|
Description
|
event manager environment
|
Sets an EEM environment variable.
|
show event manager history events
To display the Embedded Event Manager (EEM) events that have been triggered, use the show event manager history events command in privileged EXEC mode.
show event manager history events [detailed] [maximum number]
Syntax Description
detailed
|
(Optional) Displays detailed information about each EEM event.
|
maximum
|
(Optional) Specifies the maximum number of events to display.
• number—Number in the range from 1 to 50. The default is 50.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.2(25)S
|
This command was introduced.
|
12.3(14)T
|
This command was integrated into Cisco IOS Release 12.3(14)T.
|
Usage Guidelines
Use the show event manager history events command to track information about the EEM events that have been triggered.
Examples
The following is sample output from the show event manager history events command showing that two types of events, SNMP and application, have been triggered.
Router# show event manager history events
No. Time of Event Event Type Name
1 Fri Aug13 21:42:57 2004 snmp applet: SAAping1
2 Fri Aug13 22:20:29 2004 snmp applet: SAAping1
3 Wed Aug18 21:54:48 2004 snmp applet: SAAping1
4 Wed Aug18 22:06:38 2004 snmp applet: SAAping1
5 Wed Aug18 22:30:58 2004 snmp applet: SAAping1
6 Wed Aug18 22:34:58 2004 snmp applet: SAAping1
7 Wed Aug18 22:51:18 2004 snmp applet: SAAping1
8 Wed Aug18 22:51:18 2004 application applet: CustApp1
Table 91 describes the significant fields shown in the display.
Table 91 show event manager history events Field Descriptions
Field
|
Description
|
No.
|
Event number.
|
Time of Event
|
Date and time when the event was triggered.
|
Event Type
|
Type of event.
|
Name
|
Name of the policy that was triggered.
|
Related Commands
Command
|
Description
|
event manager history size
|
Modifies the size of the EEM history tables.
|
show event manager history traps
To display the Embedded Event Manager (EEM) Simple Network Management Protocol (SNMP) traps that have been sent, use the show event manager history traps command in privileged EXEC mode.
show event manager history traps {server | policy}
Syntax Description
server
|
Displays SNMP traps that were triggered from the EEM server.
|
policy
|
Displays SNMP traps that were triggered from within an EEM policy.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.2(25)S
|
This command was introduced.
|
12.3(14)T
|
This command was integrated into Cisco IOS Release 12.3(14)T.
|
Usage Guidelines
Use the show event manager history traps command to identify whether the SNMP traps were implemented from the EEM server or from an EEM policy.
Examples
The following is sample output from the show event manager history traps command:
Router# show event manager history traps policy
1 Wed Aug18 22:30:58 2004 policy EEM Policy Director
2 Wed Aug18 22:34:58 2004 policy EEM Policy Director
3 Wed Aug18 22:51:18 2004 policy EEM Policy Director
Table 92 describes the significant fields shown in the display.
Table 92 show event manager history traps Field Descriptions
Field
|
Description
|
No.
|
Trap number.
|
Time
|
Date and time when the SNMP trap was implemented.
|
Trap Type
|
Type of SNMP trap.
|
Name
|
Name of the SNMP trap that was implemented.
|
Related Commands
Command
|
Description
|
event manager history size
|
Modifies the size of the EEM history tables.
|
show event manager policy available
To display Embedded Event Manager (EEM) policies that are available to be registered, use the show event manager policy available command in privileged EXEC mode.
show event manager policy available [system | user]
Syntax Description
system
|
(Optional) Displays all available system policies.
|
user
|
(Optional) Displays all available user policies.
|
Defaults
If no keyword is specified, information for all available system and user policies is displayed.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.2(25)S
|
This command was introduced.
|
12.3(14)T
|
The user keyword was added, and this command was integrated into Cisco IOS Release 12.3(14)T.
|
Usage Guidelines
This command is useful if you forget the exact name of a policy required for the event manager policy command.
Examples
The following is sample output from the show event manager policy available command:
Router# show event manager policy available
No. Type Time Created Name
1 system Tue Sep 12 09:41:32 2002 sl_pattern_ios.tcl
2 system Tue Sep 12 09:41:32 2002 tm_countdown_ios.tcl
Table 93 describes the significant fields shown in the display.
Table 93 show event manager policy available Field Descriptions
Field
|
Description
|
No.
|
Index number automatically assigned to the policy.
|
Type
|
Indicates whether the policy is a system policy.
|
Time Created
|
Time stamp indicating the date and time when the policy file was created.
|
Name
|
Name of the EEM policy file.
|
Related Commands
Command
|
Description
|
event manager policy
|
Registers an EEM policy with the EEM.
|
show event manager policy pending
To display Embedded Event Manager (EEM) policies that are pending execution, use the show event manager policy pending command in privileged EXEC mode.
show event manager policy pending
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.2(25)S
|
This command was introduced.
|
12.3(14)T
|
This command was integrated into Cisco IOS Release 12.3(14)T.
|
Usage Guidelines
Pending policies are policies that are pending execution in the EEM server execution queue. When an event is triggered, the policy that is registered to handle the event is queued for execution in the EEM server. Use the show event manager policy pending command to display the policies in this queue.
Examples
The following is sample output from the show event manager policy pending command:
Router# show event manager policy pending
No. Time of Event Event Type Name
1 Sat Oct11 05:02:41 2003 timer watchdog script:fd_timer_watchdog.tcl
2 Sat Oct11 05:02:41 2003 timer watchdog script:fd_timer_watchdog2.tcl
Table 94 describes the significant fields shown in the display.
Table 94 show event manager policy pending Field Descriptions
Field
|
Description
|
No.
|
Index number automatically assigned to the policy.
|
Time of Event
|
Date and time when the policy was queued for execution in the EEM server.
|
Event Type
|
Type of event.
|
Name
|
Name of the EEM policy file.
|
Related Commands
Command
|
Description
|
event manager policy
|
Registers an EEM policy with the EEM.
|
show event manager policy registered
To display Embedded Event Manager (EEM) policies that are already registered, use the show event manager policy registered command in privileged EXEC mode.
show event manager policy registered [event-type event-name] [system | user] [time-ordered |
name-ordered]
Syntax Description
event-type
|
(Optional) Displays the registered policies for the event type specified in the event-name argument. If the event type is not specified, all registered policies are displayed. The event-name argument can be one of the following:
• application—Application event type.
• cli—Command-line interface (CLI) event type.
• counter—Counter event type.
• interface—Interface event type.
• ioswdsysmon—Watchdog system monitor event type.
• memory—Memory thresholding event type.
• none—Manually run policy event type.
• snmp—Simple Network Management Protocol (SNMP) event type.
• syslog—Syslog event type.
• timer-absolute—Absolute timer event type.
• timer-countdown—Countdown timer event type.
• timer-cron—Clock daemon (CRON) timer event type.
• timer-watchdog—Watchdog timer event type.
|
system
|
(Optional) Displays the registered system policies.
|
user
|
(Optional) Displays the registered user policies.
|
time-ordered
|
(Optional) Displays the policies by the time at which they were registered. This is the default.
|
name-ordered
|
(Optional) Displays the policies in alphabetical order by policy name.
|
Defaults
If this command is invoked with no optional keywords, it displays all registered EEM system and user policies for all event types. The policies are displayed according to the time at which they were registered.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.0(26)S
|
This command was introduced.
|
12.3(4)T
|
This command was integrated into Cisco IOS Release 12.3(4)T.
|
12.2(25)S
|
This command was integrated into Cisco IOS Release 12.2(25)S.
|
12.3(14)T
|
Additional event types and the user keyword were added, and this command was integrated into Cisco IOS Release 12.3(14)T.
|
Usage Guidelines
The output of this command is most helpful to the person who has the task of writing and monitoring EEM policies. The output shows registered policy information in two parts. The first line in each policy description lists the index number assigned to the policy, the policy type (system), the type of event registered, the time when the policy was registered, and the name of the policy file. The remaining lines of each policy description display information about the registered event and how the event is to be handled; the information comes directly from the Tool Command Language (Tcl) command arguments that make up the policy file.
Examples
The following is sample output from the show event manager policy registered command:
Router# show event manager policy registered
No. Class Type Event Type Trap Time Registered Name
1 applet system snmp Off Fri Aug 13 17:42:52 2004 IPSLAping1
oid {1.3.6.1.4.1.9.9.42.1.2.9.1.6.4} get-type exact entry-op eq entry-val {1}
exit-op eq exit-val {2} poll-interval 5.000
action 1.0 syslog priority critical msg Server IPecho Failed: OID=$_snmp_oid_val
action 1.1 snmp-trap strdata EEM detected server reachability failure to 10.1.88.9
action 1.2 publish-event sub-system 88000101 type 1 arg1 10.1.88.9 arg2 IPSLAEcho arg3
fail
action 1.3 counter name _IPSLA1F value 1 op inc
Table 95 describes the significant fields shown in the display.
Table 95 show event manager policy registered Field Descriptions
Field
|
Description
|
No.
|
Index number automatically assigned to the policy.
|
Class
|
Class of policy, either applet or script.
|
Type
|
Whether the policy is a system policy.
|
Event Type
|
Type of event.
|
Trap
|
Whether an SNMP trap is enabled.
|
Time Registered
|
Time stamp indicating the date and time when the policy file was registered.
|
Name
|
Name of the EEM policy file.
|
Related Commands
Command
|
Description
|
event manager policy
|
Registers an EEM policy with the EEM.
|
show event manager session cli username
To display the username associated with Embedded Event Manager (EEM) policies that use the command-line interface (CLI) library, use the show event manager session cli username command in privileged EXEC mode.
show event manager session cli username
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.3(14)T
|
This command was introduced.
|
Usage Guidelines
Use this command to display the username associated with a Tool Command Language (Tcl) EEM policy. If you are using authentication, authorization, and accounting (AAA) security and implement authorization on a command basis, you should use the event manager session cli username command to set a username to be associated with a Tcl session. The username is used when a Tcl policy executes a CLI command. TACACS+ verifies each CLI command using the username associated with the Tcl session that is running the policy. Commands from Tcl policies are not usually verified because the router must be in privileged EXEC mode to register the policy.
Examples
The following example shows that the username of finance1 is associated with a Tcl session:
Router# show event manager session cli username
Related Commands
Command
|
Description
|
event manager session cli username
|
Associates a username with EEM policies that use the CLI library.
|
show file
The show file command has been replaced by the more command. See the description of the more command for more information.
show file descriptors
To display a list of open file descriptors, use the show file descriptors command in EXEC mode.
show file descriptors
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Release
|
Modification
|
11.3 AA
|
This command was introduced.
|
Usage Guidelines
File descriptors are the internal representations of open files. You can use this command to learn if another user has a file open.
Examples
The following is sample output from the show file descriptors command:
Router# show file descriptors
FD Position Open PID Path
0 187392 0001 2 tftp://dirt/hampton/c4000-i-m.a
1 184320 030A 2 flash:c4000-i-m.a
Table 96 describes the fields shown in the display.
Table 96 show file descriptors Field Descriptions
Field
|
Description
|
FD
|
File descriptor. The file descriptor is a small integer used to specify the file once it has been opened.
|
Position
|
Byte offset from the start of the file.
|
Open
|
Flags supplied when opening the file.
|
PID
|
Process ID of the process that opened the file.
|
Path
|
Location of the file.
|
show file information
To display information about a file, use the show file information command in EXEC mode.
show file information file-url
Syntax Description
file-url
|
The URL of the file to display.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
11.3 AA
|
This command was introduced.
|
Examples
The following is sample output from the show file information command:
Router# show file information tftp://dirt/hampton/c2500-j-l.a
tftp://dirt/hampton/c2500-j-l.a:
type is image (a.out) [relocatable, run from flash]
file size is 8624596 bytes, run size is 9044940 bytes [8512316+112248+420344]
Router# show file information slot0:c7200-js-mz
file size is 4770316 bytes, run size is 4935324 bytes
Runnable image, entry point 0x80008000, run from ram
Router1# show file information nvram:startup-config
Table 97 describes the possible file types.
Table 97 Possible File Types
Types
|
Description
|
image (a.out)
|
Runnable image in a.out format.
|
image (elf)
|
Runnable image in elf format.
|
ascii text
|
Configuration file or other text file.
|
coff
|
Runnable image in coff format.
|
ebcdic
|
Text generated on an IBM mainframe.
|
lzw compression
|
Lzw compressed file.
|
tar
|
Text archive file used by the Channel Interface Processor (CIP).
|
show file systems
To list available file systems, use the show file systems command in privileged EXEC mode.
show file systems
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
11.3 AA
|
This command was introduced.
|
12.3(7)T
|
This command was enhanced to display information about the ATA ROM monitor library (monlib) file.
|
12.2(25)S
|
This command was integrated into the Cisco IOS Release 12.2(25)S.
|
Usage Guidelines
Use this command to learn the alias names (Prefixes) of the file systems that your router supports.
Examples
The following is sample output from the show file systems command:
Router# show file systems
Size(b) Free(b) Type Flags Prefixes
* 4798624- 4567040 disk rw disk0:#
* 4194304 4190616 flash rw flash:
131066 129185 nvram rw nvram:
Table 98 describes the significant fields shown in the display.
Table 98 show file systems Field Descriptions
Field
|
Description
|
Size(b)
|
Amount of memory in the file system (in bytes).
|
Free(b)
|
Amount of free memory in the file system (in bytes).
|
Type
|
Type of file system. The file system can be one of the following types:
• disk—The file system is for a rotating medium.
• flash—The file system is for a flash memory device.
• network—The file system is a network file system (TFTP, rcp, FTP, and so on).
• nvram—The file system is for an NVRAM device.
• opaque—The file system is a locally generated "pseudo" file system (for example, the "system") or a download interface, such as brimux.
• rom—The file system is for a ROM or EPROM device.
• tty—The file system is for a collection of terminal devices.
• unknown—The file system is of unknown type.
|
Flags
|
Permissions for file system. The file system can have one of the following permission states:
• ro—The file system is Read Only.
• wo—The file system is Write Only.
• rw—The file system is Read/Write.
|
Prefixes
|
Alias for file system. Prefixes marked with a pound symbol (#) indicate a bootable disk.
|
show flh-log
The show flh-log command has been replaced by the more flh:logfile command. See the description of the more flh:logfile command for more information.
show gsr
To display hardware information on the Cisco 12000 series Gigabit Switch Routers (GSRs), use the show gsr command in EXEC mode.
show gsr [chassis-info [details]]
Syntax Description
chassis-info
|
(Optional) Displays backplane NVRAM information.
|
details
|
(Optional) In addition to the information displayed, this option includes hexadecimal output of the backplane NVRAM information.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
11.2GS
|
This command was introduced to support the Cisco 12000 series GSRs.
|
Usage Guidelines
Use this command to determine the type of hardware installed in your Cisco 12000 series GSR router.
Examples
The following is sample output from the show gsr command for a Cisco 12012 router. This command shows the type and state of the card installed in the slot.
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:
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 (7200)
To display all GT64010 internal registers and interrupt status on the Cisco 7200 series routers, use the show gt64010 command in EXEC mode.
show gt64010
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Release
|
Modification
|
11.2
|
This command was introduced.
|
Usage Guidelines
This command displays information about the CPU interface, DRAM/device address space, device parameters, direct memory access (DMA) channels, timers and counters, and protocol control information (PCI) internal registers. The information is generally useful for diagnostic tasks performed by technical support only.
Examples
The following is a partial sample output for the show gt64010 command:
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 history
To list the commands you have entered in the current EXEC session, use the show history command in EXEC mode.
show history
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
Usage Guidelines
The command history feature provides a record of EXEC commands you have entered. The number of commands that the history buffer will record is determined by the history size line configuration command or the terminal history size EXEC command.
Table 99 lists the keys and functions you can use to recall commands from the command history buffer.
Table 99 History Keys
Key
|
Function
|
Ctrl-P or Up Arrow1
|
Recalls commands in the history buffer in a backward sequence, beginning with the most recent command. Repeat the key sequence to recall successively older commands.
|
Ctrl-N or Down Arrow1
|
Returns to more recent commands in the history buffer after recalling commands with Ctrl-P or the Up Arrow. Repeat the key sequence to recall successively more recent commands.
|
Examples
The following is sample output from the show history command, which lists the commands the user has entered in EXEC mode for this session:
Related Commands
Command
|
Description
|
history size
|
Enables the command history function, or changes the command history buffer size for a particular line.
|
terminal history size
|
Enables the command history feature for the current terminal session, or changes the size of the command history buffer for the current terminal session.
|
show idb
To display information about the status of interface descriptor blocks (IDBs), use the show idb command in privileged EXEC mode.
show idb
Syntax Description
This command has nor arguments or keywords.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.1
|
This command was introduced.
|
12.2(15)T
|
The output of this command was changed to show additional information.
|
Examples
The following is sample output from the show idb command:
Maximum number of Software IDBs 8192. In use 17.
Size each (bytes) 5784 2576
HWIDB#1 1 2 GigabitEthernet0/0 0 5, HW IFINDEX, Ether)
HWIDB#2 2 3 GigabitEthernet9/0 0 5, HW IFINDEX, Ether)
HWIDB#3 3 4 GigabitEthernet9/1 6 5, HW IFINDEX, Ether)
HWIDB#4 4 5 GigabitEthernet9/2 6 5, HW IFINDEX, Ether)
HWIDB#5 13 1 Ethernet0 4 5, HW IFINDEX, Ether)
Table 100 describes the significant fields shown in the display.
Table 100 show idb Field Descriptions
Field
|
Description
|
In use
|
Total number of software IDBs (SWIDBs) that have been allocated. This number never decreases. SWIDBs are never deallocated.
|
Active
|
Total number of hardware IDBs (HWIDBs) and SWIDBs that are allocated and in use.
|
Inactive
|
Total number of HWIDBs and SWIDBs that are allocated but not in use.
|
Total
|
Total number of HWIDBs and SWIDBs that are allocated.
|
show inventory
To display the product inventory listing of all Cisco products installed in the networking device, use the show inventory command in user EXEC or privileged EXEC mode.
show inventory [raw] [entity]
Syntax Description
raw
|
(Optional) Retrieves information about all of the Cisco products—referred to as entities—installed in the Cisco networking device, even if the entities do not have a product ID (PID) value.
|
entity
|
(Optional) Name of a Cisco entity (for example, chassis, backplane, module).
|
Defaults
Displays a list of Cisco entities installed in the networking device that are assigned a PID.
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
12.3(4)T
|
This command was introduced.
|
Usage Guidelines
The show inventory command retrieves and displays inventory information about each Cisco product in the form of a unique device identifier (UDI). The Cisco UDI is a combination of three separate data elements: a PID which can be used to order a Cisco product, version identifier (VID), and the serial number (SN).
The Cisco UDI refers to each product as an entity. Some entities, such as a chassis, will have subentities like slots. Each entity will display on a separate line in a logically-ordered presentation that is arranged hierarchically by Cisco entities.
Examples
The following is sample output from the show inventory command without any keywords or arguments. This sample output displays a list of Cisco entities installed in a router that are assigned a PID.
NAME: "Chassis", DESCR: "12008/GRP chassis"
PID: GSR8/40 , VID: V01, SN: 63915640
NAME: "slot 0", DESCR: "GRP"
PID: GRP-B , VID: V01, SN: CAB021300R5
NAME: "slot 1", DESCR: "4 port ATM OC3 multimode"
PID: 4OC3/ATM-MM-SC , VID: V01, SN: CAB04036GT1
NAME: "slot 3", DESCR: "4 port 0C3 POS multimode"
PID: LC-4OC3/POS-MM , VID: V01, SN: CAB014900GU
NAME: "slot 5", DESCR: "1 port Gigabit Ethernet"
PID: GE-GBIC-SC-B , VID: V01, SN: CAB034251NX
NAME: "slot 7", DESCR: "GRP"
PID: GRP-B , VID: V01, SN: CAB0428AN4O
NAME: "slot 16", DESCR: "GSR 12008 Clock Scheduler Card"
PID: GSR8-CSC/ALRM , VID: V01, SN: CAB0429AUYH
NAME: "sfslot 1", DESCR: "GSR 12008 Switch Fabric Card"
PID: GSR8-SFC , VID: V01, SN: CAB0428ALOS
NAME: "sfslot 2", DESCR: "GSR 12008 Switch Fabric Card"
PID: GSR8-SFC , VID: V01, SN: CAB0429AU0M
NAME: "sfslot 3", DESCR: "GSR 12008 Switch Fabric Card"
PID: GSR8-SFC , VID: V01, SN: CAB0429ARD7
NAME: "PSslot 1", DESCR: "GSR 12008 AC Power Supply"
PID: FWR-GSR8-AC-B , VID: V01, SN: CAB041999CW
Table 101 describes the fields shown in the display.
Table 101 show inventory Field Descriptions
Field
|
Description
|
NAME
|
Physical name (text string) assigned to the Cisco entity. For example, console or a simple component number (port or module number), such as "1," depending on the physical component naming syntax of the device.
|
DESCR
|
Physical description of the Cisco entity that characterizes the object. The physical description includes the hardware serial number and the hardware revision.
|
PID
|
Entity product identifier.
|
VID
|
Entity version identifier.
|
SN
|
Entity serial number.
|
The following is sample output from the show inventory raw command. The raw keyword generates a list of all Cisco entities that are in the chassis: entities with and without an assigned PID.
Router# show inventory raw
NAME: "Chassis", DESCR: "12008/GRP chassis"
PID: , VID: V01, SN: 63915640
NAME: "slot 0", DESCR: "GRP"
PID: , VID: V01, SN: CAB021300R5
NAME: "slot 1", DESCR: "4 port ATM OC3 multimode"
PID: 4OC3/ATM-MM-SC , VID: V01, SN: CAB04036GT1
NAME: "slot 3", DESCR: "4 port 0C3 POS multimode"
PID: LC-4OC3/POS-MM , VID: V01, SN: CAB014900GU
In the following example, a value for the entity argument is specified with the show inventory command. This sample output displays a list of the Cisco entities that match the string specified by the entity argument.
Router# show inventory Psslot 1
NAME: "PSslot 1", DESCR: "GSR 12008 AC Power Supply"
PID: FWR-GSR8-AC-B , VID: V01, SN: CAB041999CW
Related Commands
Command
|
Description
|
show diag
|
Displays diagnostic information about the controller, interface processor, and port adapters for a networking device.
|
show tech-support
|
Displays general information about the router when it reports a problem.
|
show ip director default
To verify default metric configuration information for DistributedDirector metrics, use the show ip director default command in privileged EXEC mode.
show ip director default [priority | weight]
Syntax Description
priority
|
(Optional) Default priorities for metrics.
|
weight
|
(Optional) Displays the weights for metrics.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.2(4)T
|
This command was introduced.
|
Usage Guidelines
Use this command to verify default metric configurations.
Examples
The following is sample output from the show ip director default priority command:
Router# show ip director default priority
Director default metric priorities:
DRP route lookup external to AS priority = 1
administrative preference priority = 0
DRP route lookup internal to AS priority = 0
DRP distance to associated server priority = 0
Round-trip time from DRP to client priority = 0
DFP originated weight priority = 0
Route-map evaluation priority = 0
Related Commands
Command
|
Description
|
ip director default priorities
|
Sets default priorities for DistributedDirector metrics.
|
show ip director dfp
To display information about the current status of the DistributedDirector connections with a particular Dynamic Feedback Protocol (DFP) agent, use the show ip director dfp command in EXEC mode.
show ip director dfp [host-name | ip-address]
Syntax Description
host-name
|
(Optional) Host name.
|
ip-address
|
(Optional) IP address.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
12.1(5)T
|
This command was introduced.
|
Examples
The following is sample output from the show ip director dfp command:
Router# show ip director dfp
Timeout between connect attempts: 60
Timeout between updates: 90
Last update received: 00:00:12 ago
Server Port BindID Address Mask
172.28.9.9 80 0 0.0.0.0 0.0.0.0
Timeout between connect attempts: 60
Timeout between updates: 90
Last update received: 00:00:44 ago
Server Port BindID Address Mask
192.168.30.30 80 0 0.0.0.0 0.0.0.0
show ip drp boomerang
To display the status of various boomerang domains, use the show ip drp boomerang command in privileged EXEC mode.
show ip drp boomerang [domain-name]
Syntax Description
domain-name
|
(Optional) Specified domain name.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.2(8)T
|
This command was introduced.
|
Usage Guidelines
The show ip drp boomerang command can be used on the boomerang client to display the status of the various boomerang domains. The following information can be shown for each domain:
•
Alias information—The number of DNS requests for each alias.
•
Content server address information:
–
Number of DNS requests.
–
Number of requests dropped because server is down.
–
Number of requests dropped because there is no original server.
–
Number of requests dropped because of security failures.
Examples
The following is sample output from the show ip drp boomerang command:
Router# show ip drp boomerang www.boom1.com
DNS packets with unknown domain 0
Content server 172.16.101.101 up
Dropped (no origen server) 0
Related Commands
Command
|
Description
|
alias (boomerang configuration)
|
Configures an alias name for a specified domain.
|
ip drp domain
|
Adds a new domain to the DistributedDirector client or configures an existing domain and puts the client in boomerang configuration mode.
|
server (boomerang configuration)
|
Configures the server address for a specified boomerang domain.
|
show ip drp
|
Displays DRP statistics on DistributedDirector or a DRP server agent.
|
ttl dns
|
Configures the number of seconds for which an answer received from the boomerang client will be cached by the DNS client.
|
ttl ip
|
Configures the IP TTL value for the boomerang response packets sent from the boomerang client to the DNS client in number of hops.
|
show ip http client connection
To display a report about HTTP client active connections, use the show ip http client connection command in privileged EXEC mode.
show ip http client connection
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.3(2)T
|
This command was introduced.
|
Usage Guidelines
Use this command to display active connections and configured values for connections.
Examples
The following is sample output from the show ip http client connection command:
Router# show ip http client connection
HTTP client current connections:
Persistent connection = enabled (default)
Connection establishment timeout = 10s (default)
Connection idle timeout = 30s (default)
Maximum number of connection establishment retries = 1 (default)
Maximum http client connections per host : 2
HTTP secure client capability: Not present
local-ipaddress:port remote-ipaddress:port in-bytes out-bytes
:80 172.20.67.174:11012 12584 176
Total client connections : 1
The report is self-explanatory and lists the active connections and user-configured or default values for the connections.
Related Commands
Command
|
Description
|
copy
|
Copies a file from any supported remote location to a local file system, or from a local file system to a remote location, or from a local file system to a local file system.
|
debug ip http client
|
Enables debugging output for the HTTP client.
|
ip http client connection
|
Configures the HTTP client connection.
|
ip http client password
|
Configures a password for all HTTP client connections.
|
ip http client proxy-server
|
Configures an HTTP proxy server.
|
ip http client source-interface
|
Configures a source interface for the HTTP client.
|
ip http client username
|
Configures a login name for all HTTP client connections.
|
show ip http client history
|
Displays the URLs accessed by the HTTP client.
|
show ip http client session-module
|
Displays a report about sessions that have registered with the HTTP client.
|
show ip http client history
To display up to 20 URLs accessed by the HTTP client, use the show ip http client history command in privileged EXEC mode.
show ip http client history
Syntax Description
This command has no arguments or keywords
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.3(2)T
|
This command was introduced.
|
Usage Guidelines
This command displays a list of up to 20 URLs most recently accessed by the HTTP client.
Examples
The following is sample output from the show ip http client history command:
Router# show ip http client history
GET 03:25:36 UTC Thu Feb 26 2004
mailer.cisco.com/mailer.html
GET 03:25:56 UTC Thu Feb 26 2004
mailer.cisco.com/mailer.html
GET 03:26:10 UTC Thu Feb 26 2004
mailer.cisco.com/mailer.html
The report is self-explanatory and lists the most recent URLs accessed by the HTTP client.
Related Commands
Command
|
Description
|
copy
|
Copies a file from any supported remote location to a local file system, or from a local file system to a remote location, or from a local file system to a local file system.
|
debug ip http client
|
Enables debugging output for the HTTP client.
|
ip http client connection
|
Configures the HTTP client connection.
|
ip http client password
|
Configures a password for all HTTP client connections.
|
ip http client proxy-server
|
Configures an HTTP proxy server.
|
ip http client source-interface
|
Configures a source interface for the HTTP client.
|
ip http client username
|
Configures a login name for all HTTP client connections.
|
show ip http client connection
|
Displays a report about HTTP client active connections.
|
show ip http client session-module
|
Displays a report about sessions that have registered with the HTTP client.
|
show ip http client session-module
To display a report about sessions or applications that have registered with the HTTP client, use the show ip http client session-module command in privileged EXEC mode.
show ip http client session-module
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.3(2)T
|
This command was introduced.
|
Usage Guidelines
Use this command to display information about applications that have registered with the HTTP client.
Examples
The following is sample output from the show ip http client session-module command:
Router# show ip http client session-module
HTTP client application session modules:
Application Name :HTTP CFS
Persistent :non-persistent
Application Name :httpc_ifs_0
Persistent :non-persistent
Table 102 describes the fields shown in the display.
Table 102 show ip http client session-module Field Descriptions
Field
|
Description
|
Id
|
A number that identifies the registering application. Every application or session that registers with the HTTP client is provided an identification number.
|
Application Name
|
Name of the application in use. Every application or session that registers with the HTTP client provides a name that is displayed by this field. In the sample output, HTTP CFS is the name for the HTTP Client File Session application, and the name httpc_ifs_0 is the HTTPC IFS Copy application.
|
Version
|
HTTP protocol version supported by the application. Every application or session that registers with the HTTP client indicates the HTTP protocol version it supports in this field. HTTP1.0 does not support persistent connections; HTTP1.1 supports both persistent and nonpersistent connections.
|
Persistent
|
Value of the persistent connection. Persistent indicates that the application needs the HTTP client to maintain connection after data transfer from itself to the remote server. Nonpersistent indicates that the application does not need the HTTP client to maintain connections after the data transfer.
|
Response-timeout
|
Configured response timeout period, in seconds. The application specifies the amount of time the HTTP Client has to wait for a response from the remote server before returning a failure notice, for those data transfers initiated by this application.
|
Retries
|
Configured connection retries. The application specifies the number of retries for establishing connection that the HTTP client must attempt before returning a failure notice to the application.
|
Proxy
|
Specifies a proxy name that the HTTP client uses to route all HTTP data transfer requests to or from the application.
|
Related Commands
Command
|
Description
|
copy
|
Copies a file from any supported remote location to a local file system, or from a local file system to a remote location, or from a local file system to a local file system.
|
debug ip http client
|
Enables debugging output for the HTTP client.
|
ip http client connection
|
Configures the HTTP client connection.
|
ip http client password
|
Configures a password for all HTTP client connections.
|
ip http client proxy-server
|
Configures an HTTP proxy server.
|
ip http client source-interface
|
Configures a source interface for the HTTP client.
|
ip http client username
|
Configures a login name for all HTTP client connections.
|
show ip http client connection
|
Displays a report about HTTP client active connections.
|
show ip http client history
|
Displays the URLs accessed by the HTTP client.
|
show ip http server
To display details about the current configuration of the HTTP server, use the show ip http server command in user EXEC or privileged EXEC mode.
show ip http server {all | status | session-module | connection | statistics | history}
Syntax Description
all
|
Displays all HTTP server information.
|
status
|
Displays only HTTP server status configuration.
|
session-module
|
Displays only supported HTTP services (Cisco IOS modules).
|
connection
|
Displays only the current connections to the HTTP server, including the local and remote IP addresses being accessed.
|
statistics
|
Displays only HTTP server connection statistics.
|
history
|
Displays only the previous 20 connections to the HTTP server, including the IP address accessed, and the time when the connection was closed.
|
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
12.2(15)T
|
This command was introduced.
|
Usage Guidelines
Use this command to show detailed status information about the HTTP server.
If the HTTP secure server capability is present, the output of the show ip http server all command will also include the information found in the output of the show ip http server secure status command.
Examples
The following is sample output from the show ip http server all command:
Router# show ip http server all
HTTP server status: Enabled
HTTP server authentication method: enable
HTTP server access class: 0
Maximum number of concurrent server connections allowed: 5
Server idle time-out: 30 seconds
Server life time-out: 120 seconds
Maximum number of requests allowed on a connection: 2
HTTP secure server capability: Not Present
HTTP server application session modules:
Session module Name Handle Description
Homepage_Server 5 IOS Homepage Server
QDM 2 QOS Device Manager Server
HTTP IFS Server 1 HTTP based IOS File Server
QDM SA 3 QOS Device Manager Signed Applet Server
WEB_EXEC 4 HTTP based IOS EXEC Server
XSM 6 XML Session Manager
VDM 7 VPN Device Manager Server
ITS 8 IOS Telephony Service
ITS_LOCDIR 9 ITS Local Directory Search
HTTP server current connections:
local-ipaddress:port remote-ipaddress:port in-bytes out-bytes
172.19.254.37:80 128.190.254.45:33737 70 2294
Accepted connections total: 1360
local-ipaddress:port remote-ipaddress:port in-bytes out-bytes end-time
172.91.254.37:80 128.190.254.45:63530 60 1596 10:50:00 12/19
Table 103 describes the significant fields shown in the display.
Table 103 show ip http server Field Descriptions
Field
|
Description
|
HTTP server status:
|
Enabled or disabled. Corresponds to the [no] ip http server command.
|
HTTP server port:
|
Port used by the HTTP server. Corresponds to the ip http port command.
|
HTTP server authentication method:
|
Authentication method used for HTTP server logins. Corresponds to the ip http authentication command.
|
HTTP server access class:
|
Access list number assigned to the HTTP server. A value of zero (0) indicates no access list is assigned. Corresponds to the ip http access-class command.
|
HTTP server base path:
|
Base HTTP path specifying the location of the HTTP server files (HTML files). Corresponds to the ip http path command.
|
Maximum number of concurrent server connections allowed:
|
Corresponds to the ip http max-connections command.
|
Server idle time-out:
|
The maximum number of seconds the connection will be kept open if no data is received or if response data can not be sent out. Corresponds to the ip http timeout-policy command.
|
Server life time-out:
|
The maximum number of seconds the connection will be kept open. Corresponds to the ip http timeout-policy command.
|
Maximum number of requests allowed on a connection:
|
The maximum number of requests that will be processed on a connection before the connection is closed. Corresponds to the ip http timeout-policy command.
|
HTTP secure server capability:
|
Indicates if the running software image supports the secure HTTP server ("Present" or "Not Present"). If the capability is present, the output from the show ip http server secure status command will appear after this line.
|
HTTP server application session modules:
|
Cisco IOS services that use the HTTP server. Services are provided for application interfaces, including:
• the Cisco Web browser user interface, which uses the Cisco IOS Homepage Server, HTTP-based EXEC Server, and HTTP IOS File System (IFS) Server
• the VPN Device Manager (VDM) application, which uses the VDM Server and the XML Session Manager (XSM)
• the QoS Device Manager (QDM) application, which uses the QDM Server
• the IP Phone and Cisco IOS Telephony Service applications, which use the ITS Local Directory Search and IOS Telephony Server (ITS)
|
HTTP server current connections:
|
Currently active HTTP connections.
|
HTTP server statistics:
|
How many connections have been accepted.
|
HTTP server history:
|
Details about the last 20 connections, including the time the connection was closed (end-time). End-time is given in Universal Coordinated Time (UTC or GMT), using a 24-hour clock and the following format:
hh:mm:ss month/day
|
The following example shows sample output for the show ip http server status command:
Router# show ip http server status
HTTP server status: Disabled
HTTP server authentication method: enable
HTTP server access class: 0
Maximum number of concurrent server connections allowed: 5
Server idle time-out: 600 seconds
Server life time-out: 600 seconds
Maximum number of requests allowed on a connection: 1
HTTP secure server capability: Present
HTTP secure server status: Disabled
HTTP secure server port: 443
HTTP secure server ciphersuite: 3des-ede-cbc-sha des-cbc-sha rc4-128-md5 rc4-12a
HTTP secure server client authentication: Disabled
HTTP secure server trustpoint:
The lines indicating the status of the HTTP secure (HTTPS) server will only be visible if your software image supports the HTTPS server. If your software image does not support SSL, only the following line will be visible:
HTTP secure server capability: Not present
Related Commands
Command
|
Description
|
debug ip http server all
|
Enables debugging output for all HTTP processes on the system.
|
ip http server
|
Enables the HTTP 1.1 server, including the Cisco web browser user interface.
|
ip http secure-server
|
Enables the secure HTTP (HTTPS) server.
|
show ip http server secure status
|
Displays the status of the secure HTTP (HTTPS) server.
|
show ip sla monitor apm cache
To display the amount of memory available in the Cisco IOS IP Service Level Agreements (SLAs) Application Performance Monitor (APM) cache and information about the files stored in the cache, use the show ip sla monitor apm cache command in user EXEC or privileged EXEC mode.
show ip sla monitor apm cache
Syntax Description
This command has no arguments or keywords.
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
12.3(14)T
|
This command was introduced. This command replaces the show saa apm cache command.
|
Usage Guidelines
IP SLAs APM script and scheduler files are kept in an area of system memory called the IP SLAs APM cache.
Examples
The following is sample output from the show ip sla monitor apm cache command:
Router# show ip sla monitor apm cache
Cache Size (bytes): 100000
TimeCreated TimeAccessed Size Ref Loc Type SBit FileName
03/21 13:31:25 03/21 13:31:48 1170 0 1 SCR 0 user/scripts/ldap-rem.scr
03/21 13:31:23 03/21 13:31:48 38 0 1 DAT 0 user/data/ldap-rem.dat
03/21 13:31:22 03/21 13:31:27 69 1 0 DAT 0 user/data/ldap.dat
03/21 13:31:20 03/21 13:31:27 1513 1 0 SCR 0 user/scripts/ldap.scr
03/21 13:31:19 03/21 13:31:27 2500 1 0 SCH 0 user/scheduler/master.sch
03/21 13:31:17 03/21 13:31:27 256 1 0 CFG 0 apm.cfg.1
03/21 13:31:17 03/21 13:31:17 568 1 0 CFG 0 user/config/ldap.cf
03/20 14:29:13 03/20 14:29:36 735 0 1 SCR 0 user/scripts/udp-rem.scr
Table 104 describes the significant fields shown in the display.
Table 104 show ip sla monitor apm cache Field Descriptions
Field
|
Description
|
Size
|
Size of the file, in bytes.
|
Ref
|
Referencing count. Indicates how many APM operations are accessing (referencing) the file.
|
Loc
|
"Local" value. Indicates whether the file is local or remote. Possible values are:
• 0—File is remote.
• 1—File is local.
|
Type
|
Type of file in the cache. Possible types are:
• CFG—APM configuration file
• DAT—APM data file
• SCR—APM script file
• SCH—APM scheduler file
|
SBit
|
"Sticky bit" value. Possible values are:
• 0—sticky bit is not set; this file will be deleted from the APM cache during the next cache trimming operation, or when a clear ip sla monitor apm cache command is executed.
• 1—sticky bit is set; this file can be deleted only by using the force keyword with the clear ip sla monitor apm cache command.
|
Related Commands
Command
|
Description
|
clear ip sla monitor apm cache
|
Deletes files from the IP SLAs APM cache.
|
ip sla monitor apm cache-size
|
Sets the size of the IP SLAs APM cache.
|
show ip sla monitor apm operation
|
Displays details about IP SLAs APM operations.
|
show ip sla monitor apm information
To display details about a Cisco IOS IP Service Level Agreements (SLAs) Application Performance Monitor (APM) running on the system, use the show ip sla monitor apm information command in user EXEC or privileged EXEC mode.
show ip sla monitor apm information
Syntax Description
This command has no arguments or keywords.
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
12.3(14)T
|
This command was introduced. This command replaces the show saa apm information command.
|
Examples
The following is sample output from the show ip sla monitor apm information command:
Router# show ip sla monitor apm information
Service Assurance Agent: Application Performance Monitor
Max Number of oper supported: 50
Number of configurable oper: 50
Number of oper configured: 0
Number of files in cache: 0
Cache Size (bytes): 100000
APM low memory water-mark: 6708828
Related Commands
Command
|
Description
|
ip sla monitor apm lowWaterMark
|
Specifies the lowest amount of free memory that must be available on the system to allow additional IP SLAs APM operations to be configured.
|
show ip sla monitor apm operation
To display details about a Cisco IOS IP Service Level Agreements (SLAs) Application Performance Monitor (APM) operation, use the show ip sla monitor apm operation command in user EXEC or privileged EXEC mode.
show ip sla monitor apm operation [operation-number]
Syntax Description
operation-number
|
(Optional) Number that uniquely identifies an APM operation.
|
Defaults
Information for all APM operations is displayed.
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
12.3(14)T
|
This command was introduced. This command replaces the show saa apm operation command.
|
Examples
The following is sample output from the show ip sla monitor apm operation command:
Router# show ip sla monitor apm operation
ControlFile URL: ftp://user:password@saa-nms/apm/config/smtp-1000.cfg
Latest Operation Time: *08:13:40.000 UTC Mon Oct 08 2001
Latest Operation Status: 0
show ip sla monitor apm results
To display the accumulated data for Cisco IOS IP Service Level Agreements (SLAs) Application Performance Monitor (APM) operations, use the show ip sla monitor apm results command in user EXEC or privileged EXEC mode.
show ip sla monitor apm results [operation-number]
Syntax Description
operation-number
|
(Optional) Number that uniquely identifies an APM operation. If an operation number is not specified, all operation results in the buffer are displayed.
|
Defaults
All APM operation results are displayed.
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
12.3(14)T
|
This command was introduced. This command replaces the show saa apm results command.
|
Usage Guidelines
IP SLAs APM script and scheduler files are kept in an area of system memory called the IP SLAs APM cache.
Examples
The following is sample output from the show ip sla monitor apm results command:
Router# show ip sla monitor apm results
Cache Size (bytes): 100000
Cache used (bytes): 14188
File Name TimeCreated TimeAccessed ref Type sticky
apm/data/ldap-13.dat 13:37:20 13:37:25 1 DAT 0
apm.cf.9 13:37:18 13:37:25 1 CFG 0
apm/config/ldap-13.cf 13:37:18 00:00:00 1 CFG 0
apm/data/ldap-12.dat 13:37:15 13:37:20 1 DAT 0
apm.cf.8 13:37:14 13:37:20 1 CFG 0
apm/config/ldap-12.cf 13:37:14 00:00:00 1 CFG 0
apm/data/ldap-11.dat 13:37:11 13:37:16 1 DAT 0
apm.cf.7 13:37:11 13:37:16 1 CFG 0
apm/config/ldap-11.cf 13:37:11 00:00:00 1 CFG 0
apm/scripts/ldap.scr 13:37:07 13:37:29 3 SCR 0
apm/data/iptv-2.dat 13:36:49 13:36:54 1 DAT 0
apm/config/iptv-2.cf 13:36:48 00:00:00 1 CFG 0
apm/scripts/iptv.scr 13:36:47 13:37:08 1 SCR 0
apm/scheduler/master.sch 13:36:45 13:37:34 4 SCH 0
Table 105 describes the significant fields shown in the display.
Table 105 show ip sla monitor apm results Field Descriptions
Field
|
Description
|
Type
|
Type of file in cache. Possible types are:
• CFG—APM configuration file
• DAT—APM data file
• SCR—APM script file
• SCH—APM scheduler file
|
sticky
|
"Sticky bit" value. Possible values are:
• 0—sticky bit is not set; this file will be deleted from the APM cache during the next cache trimming operation, or when a clear ip sla monitor apm cache command is executed.
• 1—sticky bit is set; this file can be deleted only by using the force keyword with the clear ip sla monitor apm cache command.
|
Related Commands
Command
|
Description
|
clear ip sla monitor apm cache
|
Deletes files from the IP SLAs APM cache.
|
ip sla monitor apm cache-size
|
Sets the size of the IP SLAs APM cache.
|
show ip sla monitor apm operation
|
Displays details about IP SLAs APM operations.
|
show ip sla monitor application
To display global information about Cisco IOS IP Service Level Agreements (SLAs), use the show ip sla monitor application command in user EXEC or privileged EXEC mode.
show ip sla monitor application [tabular | full]
Syntax Description
tabular
|
(Optional) Displays information in a column format, reducing the number of screens required to display the information.
|
full
|
(Optional) Displays all information, using identifiers next to each displayed value. This is the default.
|
Defaults
Full format
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
12.3(14)T
|
This command was introduced. This command replaces the show rtr application command.
|
Usage Guidelines
Use the show ip sla monitor application command to display information such as supported operation types and supported protocols.
Examples
The following is sample output from the show ip sla monitor application command in full format:
Router# show ip sla monitor application
IP Service Level Agreement Monitor
Version: 2.2.0 Round Trip Time MIB
Time of last change in whole IP SLA Monitor: *17:21:30.819 UTC Tue Mar 19 2002
Estimated system max number of entries: 4699
Number of Entries configured:5
Number of active Entries:5
Number of pending Entries:0
Number of inactive Entries:0
Supported Operation Types
Type of Operation to Perform: echo
Type of Operation to Perform: pathEcho
Type of Operation to Perform: udpEcho
Type of Operation to Perform: tcpConnect
Type of Operation to Perform: http
Type of Operation to Perform: dns
Type of Operation to Perform: jitter
Type of Operation to Perform: dlsw
Type of Operation to Perform: dhcp
Type of Operation to Perform: ftp
Protocol Type: ipIcmpEcho
Protocol Type: ipUdpEchoAppl
Protocol Type: snaLU0EchoAppl
Protocol Type: snaLU2EchoAppl
Protocol Type: jitterAppl
Number of configurable probe is 490
Related Commands
Command
|
Description
|
show ip sla monitor configuration
|
Displays configuration values including all defaults for all IP SLAs operations or the specified operation.
|
show ip sla monitor authentication
To display Cisco IOS IP Service Level Agreements (SLAs) authentication information, use the show ip sla monitor authentication command in user EXEC or privileged EXEC mode.
show ip sla monitor authentication
Syntax Description
This command has no arguments or keywords.
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
12.3(14)T
|
This command was introduced. This command replaces the show rtr authentication command.
|
Usage Guidelines
Use the show ip sla monitor authentication command to display information such as supported operation types and supported protocols.
Examples
The following is sample output from the show ip sla monitor authentication command:
Router# show ip sla monitor authentication
IP SLA Monitor control message uses MD5 authentication, key chain name is: ipsla
Related Commands
Command
|
Description
|
show ip sla monitor configuration
|
Displays configuration values for IP SLAs operations.
|
show ip sla monitor collection-statistics
To display statistical errors for all Cisco IOS IP Service Level Agreements (SLAs) operations or a specified operation, use the show ip sla monitor collection-statistics command in user EXEC or privileged EXEC mode.
show ip sla monitor collection-statistics [operation-number]
Syntax Description
operation-number
|
(Optional) Number of the IP SLAs operation to display.
|
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
12.3(14)T
|
This command was introduced. This command replaces the show rtr collection-statistics command.
|
Usage Guidelines
Use the show ip sla monitor collection-statistics command to display information such as the number of failed operations and the failure reason. You can also use the show ip sla monitor distribution-statistics and show ip sla monitor totals-statistics commands to display additional statistical information.
This command shows information collected over the past two hours, unless you specify a different amount of time using the hours-of-statistics-kept command.
For one-way delay jitter operations, the clocks on each device must be synchronized using Network Time Protocol (NTP) or global positioning systems. If the clocks are not synchronized, one-way measurements are discarded. (If the sum of the source to destination (SD) and the destination to source (DS) values is not within 10 percent of the round-trip time, the one-way measurement values are assumed to be faulty, and are discarded.)
Note
This command does not support the IP SLAs ICMP path jitter operation.
Examples
The following is sample output from the show ip sla monitor collection-statistics command:
Router# show ip sla monitor collection-statistics 1
Start Time Index: *17:15:41.000 UTC Thu May 16 1996
Number of Failed Operations due to a Disconnect: 0
Number of Failed Operations due to a Timeout: 0
Number of Failed Operations due to a Busy: 0
Number of Failed Operations due to a No Connection: 0
Number of Failed Operations due to an Internal Error: 0
Number of Failed Operations due to a Sequence Error: 0
Number of Failed Operations due to a Verify Error: 0
Target Address: 172.16.1.176
Output for HTTP Operations
The following is output from the show ip sla monitor collection-statistics command when the specified operation is an HTTP operation:
Router# show ip sla monitor collection-statistics 2
HTTP URL:http://172.20.150.200
Start Time:*00:01:16.000 UTC Mon Nov 1 2003
TCPTimeOut:0 RTTSum2:117649
Output for UDP Jitter Operations
The following is sample output from the show ip sla monitor collection-statistics command, where operation 2 is a jitter operation that includes one-way statistics. Table 106 describes the significant fields shown in the display.
Router# show ip sla monitor collection-statistics
Target Address: 5.0.0.1, Port Number:99
Start Time: 11:12:03.000 UTC Thu Jul 1 1999
NumOfRTT: 600 RTTSum: 3789 RTTSum2: 138665
PacketLossSD: 0 PacketLossDS: 0
PacketOutOfSequence: 0 PacketMIA: 0 PacketLateArrival: 0
InternalError: 0 Busies: 0
MinOfPositivesSD: 1 MaxOfPositivesSD: 2
NumOfPositivesSD: 26 SumOfPositivesSD: 31 Sum2PositivesSD: 41
MinOfNegativesSD: 1 MaxOfNegativesSD: 4
NumOfNegativesSD: 56 SumOfNegativesSD: 73 Sum2NegativesSD: 133
MinOfPositivesDS: 1 MaxOfPositivesDS: 338
NumOfPositivesDS: 58 SumOfPositivesDS: 409 Sum2PositivesDS: 114347
MinOfNegativesDS: 1 MaxOfNegativesDS: 338
NumOfNegativesDS: 48 SumOfNegativesDS: 396 Sum2NegativesDS: 114332
OWMinSD: 2 OWMaxSD: 6 OWSumSD: 1273 OWSum2SD: 4021
OWMinDS: 2 OWMaxDS: 341 OWSumDS: 1643 OWSum2DS: 120295
Output for UDP Jitter (codec) Operations
The following is sample output from the show ip sla monitor collection-statistics command, where operation 10 is a UDP jitter (codec) operation. Table 106 describes the significant fields shown in the display.
Router# show ip sla monitor collection-statistics 10
Start Time Index: 12:57:45.931 UTC Wed Mar 12 2003
Number of successful operations: 60
Number of operations over threshold: 0
Number of failed operations due to a Disconnect: 0
Number of failed operations due to a Timeout: 0
Number of failed operations due to a Busy: 0
Number of failed operations due to a No Connection: 0
Number of failed operations due to an Internal Error: 0
Number of failed operations due to a Sequence Error: 0
Number of failed operations due to a Verify Error: 0
MinOfICPIF: 2 MaxOfICPIF: 20 MinOfMos: 3.20 MaxOfMos: 4.80
NumOfRTT: 600 RTTSum: 3789 RTTSum2: 138665
PacketLossSD: 0 PacketLossDS: 0
PacketOutOfSequence: 0 PacketMIA: 0 PacketLateArrival: 0
InternalError: 0 Busies: 0
MinOfPositivesSD: 1 MaxOfPositivesSD: 2
NumOfPositivesSD: 26 SumOfPositivesSD: 31 Sum2PositivesSD: 41
MinOfNegativesSD: 1 MaxOfNegativesSD: 4
NumOfNegativesSD: 56 SumOfNegativesSD: 73 Sum2NegativesSD: 133
MinOfPositivesDS: 1 MaxOfPositivesDS: 338
NumOfPositivesDS: 58 SumOfPositivesDS: 409 Sum2PositivesDS: 114347
MinOfNegativesDS: 1 MaxOfNegativesDS: 338
NumOfNegativesDS: 48 SumOfNegativesDS: 396 Sum2NegativesDS: 114332
Interarrival jitterout: 0 Interarrival jitterin: 0
OWMinSD: 2 OWMaxSD: 6 OWSumSD: 1273 OWSum2SD: 4021
OWMinDS: 2 OWMaxDS: 341 OWSumDS: 1643 OWSum2DS: 120295
Table 106 show ip sla monitor collection-statistics Field Descriptions
Field
|
Description
|
Voice Scores
|
Indicates that Voice over IP statistics appear on the following lines. Voice score data is computed when the operation type is configured as type jitter (codec).
|
ICPIF
|
The Calculated Planning Impairment Factor (ICPIF) value for the operation. The ICPIF value is computed by IP SLAs using the formula Icpif = Io + Iq + Idte + Idd + Ie - A, where
• The values for Io, Iq, and Idte are set to zero.
• The value Idd is computed based on the measured one-way delay.
• The value Ie is computed based on the measured packet loss.
• The value of A is specified by the user.
ICPIF values are expressed in a typical range of 5 (very low impairment) to 55 (very high impairment). ICPIF values numerically lower than 20 are generally considered "adequate."
Note This value is intended only for relative comparisons, and may not match ICPIF values generated using alternate methods.
|
MinOfICPIF
|
The lowest (minimum) ICPIF value computed for the collected statistics.
|
MaxOfICPIF
|
The highest (maximum) ICPIF value computed for the collected statistics.
|
Mos
|
The estimated Mean Opinion Score (Conversational Quality, Estimated) for the latest iteration of the operation. The MOS-CQE is computed by IP SLAs as a function of the ICPIF.
MOS values are expressed as a number from 1 (1.00) to 5 (5.00), with 5 being the highest level of quality, and 1 being the lowest level of quality. A MOS value of 0 (zero) indicates that MOS data could not be generated for the operation.
|
MinOfMos
|
The lowest (minimum) MOS value computed for the collected statistics.
|
MaxOfMos
|
The highest (maximum) ICPIF value computed for the collected statistics.
|
RTT Values
|
Indicates that round-trip-time statistics appear on the following lines.
|
NumOfRTT
|
The number of successful round-trips.
|
RTTSum
|
The sum of all successful round-trip values (in milliseconds).
|
RTTSum2
|
The sum of squares of those round-trip values (in milliseconds).
|
PacketLossSD
|
The number of packets lost from source to destination.
|
PacketLossDS
|
The number of packets lost from destination to source.
|
PacketOutOfSequence
|
The number of packets returned out of order.
|
PacketMIA
|
The number of packets lost where the direction (SD/DS) cannot be determined.
|
PacketLateArrival
|
The number of packets that arrived after the timeout.
|
InternalError
|
The number of times an operation could not be started due to other internal failures.
|
Busies
|
The number of times this operation could not be started because the previously scheduled run was not finished.
|
Jitter Values
|
Indicates that jitter statistics appear on the following lines. Jitter is interpacket delay variance.
|
NumOfJitterSamples
|
The number of jitter samples collected. This is the number of samples that are used to calculate the following jitter statistics.
|
MinOfPositivesSD MaxOfPositivesSD
|
The minimum and maximum positive jitter values from source to destination, in milliseconds.
|
NumOfPositivesSD
|
The number of jitter values from source to destination that are positive (that is, network latency increases for two consecutive test packets).
|
SumOfPositivesSD
|
The sum of those positive values (in milliseconds).
|
Sum2PositivesSD
|
The sum of squares of those positive values.
|
MinOfNegativesSD MaxOfNegativesSD
|
The minimum and maximum negative jitter values from source to destination. The absolute value is given.
|
NumOfNegativesSD
|
The number of jitter values from source to destination that are negative (that is, network latency decreases for two consecutive test packets).
|
SumOfNegativesSD
|
The sum of those values.
|
Sum2NegativesSD
|
The sum of the squares of those values.
|
Interarrival jitterout
|
The source-to-destination (SD) jitter value calculation, as defined in RFC 1889.
|
Interarrival jitterin
|
The destination-to-source (DS) jitter value calculation, as defined in RFC 1889.
|
One Way Values
|
Indicates that one-way measurement statistics appear on the following lines.
One Way (OW) values are the amount of time required for the packet to travel from the source router to the target router (SD) or from the target router to the source router (DS).
|
NumOfOW
|
Number of successful one-way time measurements.
|
OWMinSD
|
Minimum time (in milliseconds) from the source to the destination.
|
OWMaxSD
|
Maximum time (in milliseconds) from the source to the destination.
|
OWSumSD
|
Sum of the OWMinSD and OWMaxSD values.
|
OWSum2SD
|
Sum of the squares of the OWMinSD and OWMaxSD values.
|
Related Commands
Command
|
Description
|
show ip sla monitor configuration
|
Displays configuration values including all defaults for all IP SLAs operations or the specified operation.
|
show ip sla monitor distributions-statistics
|
Displays statistics distribution information (captured response times) for all IP SLAs operations or the specified operation.
|
show ip sla monitor totals-statistics
|
Displays the total statistical values (accumulation of error counts and completions) for all IP SLAs operations or the specified operation.
|
show ntp status
|
Displays the status of the NTP configuration on your system.
|
show ip sla monitor configuration
To display configuration values including all defaults for all Cisco IOS IP Service Level Agreements (SLAs) operations or a specified operation, use the show ip sla monitor configuration command in user EXEC or privileged EXEC mode.
show ip sla monitor configuration [operation]
Syntax Description
operation
|
(Optional) Number of the IP SLAs operation for which the details will be displayed.
|
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
12.3(14)T
|
This command was introduced. This command replaces the show rtr configuration command.
|
Examples
The following sections show sample output from the show ip sla monitor configuration command for different IP SLAs operations.
Output for ICMP Echo Operations
The following example shows output from the show ip sla monitor configuration command when the specified operation is an Internet Control Message Protocol (ICMP) echo operation:
Router# show ip sla monitor configuration
Complete Configuration Table (includes defaults)
Type of Operation to Perform: echo
Reaction and History Threshold (milliseconds): 5000
Operation Frequency (seconds): 60
Operation Timeout (milliseconds): 5000
Status of Entry (SNMP RowStatus): active
Protocol Type: ipIcmpEcho
Target Address: 172.16.1.176
Request Size (ARR data portion): 1
Response Size (ARR data portion): 1
Next Start Time: Start Time already passed
Entry Ageout (seconds): 3600
Number of Statistic Hours kept: 2
Number of Statistic Paths kept: 1
Number of Statistic Hops kept: 1
Number of Statistic Distribution Buckets kept: 1
Number of Statistic Distribution Intervals (milliseconds): 20
Number of History Lives kept: 0
Number of History Buckets kept: 50
Number of History Samples kept: 1
History Filter Type: none
Output for HTTP Operations
The following example shows output from the show ip sla monitor configuration command when the specified operation is a Hypertext Transfer Protocol (HTTP) operation:
Router# show ip sla monitor configuration
Complete Configuration Table (includes defaults)
Type of Operation to Perform:http
Reaction and History Threshold (milliseconds):5000
Operation Frequency (seconds):60
Operation Timeout (milliseconds):5000
Status of Entry (SNMP RowStatus):active
Request Size (ARR data portion):1
Response Size (ARR data portion):1
Loose Source Routing:disabled
Type of Service Parameters:0x0
Next Scheduled Start Time:Start Time already passed
Number of Statistic Hours kept:2
Number of Statistic Paths kept:1
Number of Statistic Hops kept:1
Number of Statistic Distribution Buckets kept:1
Statistic Distribution Interval (milliseconds):20
Number of History Lives kept:0
Number of History Buckets kept:15
Number of History Samples kept:1
Output for ICMP Path Jitter Operations
The following example shows output from the show ip sla monitor configuration command when the specified operation is an ICMP path jitter operation:
Router# show ip sla monitor configuration 1
Type of operation to perform: pathJitter
Destination address: 171.69.1.129
Interval (milliseconds): 20
Request size (ARR data portion): 1
Operation timeout (milliseconds): 5000
Type Of Service parameters: 0x0
Loose Source Routing: Disabled
Operation frequency (seconds): 60
Next Scheduled Start Time: Start Time already passed
Entry Ageout (seconds): never
Status of entry (SNMP RowStatus): Active
Output for UDP Jitter (codec) Operations
The following example shows output from the show ip sla monitor configuration command when the specified operation is a User Datagram Protocol (UDP) jitter (codec) operation:
Router# show ip sla monitor configuration
Type of operation to perform: jitter
Target address: 209.165.200.225
Operation timeout (milliseconds): 5000
Codec Number Of Packets: 1000
Codec Interval (milliseconds): 20
Type Of Service parameters: 0x0
Operation frequency (seconds): 60
Next Scheduled Start Time: Start Time already passed
Entry Ageout (seconds): never
Status of entry (SNMP RowStatus): Active
Threshold (milliseconds): 5000
Number of statistic hours kept: 2
Number of statistic distribution buckets kept: 1
Statistic distribution interval (milliseconds): 20
Related Commands
Command
|
Description
|
ip sla monitor
|
Begins configuration for an IP SLAs operation and enters IP SLA monitor configuration mode.
|
show ip sla monitor distributions-statistics
To display distribution statistics (captured response times) for all Cisco IOS IP Service Level Agreements (SLAs) operations or the specified operation, use the show ip sla monitor distributions-statistics command in user EXEC or privileged EXEC mode.
show ip sla monitor distributions-statistics [operation] [tabular | full]
Syntax Description
operation
|
(Optional) Number of the IP SLAs operation to display.
|
tabular
|
(Optional) Displays information in a column format, reducing the number of screens required to display the information. This is the default.
|
full
|
(Optional) Displays all information, using identifiers next to each displayed value.
|
Defaults
Statistics are displayed for the past two hours.
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
12.3(14)T
|
This command was introduced. This command replaces the show rtr distributions-statistics command.
|
Usage Guidelines
The distribution statistics consist of the following:
•
The sum of completion times (used to calculate the mean)
•
The sum of the completion times squared (used to calculate standard deviation)
•
The maximum and minimum completion time
•
The number of completed attempts
Note
This command does not support the IP SLAs ICMP path jitter operation.
This command shows information collected over the past two hours, unless you specify a different amount of time using the hours-of-statistics-kept command.
You can also use the show ip sla monitor collection-statistics and show ip sla monitor totals-statistics commands to display additional statistical information.
Examples
The following is sample output from the show ip sla monitor distributions-statistics command:
Router# show ip sla monitor distributions-statistics
StartT = Start Time of Entry (hundredths of seconds)
Dst = Time Distribution Index
Comps = Operations Completed
OvrTh = Operations Completed Over Thresholds
SumCmp = Sum of Completion Times (milliseconds)
SumCmp2L = Sum of Completion Times Squared Low 32 Bits (milliseconds)
SumCmp2H = Sum of Completion Times Squared High 32 Bits (milliseconds)
TMax = Completion Time Maximum (milliseconds)
TMin = Completion Time Minimum (milliseconds)
Entry StartT Pth Hop Dst Comps OvrTh SumCmp SumCmp2L SumCmp2H TMax TMin
1 17417068 1 1 1 2 0 128 8192 0 64 64
The fields shown in the display are self-explanatory.
Related Commands
Command
|
Description
|
show ip sla monitor collection-statistics
|
Displays statistical errors for all IP SLAs operations or the specified operation.
|
show ip sla monitor configuration
|
Displays configuration values including all defaults for all IP SLAs operations or the specified operation.
|
show ip sla monitor totals-statistics
|
Displays the total statistical values (accumulation of error counts and completions) for all IP SLAs operations or the specified operation.
|
show ip sla monitor enhanced-history collection-statistics
To display enhanced history statistics for all collected history buckets for the specified Cisco IOS IP Service Level Agreements (SLAs) operation, use the show ip sla monitor enhanced-history collection-statistics command in user EXEC or privileged EXEC mode.
show ip sla monitor enhanced-history collection-statistics [operation-number] [interval
seconds]
Syntax Description
operation-number
|
(Optional) Number of the operation for which enhanced history statistics is displayed.
|
interval seconds
|
(Optional) Displays enhanced history distribution statistics for only the specified aggregation interval.
• This keyword will not function for IP SLAs Service Level Monitoring (SLM) operations.
|
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
12.3(14)T
|
This command was introduced. This command replaces the show rtr enhanced-history collection-statistics command.
|
Usage Guidelines
This command displays data for each bucket of enhanced history data. Data is shown individually (one after the other).
The number of buckets and the collection interval is set using the enhanced-history command.
Note
For IP SLAs SLM operations, the enhanced history collection interval is fixed at 900 seconds and the number of buckets is fixed at 100. In other words, the collection interval and number of buckets cannot be modified with the enhanced-history command. These values are fixed so that complete SLM statistics can be provided.
You can also use the following commands to display additional statistics or history information, or to view the status of the operation:
•
show ip sla monitor enhanced-history distribution-statistics
•
show ip sla monitor statistics
Tip
If the letter n appears in your output, or not all fields are displayed, you should increase the screen width for your command line interface display (for example, using the width line configuration command or the terminal width EXEC mode command).
Examples
The output of this command will vary depending on the type of operation. The following examples show sample output for various IP SLAs operations:
Output for SLM Controller Operation
Router# show ip sla monitor configuration 1 | include Type
Type of operation to perform: slm controller
Router# show running-config | begin ip sla monitor
enhanced-history interval 900 buckets 100
ip sla monitor schedule 1 start-time now life forever
Router# show ip sla monitor enhanced-history collection-statistics 1
Aggregation Interval: 900
Aggregation start time 00:15:00.003 UTC Thur May 1 2003
Number of failed operations due to a Disconnect: 0
Number of failed operations due to a Timeout: 0
Number of failed operations due to a Busy: 0
Number of failed operations due to a No Connection: 0
Number of failed operations due to an Internal Error: 0
Number of failed operations due to a Sequence Error: 0
Number of failed operations due to a Verify Error: 0
Ds1StatRxLineStatus: 16385
Ds1StatRxBPVs: 0, Ds1StatRxCrcFrameErrors: 0
Ds1StatRxErrSecs: 0, Ds1StatRxSevereErrSecs: 0
Ds1StatRxUnavailSecs: 0, Ds1StatRxBurstyErrSecs: 0