Table Of Contents
show rtr configuration
show rtr distributions-statistics
show rtr enhanced-history collection-statistics
show rtr enhanced-history distribution-statistics
show rtr group schedule
show rtr history
show rtr operational-state
show rtr reaction-configuration
show rtr reaction-trigger
show rtr responder
show rtr totals-statistics
show running-config
show running-config map-class
show saa apm cache
show saa apm information
show saa apm operation
show saa apm results
show slot
show slot0:
show slot1:
show snmp
show snmp engineID
show snmp group
show snmp mib
show snmp mib bulkstat transfer
show snmp mib ifmib ifindex
show snmp mib notification-log
show snmp pending
show snmp sessions
show snmp user
show sntp
show stacks
show startup-config
show subsys
show tcp
show tcp brief
show tech-support
show time-range
show usb controllers
show usb device
show usb driver
show usb port
show usbtoken
show version
show warm-reboot
show whoami
show xsm status
show xsm xrd-list
showmon
slot (ERM policy)
snmp ifmib ifalias long
snmp mib bulkstat object-list
snmp mib bulkstat schema
snmp mib bulkstat transfer
snmp mib community-map
snmp mib notification-log default
snmp mib notification-log default disable
snmp mib notification-log globalageout
snmp mib notification-log globalsize
snmp mib persist
snmp mib target list
snmp trap link-status
snmp-server chassis-id
snmp-server community
snmp-server contact
snmp-server context
snmp-server enable informs
show rtr configuration
Note
Effective with Cisco IOS Release 12.3(14)T, the show rtr configuration command is replaced by the show ip sla monitor configuration command. See the show ip sla monitor configuration command for more information.
To display configuration values including all defaults for all Cisco IOS IP Service Level Agreements (IP SLAs) operations or the specified operation, use the show rtr configuration command in user EXEC or privileged EXEC mode.
show rtr 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
|
11.2
|
This command was introduced.
|
12.1
|
The tabular and full keywords were removed.
|
12.3(2)T
|
Output was added to show the VRF assignment name (if configured).
|
12.3(4)T
|
Output specific to the jitter (codec) operation type was added.
|
12.3(7)T
|
Output pertaining to reaction configuration (threshold values, reaction types) was removed from the output. Reaction configuration is now displayed using the show rtr reaction-configuration command.
|
12.3(8)T
|
Output was added to show the group schedule and the recurring schedule details for the IP SLAs operations.
|
12.2(25)S
|
This command was integrated into Cisco IOS Release 12.2(25)S. This integration includes the addition of output to show the group schedule and recurring schedule details for the IP SLAs operations.
|
12.3(14)T
|
This command was replaced by the show ip sla monitor configuration command.
|
12.2(27)SBC
|
This command was integrated into Cisco IOS Release 12.2(27)SBC. This integration includes the addition of output to show the group schedule and recurring schedule details for the IP SLAs operations.
|
Examples
The following is sample output from the show rtr configuration command for an IP SLAs Echo operation:
Router# show rtr 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
The following is sample output from the show rtr configuration command that verifies the configuration of an IP SLAs HTTP operation:
Router# show rtr 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
The following is sample output from the show rtr configuration command that shows output for a PathJitter operation associated with the VPN vrf1:
Router# show rtr 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
The following is sample output from the show rtr configuration command that includes output for the type jitter (codec) operation for VoIP metric monitoring:
Router# show rtr 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
The following is sample output from the show rtr configuration command for a recurring IP SLAs operation, with the recurring state as TRUE:
Router# show rtr configuration
Type of operation to perform: udpEcho
Target address: 10.2.31.121
Request size (ARR data portion): 16
Operation timeout (milliseconds): 5000
Type Of Service parameters: 0x0
Operation frequency (seconds): 60
Next Scheduled Start Time: Start Time already passed
Group Schedule Entry number :
Entry Ageout (seconds): never
Recurring (Starting everyday): TRUE
Status of entry (SNMP RowStatus): Active
Connection loss reaction enabled: No
Related Commands
Command
|
Description
|
show rtr application
|
Displays global information about the IP SLAs feature.
|
show rtr collection-statistics
|
Displays statistical errors for all IP SLAs operations or the specified operation.
|
show rtr distributions-statistics
|
Displays statistic distribution information (captured response times) for all IP SLAs operations or the specified operation.
|
show rtr group schedule
|
Displays the group schedule details of the specified IP SLAs operation.
|
show rtr history
|
Displays history collected for all IP SLAs operations or the specified operation.
|
show rtr operational-state
|
Displays the operational state of all IP SLAs operations or the specified operation.
|
show rtr reaction-trigger
|
Displays the reaction trigger information for all IP SLAs operations or the specified operation.
|
show rtr totals-statistics
|
Displays the total statistical values (accumulation of error counts and completions) for all IP SLAs operations or the specified operation.
|
show rtr distributions-statistics
Note
Effective with Cisco IOS Release 12.3(14)T, the show rtr distributions-statistics command is replaced by the show ip sla monitor distributions-statistics command. See the show ip sla monitor distributions-statistics command for more information.
To display statistic distribution information (captured response times) for all Cisco IOS IP Service Level Agreements (IP SLAs) operations or the specified operation, use the show rtr distributions-statistics command in EXEC mode.
show rtr 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
Tabular format for all operations is displayed.
Command Modes
EXEC
Command History
Release
|
Modification
|
11.2
|
This command was introduced.
|
12.3(14)T
|
This command was replaced by the show ip sla monitor distributions-statistics command.
|
Usage Guidelines
The distributions statistics consist of the following:
•
The sum of completion times (used to calculate the mean)
•
The sum of the completions 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.
You can also use the show rtr collection-statistics and show rtr totals-statistics commands to display additional statistical information.
Examples
The following is sample output from the show rtr distributions-statistics command in tabular format when the output is split over multiple lines
Router# show rtr 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
The following example shows the output as it appears on a single line:
Entry StartT Pth Hop Dst Comps OvrTh SumCmp SumCmp2L SumCmp2H TMax TMin
10 3581 1 1 1 0 0 0 0 0 0 0
Related Commands
Command
|
Description
|
show rtr collection-statistics
|
Displays statistical errors for all IP SLAs operations or the specified operation.
|
show rtr configuration
|
Displays configuration values including all defaults for all IP SLAs operations or the specified operation.
|
show rtr totals-statistics
|
Displays the total statistical values (accumulation of error counts and completions) for all IP SLAs operations or the specified operation.
|
show rtr enhanced-history collection-statistics
Note
Effective with Cisco IOS Release 12.3(14)T, the show rtr enhanced-history collection-statistics command is replaced by the show ip sla monitor enhanced-history collection-statistics command. See the show ip sla monitor enhanced-history collection-statistics command for more information.
To display enhanced history statistics for all collected history buckets for the specified Cisco IOS IP Service Level Agreements (IP SLAs) operation, use the show rtr enhanced-history distributio-statistics command in user EXEC or privileged EXEC mode.
show rtr enhanced-history collection-statistics [operation-number] [interval seconds]
Syntax Description
operation-number
|
(Optional) Displays enhanced history distribution statistics for only the specified operation.
|
interval seconds
|
(Optional) Displays enhanced history distribution statistics for only the specified aggregation interval.
• This keyword will not function for SLM operations.
|
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
12.2(15)T
|
This command was introduced.
|
12.3(14)T
|
This command was replaced by the show ip sla monitor enhanced-history collection-statistics command.
|
12.2(25)S
|
This command was integrated into Cisco IOS Release 12.2(25)S.
|
12.2(27)SBC
|
This command was integrated into Cisco IOS Release 12.2(27)SBC.
|
Usage Guidelines
This command displays data for each bucket of enhanced history data shown individually (one after the other).
The number of buckets and the collection interval is set using the enhanced-history interval seconds buckets number-of-buckets RTR configuration command.
For SLM operations, the enhanced history collection interval is set at 900 seconds and the number of buckets is set at 100. Because the enhanced history aggregationinterval is fixed at 900 seconds, the optional interval keyword available for this command will not work for SLM operations.
Examples
The output of this command will vary depending on the operation type. The following examples show output for various IP SLAs operations.
Output for SLM Controller Operation
Router# show rtr configuration 1 | include Type
Type of operation to perform: slm controller
Router# show running-config | begin rtr
enhanced-history interval 900 buckets 100
rtr schedule 1 start-time now life forever
Router# show rtr 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
Table 151 describes the significant fields shown in the display.
Table 151 show rtr enhanced-history Field Descriptions for SLM Controller Operations
Field
|
Description
|
Aggregation Interval:
|
The number of seconds the operation runs for each enhanced history bucket. For example, a value of 900 indicates that statistics were gathered for 15 minutes before the next bucket was created.
|
Bucket Index:
|
The number identifying the collection bucket. The number of buckets is set using the enhanced-history RTR configuration command.
|
Ds1StatRx
|
DS1 and E1 Received Statistics—The Ds1StatRx prefix is used for DS1 and E1 interfaces. DS1 and E1 interfaces are physical interfaces that run at a medium speed (for example, 1544 Kbps for DS1 interfaces). "Rx" indicates "received."
|
Ds1StatRxLineStatus:
|
Line Status—This variable indicates the Line Status of the interface. The dsx1LineStatus is a bit map represented as a sum, therefore, it can represent multiple conditions, like Excess Zeros and B8ZS detect, simultaneously. For example, the outOfFrame condition is implied by an outOfSignal condition.
Possible values include:
• 2 — yellowAlarm
• 8 — blueAlarm
• 32 — outOfFrame
• 64 — outOfSignal
• 8192 — excessZeros
• 16384 — b8zsDetect
|
Ds1StatRxBPVs:
|
Bi-Polar Violations—The total number of Bipolar Violations (BPVs) received on the interface.
|
Ds1StatRxCrcFrameErrors:
|
CRC or Frame Errors—he total number of Cyclic Redundancy Check (CRC) Errors (with ESF framing) or Frame Errors (with D4 framing) received on the interface.
|
Ds1StatRxErrSecs:
|
Errored Seconds—The total number of Errored Seconds that have occurred on the interface. This includes both Line Errored and Path Errored Seconds.
|
Ds1StatRxSevereErrSecs:
|
Severely Errored Seconds—The total number of Severely Errored Seconds that have occurred on the interface. This includes both Line Severely Errored Seconds and Path Severely Errored Seconds.
|
Ds1StatRxUnavailSecs:
|
Unavailable Seconds—The total number of Unavailable Seconds that have occurred on the interface.
|
Ds1StatRxBurstyErrSecs:
|
Type B Errored Seconds—The total number of Type B (Bursty) Errored Seconds that have occurred on the interface.
|
Ds1StatRxREBEs:
|
E1 Remote-End Block Errors—The total number of Remote-End Block Error (REBE) Events received on an E1 interface. (This data does not appear for DS1 interfaces.)
|
Output for SLM Frame Relay Operation
Router# show rtr configuration 2 | include Type
Type of operation to perform: Slm Frame-relay Interface
Router# show rtr ennhanced-history collection-statistics 2
Aggregation Interval: 900
Aggregation start time 00:15:00.003 UTC Mon Mar 1 1993
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
Tx Total Frames: 24 Rx Total Frames: 24
Tx Total Octets: 312 Rx Total Octets: 344
Tx FCSAlignErrors: 0 Rx FCSAlignErrors: 0
Tx Aborted Frames: 0 Rx Aborted Frames: 0
Tx Long Frames: 0 Rx Long Frames: 0
Tx Short Frames: 0 Rx Short Frames: 0
Tx MaxThroughput: 88 Rx MaxThroughput: 152
Tx MaxUtilization: 0 Rx MaxUtilization: 0
Tx MaxFramesSec: 1 Rx MaxFramesSec: 1
UnavailSecs: 0 Drop Events: 0
Tx OverFlowOctets: 0 Rx OverFlowOctets: 0
Tx Burst Percent1(sec): 238 Rx Burst Percent1(sec): 238
Tx Burst Percent2(sec): 0 Rx Burst Percent2(sec): 0
Tx Burst Percent3(sec): 0 Rx Burst Percent3(sec): 0
Tx Burst Percent4(sec): 0 Rx Burst Percent4(sec): 0
Tx Burst Percent5(sec): 0 Rx Burst Percent5(sec): 0
Table 152 describes the significant fields shown in the display. In the output "Tx" indicates "transmitted," "Rx" indicates "received."
Table 152 show rtr enhanced-history collection-statistics Field Descriptions for SLM Frame Relay Operations
Field
|
Description
|
LinkState
|
The Link State of the Frame Relay access channel being monitored. The link state is determined by the presence of LMI messages on the user and network side of the line.
The link state can take the following values:
• up(1)—Both sides of the access channel are up.
• networkDown(2)—The network side of the circuit has not responded to at least frDlcmiErrorThreshold Status Enquiry messages.
• userDown(3)—The user side of the access channel has not sent a Status Enquiry LMI message in FrConfigPollingTimeoutInterval (T391) seconds.
• down(4)—Both sides of the access channel have been down over some portion of the sampling interval.
• spoofNetworkUp(5)—The agent has been spoofing for the user over some portion of the sampling interval while the network side of the access channel has been up over the entire sampling interval.
• spoofNetworkDown(6)— The agent has been spoofing for the user over some portion of the sampling interval while the network side of the access channel has been down over the entire sampling interval.
|
Tx Total Frames:
|
The total number of frames (including errored frames) transmitted by the interface. Aborted frames are not included in this count.
(MIB variable: FrStatTxFrames)
|
Rx Total Frames:
|
The total number of non-errored frames received by the interface. Aborted frames are not included.
(MIB variable: FrStatRxFrames)
|
Tx Total Octets:
|
The total number of octets transmitted in frames from the interface (excluding framing bits but including FCS octets). Octets in errored and aborted frames are included in this count.
(MIB variable: FrStatTxOctets)
|
Rx Total Octets:
|
The total number of octets received by the interface in non-errored frames (excluding framing bits but including FCS octets). Octets in errored and aborted frames are included in this count.
(MIB variable: FrStatRxOctets)
|
Tx FCSAlignErrors:
|
The total number of frames transmitted by the interface that had a length (excluding framing bits, but including FCS octets) of at least (5) octets, but had either a bad Frame Check Sequence (FCS) with an integral number of octets (FCS Error) or a bad FCS with a non-integral number of octets (Alignment Error). Agents that cannot count this transmit-side object will return a value of zero.
(MIB variable: FrStatTxFcsAlignErrors)
|
Rx FCSAlignErrors:
|
The total number of frames received by the interface that had a length (excluding framing bits, but including FCS octets) of at least (5) octets, but had either a bad Frame Check Sequence (FCS) with an integral number of octets (FCS Error) or a bad FCS with a non-integral number of octets (Alignment Error).
(MIB variable: FrStatRxFcsAlignErrors)
|
Tx Burst Percent1(sec):
|
The number of one second intervals where the transmitted throughput (t) is greater than or equal to zero and less than or equal to BurstLimit 1 (0 <= t <= BurstLimit1). BurstLimit1 is defined as a percentage of the CircuitBurstNominalRate in the RTTMON MIB.
Note: The burst parameters used in this definition are defined in the CircuitConfigTable of the RTTMON MIB.
|
show rtr enhanced-history distribution-statistics
Note
Effective with Cisco IOS Release 12.3(14)T, the show rtr enhanced-history distribution-statistics command is replaced by the show ip sla monitor enhanced-history distribution-statistics command. See the show ip sla monitor enhanced-history distribution-statistics command for more information.
To display enhanced history distribution statistics for Cisco IOS IP Service Level Agreements (IP SLAs) operations in tabular format, use the show rtr enhanced-history distribution-statistics command in user EXEC or privileged EXEC mode.
show rtr enhanced-history distribution-statistics [operation-number [interval seconds]]
Syntax Description
operation-number
|
(Optional) Displays enhanced history distribution statistics for only the specified operation.
|
interval seconds
|
(Optional) Displays enhanced history distribution statistics for only the specified aggregation interval for only the specified operation.
• The valid range is from 1 to 3,600 seconds (1 hour). The default is 900 seconds.
• This keyword will not function for SLM operations.
|
Command Modes
User Exec
Privileged Exec
Command History
Release
|
Modification
|
12.3(1)
|
This command was introduced.
|
12.3(14)T
|
This command was replaced by the show ip sla monitor enhanced-history distribution-statistics command.
|
12.2(25)S
|
This command was integrated into Cisco IOS Release 12.2(25)S.
|
12.2(27)SBC
|
This command was integrated into Cisco IOS Release 12.2(27)SBC.
|
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 times
•
The number of completed attempts
You can also use the following commands to display additional statistics or history information, or to view the status of the operation:
•
show rtr enhanced-history collection-statistics
•
show rtr enhanced-history totals-statistics
Tip
If the character `n' appears in your output, or not all fields are displayed, you should increase the screen width for your CLI display (for example, using the width line configuration command or the terminal width Exec mode command).
Examples
The following is sample output from the show rtr enhanced-history distribution-statistics command for an SLM Frame Relay Circuit operation. The fields are defined at the beginning of the output for the command. RTT means round-trip-time.
Router# show ip sla monitor configuration 3 | include Type
Type of operation to perform: Slm Frame-relay Pvc
Router# show ip sla monitor enhanced-history distribution-statistics 3
Point by point Enhanced History
Int = Aggregation Interval (seconds)
StartT = Aggregation Start Time
Comps = Operations completed
OvrTh = Operations completed over thresholds
SumCmp = Sum of RTT (milliseconds)
SumCmp2L = Sum of RTT squared low 32 bits (milliseconds)
SumCmp2H = Sum of RTT squared high 32 bits (milliseconds)
TMax = RTT maximum (milliseconds)
TMin = RTT minimum (milliseconds)
Entry Int BucI StartT Pth Hop Comps OvrTh SumCmp SumCmp2L SumCmp2H TMax TMin
3 900 1 257850000 1 1 3 0 43 617 0 15 14
3 900 2 258750002 1 1 3 0 45 677 0 16 14
3 900 3 259650000 1 1 3 0 44 646 0 15 14
3 900 4 260550002 1 1 3 0 42 594 0 15 12
3 900 5 261450003 1 1 3 0 42 590 0 15 13
3 900 6 262350001 1 1 3 0 46 706 0 16 15
3 900 7 263250003 1 1 3 0 46 708 0 16 14
The time elapsed between BucketIndex 1 (started at 257,850,000) and BucketIndex 2 (started at 258,750,002) in this example is 900,002 milliseconds, or 900 seconds.
Table 153 describes the significant fields shown in the display.
Table 153 show ip sla monitor enhanced-history distribution-statistics Field Descriptions
Field
|
Description
|
Entry
|
The operation ID number you specified for the IP SLAs operation.
|
Int
|
Aggregation interval—The configured statistical distribution buckets interval, in seconds. For example, a value of 900 for Int means that statistics are gathered for 900 seconds per bucket.
|
BucI
|
Bucket index number—A number uniquely identifying the statistical distribution (aggregation) bucket.
The number of history buckets to be kept is configured using the buckets-of-history-kept command.
A bucket will gather statistics for the specified interval of time (aggregation interval), after which a new statistics bucket is created.
If a number-of-buckets-kept value is configured, the interval for the last bucket is infinity (until the end of the operation).
Buckets are not applicable to HTTP and UDP jitter monitoring operations.
This field is equivalant to the rttMonStatsCaptureDistIndex object in the Cisco RTTMON MIB.
|
StartT
|
Aggregation start time—Start time for the aggregation interval (per Bucket Index).
Shows the start time as the number of milliseconds since the router started; in other words, the time stamp is the number of milliseconds since the last system bootup.
|
Pth
|
Path index number—An identifier for a set of different paths to the target destination that have been discovered. For example, if the first operation iteration finds the path h1, h2, h3, h4, then this path is labeled as 1. If, on a later iteration, a new path is discovered, (such as h1, h2, h5, h6, h4) then this new path will be identified as 2, and so on.
Data collection per path is available only for ICMP path echo operations ("pathEcho probes"). For all other operations, a value of 1 will always appear.
Data collection per path is configured using the paths-of-statistics-kept number command when configuring the operation.
|
Hop
|
Hop Index Number—Statistics data per hop. A hop is data transmission between two points in a path (for example, from device h2 to device h3).
Data collection per hop is available only for ICMP path echo operations ("pathEcho probes"). For all other operations, a value of "1" will always appear.
Data collection per hop is configured using the hops-of-statistics-kept number command when configuring the operation.
This field is equivalent to the rrttMonStatsCaptureHopIndex object in the Cisco RTTMON MIB.
|
Comps
|
Completions—The number of round-trip time operations that have completed without an error and without timing out, per bucket index.
This object has the special behavior as defined by the ROLLOVER NOTE in the DESCRIPTION of the Cisco Rttmon MIB object.
|
SumCmp
|
Sum of completed operation times (1)—The total of all round-trip time values for all succesful operations in the row, in milliseconds.
|
SumCmp2L
|
Sum of the squares of completed operation times (2), Low-Order—The sum of the square roots of round-trip times for operations that were successfully measured, in milliseconds; displays the low-order 32 bits of the value only.
• 32 low-order bits and 32 high-order bits are ordered in unsigned 64-bit integers (Int64) as follows:
-------------------------------------------------
| High-order 32 bits | Low-order 32 bits |
-------------------------------------------------
• The "SumCmp2" values are split into "high-order" and "low-order" numbers because of limitations of Simple Network Management Protocol (SNMP). The maximum value allowed for an SNMP object is 4,294,967,295 (the Gauge32 limit).
If the sum of the square roots for your operation exceeds this value, then the "high-order" value will be utilized. (For example, the number 4,294,967,296 would have all low-order bits as 0, and the right-most high-order bit would be 1).
• The low-order value (SumCmp2L) appears first in the output because in most cases, the value will be less than 4,294,967,295, which means that the value of SumCmp2H will appear as zero.
|
SumCmp2H
|
Sum of the squares of completed operation times (2), High-Order—The high-order 32 bits of the accumulated squares of completion times (in milliseconds) of operations that completed successfully.
|
TMax
|
Round-trip time, maximum—The highest recorded round-trip time, in milliseconds, per aggregation interval.
|
TMin
|
Round-trip time, minimum—The lowest recorded round-trip time, in milliseconds, per aggregation interval.
|
Related Commands
Command
|
Description
|
rtr
|
Begins configuration for an IP SLAs operation and enters RTR configuration mode.
|
show rtr enhanced-history collection-statistics
|
Displays data for all collected history buckets for the specified IP SLAs operation, with data for each bucket shown individually.
|
show rtr group schedule
Note
Effective with Cisco IOS Release 12.3(14)T, the show rtr group schedule command is replaced by the show ip sla monitor group schedule command. See the show ip sla monitor group schedule command for more information.
To display the group schedule details of Cisco IOS IP Service Level Agreements (IP SLAs) operations, use the show rtr group schedule command in user EXEC or privileged EXEC mode.
show rtr group schedule [group-operation-number]
Syntax Description
group-operation-number
|
(Optional) Number of the IP SLAs group operation to display.
|
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
12.3(8)T
|
This command was introduced.
|
12.3(14)T
|
This command was replaced by the show ip sla monitor group schedule command.
|
12.2(25)S
|
This command was integrated into Cisco IOS Release 12.2(25)S.
|
12.2(27)SBC
|
This command was integrated into Cisco IOS Release 12.2(27)SBC.
|
Examples
The following is sample output from the show rtr group schedule command that shows information about group (multiple) scheduling. The last line in the example indicates that the IP SLAs operations are multiple scheduled (TRUE):
Router# show rtr group schedule
Multi-Scheduling Configuration:
Probes to be scheduled: 2,3,4,9-30,89
Group operation frequency: 30
The following is sample output from the show rtr group schedule command that shows information about group (multiple) scheduling, with the frequency value the same as the schedule-period value, the life value as 3600 seconds, and the ageout value as never:
Router# show rtr group schedule
Probes to be scheduled: 3,4,6-10
Total number of probes: 7
Group operation frequency: Equals schedule period
Status of entry (SNMP RowStatus): Active
Next Scheduled Start Time: Start Time already passed
Entry Ageout (seconds): never
Table 154 describes the significant fields shown in the displays.
Table 154 show rtr group schedule Field Descriptions
Field
|
Description
|
Group Entry Number
|
The operation group number specified for IP SLAs multiple operations scheduling.
|
Probes to be scheduled
|
The operations numbers specified in the operation group 1.
|
Scheduled period
|
The time in seconds you mentioned while scheduling the operation.
|
Group operation frequency
|
The frequency at which each operation is started.
|
Multi-scheduled
|
The value TRUE shows that group scheduling is active.
|
Related Commands
Command
|
Description
|
show rtr configuration
|
Displays the scheduling details.
|
show running configuration
|
Displays the configuration details which includes the IP SLAs multiple operations scheduling information.
|
show rtr history
Note
Effective with Cisco IOS Release 12.3(14)T, the show rtr history command is replaced by the show ip sla monitor history command. See the show ip sla monitor history command for more information.
To display history collected for all Cisco IOS IP Service Level Agreements (IP SLAs) operations or for a specified operation, use the show rtr history command in EXEC mode.
show rtr history [operation-number] [tabular | full]
Syntax Description
operation-number
|
(Optional) Displays history for only the specified operation.
|
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
Tabular format history for all operations is displayed.
Command Modes
EXEC
Command History
Release
|
Modification
|
11.2
|
This command was introduced.
|
12.3(14)T
|
This command was replaced by the show ip sla monitor history command.
|
Usage Guidelines
Table 155 lists the Response Return values used in the output of the show rtr history command. If the default (tabular) format is used, the Response Return description is displayed as a code in the Sense column. If the full format is used, the Response Return is displayed as indicated in the Description column.
Table 155 Response Return (Sense Column) Codes
Code
|
Description
|
1
|
Okay.
|
2
|
Disconnected.
|
3
|
Over threshold.
|
4
|
Timeout.
|
5
|
Busy.
|
6
|
Not connected.
|
7
|
Dropped.
|
8
|
Sequence error.
|
9
|
Verify error.
|
10
|
Application specific.
|
Examples
The following is sample output from the show rtr history command in tabular format:
SampleT = Sample Start Time
CompT = Completion Time (milliseconds)
Sense = Response Return Code
Line 2 has the Target Address
Entry LifeI BucketI SampleI SampleT CompT Sense
Related Commands
Command
|
Description
|
show rtr configuration
|
Displays configuration values including all defaults for all IP SLAs operations or the specified operation.
|
show rtr operational-state
Note
Effective with Cisco IOS Release 12.3(14)T, the show rtr operational-state command is replaced by the show ip sla monitor statistics command. See the show ip sla monitor statistics command for more information.
To display the operational state of all Cisco IOS IP Service Level Agreements (IP SLAs) operations or a specified operation, use the show rtr operational-state command in EXEC mode.
show rtr operational-state [operation-number]
Syntax Description
operation-number
|
(Optional) ID number of the IP SLAs operation to display.
|
Defaults
Displays output for all running IP SLAs operations.
Command Modes
EXEC
Command History
Release
|
Modification
|
11.2
|
This command was introduced.
|
12.0(5)T
|
Output for the Jitter operation type was added.
|
12.1
|
The tabular and full keywords were removed.
|
12.2(8)T
|
Output for "NumOfJitterSamples" was added (CSCdv30022).
|
12.2(8)S
|
Output for "NumOfJitterSamples" was added (CSCdv30022).
|
12.3(4)T
|
Output (MOS and ICPIF scores) for the Jitter (codec) operation type was added.
|
12.3(7)T
|
Decimal granularity for MOS scores was added.
|
12.3(14)T
|
This command was replaced by the show ip sla monitor statistics command.
|
Usage Guidelines
Use the show rtr operational-state command to display the current state of IP SLAs operations, including how much life the operation has left, whether the operation is active, and the completion time. The output will also include the monitoring data returned for the last (most recently completed) operation.
Examples
The following example shows basic sample output from the show rtr operational-state command:
Router# show rtr operational-state
Current Operational State
Modification Time: *22:15:43.000 UTC Sun Feb 11 2001
Last Time this Entry was Reset: Never
Number of Octets in use by this Entry: 1332
Number of Operations Attempted: 2
Current Seconds Left in Life: 3511
Operational State of Entry: active
Latest Completion Time (milliseconds): 544
Latest Operation Start Time: *22:16:43.000 UTC Sun Feb 11 2001
Latest Sense Description: 200 OK
HTTP Transaction RTT: 504
The following example shows sample output from the show rtr operational-state command when the specified operation is a Jitter (codec) operation:
Router# show rtr operational-state 1
Modification time: 13:18:38.012 PST Mon Jun 24 2002
Number of Octets Used by this Entry: 10392
Number of operations attempted: 2
Number of operations skipped: 0
Current seconds left in Life: Forever
Operational state of entry: Active
Last time this entry was reset: Never
Connection loss occurred: FALSE
Over thresholds occurred: FALSE
Latest RTT (milliseconds): 2
Latest operation start time: *13:18:42.896 PST Mon Jun 24 2002
Latest operation return code: OK
ICPIF Value: 0 MOS score: 0
NumOfRTT: 61 RTTAvg: 2 RTTMin: 2 RTTMax: 3
PacketLossSD: 0 PacketLossDS: 0
PacketOutOfSequence: 0 PacketMIA: 0 PacketLateArrival: 0
InternalError: 0 Busies: 0 PacketSkipped: 39 <<<<<<==========
MinOfPositivesSD: 1 MaxOfPositivesSD: 1
NumOfPositivesSD: 1 SumOfPositivesSD: 1 Sum2PositivesSD: 1
MinOfNegativesSD: 1 MaxOfNegativesSD: 1
NumOfNegativesSD: 1 SumOfNegativesSD: 1 Sum2NegativesSD: 1
MinOfPositivesDS: 0 MaxOfPositivesDS: 0
NumOfPositivesDS: 0 SumOfPositivesDS: 0 Sum2PositivesDS: 0
MinOfNegativesDS: 0 MaxOfNegativesDS: 0
NumOfNegativesDS: 0 SumOfNegativesDS: 0 Sum2NegativesDS: 0
Interarrival jitterout: 0 Interarrival jitterin: 0
OWMinSD: 0 OWMaxSD: 0 OWSumSD: 0 OWSum2SD: 0
OWMinDS: 0 OWMaxDS: 0 OWSumDS: 0 OWSum2DS: 0
The values shown indicate the values for the last IP SLAs operation. RTT stands for Round-Trip-Time. SD stands for Source-to-Destination. DS stands for Destination-to-Source. OW stands for One Way. The * symbol in front of the time stamps indicates the time is synchronized using NTP or SNTP. Table 156 describes the significant fields shown in this output.
Table 156 show rtr operational-state 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 latest iteration of 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,
• and 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 less 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.
|
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.
|
RTT Values:
|
Indicates that Round-Trip-Time statistics appear on the following lines.
|
NumOfRTT
|
The number of successful round trips.
|
RTTSum
|
The sum of those round trip values (in milliseconds).
|
RTTSum2
|
The sum of squares of those round trip values (in milliseconds).
|
Packet Loss Values:
|
Indicates that Packet Loss statistics appear on the following lines.
|
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 or DS) cannot be determined (MIA: "missing in action").
|
PacketLateArrival
|
The number of packets that arrived after the timeout.
|
PacketSkipped
|
The number of packets that are not sent during the IP SLAs jitter operation.
|
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 operation statistics appear on the following lines.
Jitter is inter-packet delay variance.
|
NumOfJitterSamples:
|
The number of jitter samples collected. This is the number of samples that are used to calculate the following jitter statitstics.
|
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 (i.e., 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 (i.e., 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 souce (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 it took 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 from the source to the destination.
|
OWMaxSD
|
Maximum time 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 rtr configuration
|
Displays configuration values including all defaults for all IP SLAs operations or the specified operation.
|
show rtr reaction-configuration
Note
Effective with Cisco IOS Release 12.3(14)T, the show rtr reaction-configuration command is replaced by the show ip sla monitor reaction-configuration command. See the show ip sla monitor reaction-configuration command for more information.
To display the configured reaction characteristics for all Cisco IOS IP Service Level Agreements (IP SLAs) operations or a specified operation, use the show rtr reaction-configuration command in EXEC mode.
show rtr reaction-configuration [operation-number]
Syntax Description
operation-number
|
(Optional) Displays the reaction configuration for only the specified IP SLAs operation.
|
Defaults
Displays reaction configuration for all IP SLAs operations.
Command Modes
EXEC
Command History
Release
|
Modification
|
12.3(7)T
|
This command was introduced.
|
12.3(14)T
|
This command was replaced by the show ip sla monitor reaction-configuration command.
|
12.2(25)S
|
This command was integrated into Cisco IOS Release 12.2(25)S.
|
12.2(27)SBC
|
This command was integrated into Cisco IOS Release 12.2(27)SBC.
|
Usage Guidelines
Use the show rtr reaction-configuration command to check the current configuration of reaction conditions for IP SLAs operations. Reaction conditions for IP SLAs operations are configured using the rtr reaction-configuration global configuration mode command.
Examples
In the following example, multiple monitored elements (indicated by the Reaction: value) are configured for a single IP SLAs operation:
Router# show rtr reaction-configuration
Rising (milliseconds): 5000
Falling (milliseconds): 3000
Falling (milliseconds): 3
Threshold type: immediate
Falling (milliseconds): 3
Threshold type: immediate
Threshold Falling (milliseconds): 3
Table 157 describes the significant fields shown in this output.
Table 157 show rtr reaction-configuration Field Descriptions
Field
|
Description
|
|
The configured monitored element for IP SLAs reactions.
Corresponds to the react { connectionLoss | jitterAvg | jitterDSAvg | jitterSDAvg | mos | PacketLossDS | PacketLossSD | rtt | timeout | verifyError } syntax in the rtr reaction-configuration command.
|
|
The configured threshold type.
Corresponds to the threshold-type { never | immediate | consecutive | xofy | average } syntax in the rtr reaction-configuration command.
|
|
The upper-threshold value, as configured by the threshold-value upper-threshold lower-threshold syntax in the rtr reaction-configuration command.
|
Threshold Falling
(milliseconds):
|
The lower-threshold value, as configured by the threshold-value upper-threshold lower-threshold syntax in the rtr reaction-configuration command.
|
|
The x-value in the xofy threshold-type, or the number-of-measurements value for average threshold-type.
|
|
The y-value in the xofy threshold-type.
|
|
The reaction to be performed when the violation conditions are met, as configured by the action-type { none | trapOnly | triggerOnly | trapAndTrigger } syntax in the rtr reaction-configuration command.
|
show rtr reaction-trigger
Note
Effective with Cisco IOS Release 12.3(14)T, the show rtr reaction-trigger command is replaced by the show ip sla monitor reaction-trigger command. See the show ip sla monitor reaction-trigger command for more information.
To display the reaction trigger information for all Cisco IOS IP Service Level Agreements (IP SLAs) operations or the specified operation, use the show rtr reaction-trigger command in EXEC mode.
show rtr reaction-trigger [operation-number]
Syntax Description
operation-number
|
(Optional) Number of the IP SLAs operation to display.
|
Defaults
None.
Command Modes
EXEC
Command History
Release
|
Modification
|
11.2
|
This command was introduced.
|
12.3(14)T
|
This command was replaced by the show ip sla monitor reaction-trigger command.
|
Usage Guidelines
Use the show rtr reaction-trigger command to display the configuration status and operational state of target operations that will be triggered as defined with the rtr reaction-configuration global command.
Examples
The following is sample output from the show rtr reaction-trigger command:
Router# show rtr reaction-trigger 1
Status of Entry (SNMP RowStatus): active
Operational State: pending
Related Commands
Command
|
Description
|
show rtr configuration
|
Displays configuration values including all defaults for all IP SLAs operations or the specified operation.
|
show rtr responder
Note
Effective with Cisco IOS Release 12.3(14)T, the show rtr responder command is replaced by the show ip sla monitor responder command. See the show ip sla monitor responder command for more information.
To display Cisco IOS IP Service Level Agreements (IP SLAs) Responder information, use the show rtr responder command in EXEC mode.
show rtr responder
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Release
|
Modification
|
12.0(3)T
|
This command was introduced.
|
12.3(14)T
|
This command was replaced by the show ip sla monitor responder command.
|
Usage Guidelines
Use the show rtr responder command to display information about recent sources of IP SLAs control messages, such as who has sent recent control messages and who has sent invalid control messages.
Examples
The following is sample output from the show rtr responder command:
Router# show rtr responder
RTR Responder is: Enabled
Number of control message received: 19 Number of errors: 1
4.0.0.1 [19:11:49.035 UTC Sat Dec 2 1995]
4.0.0.1 [19:10:49.023 UTC Sat Dec 2 1995]
4.0.0.1 [19:09:48.707 UTC Sat Dec 2 1995]
4.0.0.1 [19:08:48.687 UTC Sat Dec 2 1995]
4.0.0.1 [19:07:48.671 UTC Sat Dec 2 1995]
4.0.0.1 [19:10:49.023 UTC Sat Dec 2 1995] RTT_AUTH_FAIL
Related Commands
Command
|
Description
|
show rtr configuration
|
Displays configuration values for IP SLAs operations.
|
show rtr totals-statistics
Note
Effective with Cisco IOS Release 12.3(14)T, the show rtr totals-statistics command is replaced by the show ip sla monitor totals-statistics command. See the show ip sla monitor totals-statistics command for more information.
To display the total statistical values (accumulation of error counts and completions) for all Cisco IOS IP Service Level Agreements (IP SLAs) operations or the specified operation, use the show rtr totals-statistics command in EXEC mode.
show rtr totals-statistics [number] [tabular | full]
Syntax Description
number
|
(Optional) Number of the IP SLAs operation to display.
|
tabular
|
(Optional) Display information in a column format reducing the number of screens required to display the information.
|
full
|
(Optional) Display all information using identifiers next to each displayed value. This is the default.
|
Defaults
Full format for all operations
Command Modes
EXEC
Command History
Release
|
Modification
|
11.2
|
This command was introduced.
|
12.3(14)T
|
This command was replaced by the show ip sla monitor total-statistics command.
|
Usage Guidelines
The total statistics consist of the following items:
•
The operation number
•
The start time of the current hour of statistics
•
The age of the current hour of statistics
•
The number of attempted operations
You can also use the show rtr distributions-statistics and show rtr collection-statistics commands to display additional statistical information.
Examples
The following is sample output from the show rtr totals-statistics command in full format:
Router# show rtr totals-statistics
Start Time Index: *17:15:41.000 UTC Thu May 16 1996
Age of Statistics Entry (hundredths of seconds): 48252
Number of Initiations: 10
Related Commands
Command
|
Description
|
show rtr collection-statistics
|
Displays statistical errors for all IP SLAs operations or the specified operation.
|
show rtr configuration
|
Displays configuration values including all defaults for all IP SLAs operations or the specified operation.
|
show rtr distributions-statistics
|
Displays statistic distribution information (captured response times) for all IP SLAs operations or the specified operation.
|
show running-config
To display the contents of the currently running configuration file or the configuration for a specific class map, interface, map class, policy map, or virtual circuit (VC) class, use the show running-config command in privileged EXEC mode.
show running-config [options]
Syntax Description
options
|
(Optional) One of the following options can be entered with the command:
• brief—Displays the configuration without certification data.
• class-map name—Displays class map information. The linenum keyword can be used with the class-map name option.
• full—Displays the full configuration.
• interface type number—Displays interface-specific configuration information. If you use the interface keyword, you must specify the interface type and the interface number (for example, interface ethernet 0). Common interfaces include async, ethernet, fastEthernet, group-async, loopback, null, serial, and virtual-template. Use the show run interface ? command to determine the interfaces available on your system.
• linenum—Displays line numbers in the output. The brief or full keyword can be used with the linenum keyword.
• map-class—Displays map class information. This option is described separately; see the show running-config map-class command page.
• policy-map name—Displays policy map information. The linenum keyword can be used with the policy-map name option.
• vc-class name—Displays VC class information (display available only on limited routers such as the Cisco 7500 series). The linenum keyword can be used with the vc-class name option.
• |—Allows addition of output modifiers and is available with all the keywords for this command.
|
Defaults
The show running-config command without any arguments or keywords displays the entire contents of the running configuration file.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
11.0
|
This command was introduced.
|
12.0
|
This command was replaced by the more system:running-config command.
|
12.0(1)T
|
The output modifier (|) was added.
|
12.2(4)T
|
The linenum keyword was added.
|
Usage Guidelines
The show running-config command is technically a command alias of the more system:running-config command. Although more commands are recommended (due to their uniform structure across platforms and their expandable syntax), the show running-config command remains enabled to accommodate its widespread use, and to allow typing shortcuts such as show run.
The show running-config interface command is useful when there are multiple interfaces and you want to look at the configuration of a specific interface.
The linenum keyword causes line numbers to be displayed in the output. This option is useful for identifying a particular portion of a very large configuration.
Examples
The following example shows the configuration for serial interface 1:
Router# show running-config interface serial 1
Building configuration...
The following example shows the configuration for Ethernet interface 0/0. Line numbers are displayed in the output.
Router# show running-config interface ethernet 0/0 linenum
Building configuration...
Current configuration : 104 bytes
2 : interface Ethernet0/0
3 : ip address 10.4.2.63 255.255.255.0
The following example shows how to set line numbers in the command output, and then use the output modifier to start the display at line 10:
Router# show running-config linenum | begin 10
14 : enable password #####
17 : firmware location bootflash:mica-modem-pw.2.7.1.0.bin
20 : resource-pool disable
24 : ip domain name cisco.com
25 : ip name-server 172.16.11.48
26 : ip name-server 172.16.2.133
29 : isdn switch-type primary-5ess
Related Commands
Command
|
Description
|
boot config
|
Specifies the device and filename of the configuration file from which the router configures itself during initialization (startup).
|
configure terminal
|
Enters global configuration mode.
|
copy running-config startup-config
|
Copies the running configuration to the startup configuration. (Command alias for the copy system:running-config nvram:startup-config command.)
|
show startup-config
|
Displays the contents of NVRAM (if present and valid) or displays the configuration file pointed to by the CONFIG_FILE environment variable. (Command alias for the more:nvram startup-config command.)
|
show running-config map-class
To display only map-class configuration information from the running configuration file, use the show running-config map-class command in privileged EXEC mode.
show running-config map-class [atm [map-class-name] | dialer [map-class-name] | frame-relay
[map-class-name]] [linenum]
Syntax Description
atm
|
(Optional) Displays only ATM map-class configuration lines.
|
dialer
|
(Optional) Displays only dialer map-class configuration lines.
|
frame-relay
|
(Optional) Displays only Frame Relay map-class configuration lines.
|
map-class-name
|
(Optional) Displays only configuration lines for the specified map-class.
|
linenum
|
(Optional) Displays line numbers in the output.
|
Defaults
Displays all map-class configuration in the running configuration file.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.1
|
The map-class extension to the show running-config command was introduced to show only lines pertaining to dialer or Frame Relay map classes.
|
12.1(2)T
|
The atm, dialer, and frame-relay keywords and map-class-name argument were introduced.
|
12.2(4)T
|
The linenum keyword was added.
|
Usage Guidelines
Use the show running-config map-class command to display the following information from the running configuration file:
•
All map classes configured on the router.
•
Map classes configured specifically for ATM, Frame Relay, or dialer.
•
A specific ATM, Frame Relay, or dialer map class.
Use the linenum keyword to display line numbers in the output. This option is useful for identifying a particular portion of a very large configuration.
Examples
All Map Classes Configured on the Router Example
The following example displays all map classes configured on the router:
Router# show running-config map-class
Building configuration...
map-class frame-relay cir60
frame-relay adaptive-shaping becn
map-class frame-relay cir70
no frame-relay adaptive-shaping
frame-relay priority-group 2
All Frame Relay Map Classes Example
The following example displays all Frame Relay map classes on the router:
Router# show running-config map-class frame-relay
Building configuration...
map-class frame-relay cir60
frame-relay adaptive-shaping becn
map-class frame-relay cir70
no frame-relay adaptive-shaping
frame-relay priority-group 2
A Specific Map Class and Display of Line Numbers Example
The following example displays a specific map class called class1. Line numbers are displayed in the output.
Router# show running-config map-class frame-relay class1 linenum
Building configuration...
2 : map-class frame-relay boy
3 : no frame-relay adaptive-shaping
Related Commands
Command
|
Description
|
map-class atm
|
Specifies the ATM map class for an SVC.
|
map-class dialer
|
Defines a class of shared configuration parameters associated with the dialer map command for outgoing calls from an ISDN interface and for PPP callback.
|
map-class frame-relay
|
Specifies a map class to define QoS values for a Frame Relay VC.
|
more system:running-config
|
Displays contents of the currently running configuration file (equivalent to the show running-config command.)
|
show saa apm cache
Note
Effective with Cisco IOS Release 12.3(14)T, the show saa apm cache command is replaced by the show ip sla monitor apm cache command. See the show ip sla monitor apm cache command for more information.
To display the amount of memory available in the Cisco IOS IP Service Level Agreements (IP SLAs) Application Performance Monitor (APM) cache and information about the files stored in the cache, use the show saa apm cache command in EXEC mode.
show saa apm cache
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Release
|
Modification
|
12.2(2)T
|
This command was introduced.
|
12.3(14)T
|
This command was replaced by the show ip sla monitor 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 saa apm cache command:
Router# show saa 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 158 describes the significant fields shown in the display.
Table 158 show saa apm cache Field Descriptions
Field
|
Description
|
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
|
Size
|
Size of the file, in bytes.
|
Ref
|
Ref-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.
|
SBit
|
"Sticky bit" value. Possible values are:
0—sticky bit not set; this file will be deleted from the APM cache during the next cache trimming operation, or when a clear saa apm cache command is executed.
1—sticky bit is set; this file can only be deleted by using the force keyword with the clear saa apm cache command.
|
Related Commands
Command
|
Description
|
clear saa apm cache
|
Deletes files from the IP SLAs Application Performance Monitor cache.
|
saa apm cache-size
|
Sets the size of the IP SLAs Application Performance Monitor (APM) cache.
|
show saa apm operation
|
Displays details about IP SLAs Application Performance Monitor (APM).
|
show saa apm information
Note
Effective with Cisco IOS Release 12.3(14)T, the show saa apm information command is replaced by the show ip sla monitor apm information command. See the show ip sla monitor apm information command for more information.
To display details about the Cisco IOS IP Service Level Agreements (IP SLAs) Application Performance Monitor (APM) running on the system, use the show saa apm information command in EXEC mode.
show saa apm information
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Release
|
Modification
|
12.2(2)T
|
This command was introduced.
|
12.3(14)T
|
This command was replaced by the show ip sla monitor apm information command.
|
Examples
The following is sample output from the show saa apm information command:
Router# show saa 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
|
saa 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 saa apm operation
Note
Effective with Cisco IOS Release 12.3(14)T, the show saa apm operation command is replaced by the show ip sla monitor apm operation command. See the show ip sla monitor apm operation command for more information.
To display details about the Cisco IOS IP Service Level Agreements (IP SLAs) Application Performance Monitor (APM) operations, use the show saa apm operation command in EXEC mode.
show saa 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
EXEC
Command History
Release
|
Modification
|
12.2(2)T
|
This command was introduced.
|
12.3(14)T
|
This command was replaced by the show ip sla monitor apm operation command.
|
Examples
The following is sample output from the show saa apm operation command:
Router# show saa 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 saa apm results
Note
Effective with Cisco IOS Release 12.3(14)T, the show saa apm results command is replaced by the show ip sla monitor apm results command. See the show ip sla monitor apm results command for more information.
To display the accumulated data for Cisco IOS IP Service Level Agreements (IP SLAs) Application Performance Monitor (APM) operations, use the show saa apm results command in EXEC mode.
show saa apm results [operation-number]
Syntax Description
operation-number
|
(Optional) A 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
EXEC
Command History
Release
|
Modification
|
12.2(2)T
|
This command was introduced.
|
12.3(14)T
|
This command was replaced by the show ip sla monitor 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 saa apm results command:
Router# show saa 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 159 describes the significant fields shown in the display.
Table 159 show saa apm cache 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 not set; this file will be deleted from the APM cache during the next cache trimming operation, or when a clear saa apm cache command is executed.
1—sticky bit is set; this file can only be deleted by using the force keyword with the clear saa apm cache command.
|
Related Commands
Command
|
Description
|
clear saa apm cache
|
Deletes files from the IP SLAs Application Performance Monitor cache.
|
saa apm cache-size
|
Sets the size of the IP SLAs Application Performance Monitor cache.
|
show saa apm operation
|
Displays details about IP SLAs Application Performance Monitor operations.
|
show slot
To display information about the PCMCIA flash memory cards file system, use the show slot command in user EXEC or privileged EXEC mode.
show slot [all | chips | detailed | err | summary]
Syntax Description
all
|
(Optional) Displays all possible flash system information for all PCMCIA flash cards in the system.
|
chips
|
(Optional) Displays flash chip information.
|
detailed
|
(Optional) Displays the flash detailed directory.
|
err
|
(Optional) Displays the flash chip erase and write retries.
|
summary
|
(Optional) Displays the flash partition summary.
|
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
12.0
|
This command was introduced.
|
Usage Guidelines
Use the show slot command to display details about the files in a particular linear PCMCIA flash memory card of less than 20 MB and some 32 MB linear PCMCIA cards.
Note
Use the show disk command for ATA PCMCIA cards. Other forms of this commands are show disk0: and show disk1:.
For more information regarding file systems and flash cards, access the PCMCIA Filesystem Compatibility Matrix and Filesystem Information document at the following URL:
http://www.cisco.com/en/US/partner/products/hw/routers/ps341/products_tech_note09186a00800a7515.shtml
To see which flash cards are used in your router, use the show version command and look at the bottom portion of the output.
The following display indicates an ATA PCMCIA flash disk.
46976K bytes of ATA PCMCIA card at slot 0 (Sector size 512 bytes).
The following display indicates a linear PCMCIA flash card with 20480K bytes of flash memory in card at slot 1 with a sector size of 128K.
20480K bytes of Flash PCMCIA card at slot 1 (Sector size 128K).
Note
In some cases the show slot command will not display the file systems, use show slot0: or show slot1:.
Examples
The following example displays information about slot 0. The output is self-explanatory.
PCMCIA Slot0 flash directory:
1 11081464 c3660-bin-mz.123-9.3.PI5b
[11081528 bytes used, 9627844 available, 20709372 total]
20480K bytes of processor board PCMCIA Slot0 flash (Read/Write)
The following example shows all possible flash system information for all PCMCIA flash cards in the system.
Partition Size Used Free Bank-Size State Copy Mode
1 20223K 10821K 9402K 4096K Read/Write Direct
PCMCIA Slot0 flash directory:
1 11081464 c3660-bin-mz.123-9.3.PI5b
[11081528 bytes used, 9627844 available, 20709372 total]
20480K bytes of processor board PCMCIA Slot0 flash (Read/Write)
1 1 89A0 2048KB INTEL 28F016SA
2 1 89A0 2048KB INTEL 28F016SA
1 2 89A0 2048KB INTEL 28F016SA
2 2 89A0 2048KB INTEL 28F016SA
1 3 89A0 2048KB INTEL 28F016SA
2 3 89A0 2048KB INTEL 28F016SA
1 4 89A0 2048KB INTEL 28F016SA
2 4 89A0 2048KB INTEL 28F016SA
1 5 89A0 2048KB INTEL 28F016SA
2 5 89A0 2048KB INTEL 28F016SA
The following example shows flash chip information
20480K bytes of processor board PCMCIA Slot0 flash (Read/Write)
1 1 89A0 2048KB INTEL 28F016SA
2 1 89A0 2048KB INTEL 28F016SA
1 2 89A0 2048KB INTEL 28F016SA
2 2 89A0 2048KB INTEL 28F016SA
1 3 89A0 2048KB INTEL 28F016SA
2 3 89A0 2048KB INTEL 28F016SA
1 4 89A0 2048KB INTEL 28F016SA
2 4 89A0 2048KB INTEL 28F016SA
1 5 89A0 2048KB INTEL 28F016SA
2 5 89A0 2048KB INTEL 28F016SA
The following example show the flash detailed directory.
Router# show slot detailed
PCMCIA Slot0 flash directory:
1 11081464 c3660-bin-mz.123-9.3.PI5b
[11081528 bytes used, 9627844 available, 20709372 total]
20480K bytes of processor board PCMCIA Slot0 flash (Read/Write)
The following example shows the flash chip erase and write retries.
PCMCIA Slot0 flash directory:
1 11081464 c3660-bin-mz.123-9.3.PI5b
[11081528 bytes used, 9627844 available, 20709372 total]
20480K bytes of processor board PCMCIA Slot0 flash (Read/Write)
Chip Bank Code Size Name erase write
1 1 89A0 2048KB INTEL 28F016SA 0 0
2 1 89A0 2048KB INTEL 28F016SA 0 0
1 2 89A0 2048KB INTEL 28F016SA 0 0
2 2 89A0 2048KB INTEL 28F016SA 0 0
1 3 89A0 2048KB INTEL 28F016SA 0 0
2 3 89A0 2048KB INTEL 28F016SA 0 0
1 4 89A0 2048KB INTEL 28F016SA 0 0
2 4 89A0 2048KB INTEL 28F016SA 0 0
1 5 89A0 2048KB INTEL 28F016SA 0 0
2 5 89A0 2048KB INTEL 28F016SA 0 0
The following example shows the flash partition summary.
Router# show slot summary
Partition Size Used Free Bank-Size State Copy Mode
1 20223K 10821K 9402K 4096K Read/Write Direct
20480K bytes of processor board PCMCIA Slot0 flash (Read/Write)
Related Commands
Command
|
Description
|
dir slot0:
|
Directory listing of files on a PCMCIA Flash card located in slot0.
|
dir slot1:
|
Directory listing of files on a PCMCIA Flash card located in slot1.
|
show slot0:
|
Displays information about the PCMCIA flash memory card's file system located in slot 0.
|
show slot1:
|
Displays information about the PCMCIA flash memory card's file system located in slot 1.
|
show slot0:
To display information about the PCMCIA flash memory card's file system located in slot 0, use the show slot0: command in user EXEC or privileged EXEC mode.
show slot0: [all | chips | detailed | err | summary]
Syntax Description
all
|
(Optional) Displays all possible flash system information for all PCMCIA flash cards in the system.
|
chips
|
(Optional) Displays flash chip information.
|
detailed
|
(Optional) Displays the flash detailed directory.
|
err
|
(Optional) Displays the flash chip erase and write retries.
|
summary
|
(Optional) Displays the flash partition summary.
|
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
12.0
|
This command was introduced.
|
Usage Guidelines
Use the show slot0: command to display details about the files in a particular linear PCMCIA flash memory card of less than 20 MB and some 32 MB linear PCMCIA cards.
Note
Use the show disk command for ATA PCMCIA cards. Other forms of this commands are show disk0: and show disk1:.
For more information regarding file systems and flash cards, access the PCMCIA Filesystem Compatibility Matrix and Filesystem Information document at the following URL:
http://www.cisco.com/en/US/partner/products/hw/routers/ps341/products_tech_note09186a00800a7515.shtml
To see which flash cards are used in your router, use the show version command and look at the bottom portion of the output.
The following display indicates an ATA PCMCIA flash disk.
46976K bytes of ATA PCMCIA card at slot 0 (Sector size 512 bytes).
The following display indicates a linear PCMCIA flash card with 20480K bytes of flash memory in card at slot 1 with a sector size of 128K.
20480K bytes of Flash PCMCIA card at slot 1 (Sector size 128K).
Note
In some cases the show slot command will not display the file systems, use show slot0: or show slot1:.
Examples
The following example displays information about slot 0. The output is self-explanatory.
PCMCIA Slot0 flash directory:
1 11081464 c3660-bin-mz.123-9.3.PI5b
[11081528 bytes used, 9627844 available, 20709372 total]
20480K bytes of processor board PCMCIA Slot0 flash (Read/Write)
Partition Size Used Free Bank-Size State Copy Mode
1 20223K 10821K 9402K 4096K Read/Write Direct
PCMCIA Slot0 flash directory:
1 11081464 c3660-bin-mz.123-9.3.PI5b
[11081528 bytes used, 9627844 available, 20709372 total]
20480K bytes of processor board PCMCIA Slot0 flash (Read/Write)
1 1 89A0 2048KB INTEL 28F016SA
2 1 89A0 2048KB INTEL 28F016SA
1 2 89A0 2048KB INTEL 28F016SA
2 2 89A0 2048KB INTEL 28F016SA
1 3 89A0 2048KB INTEL 28F016SA
2 3 89A0 2048KB INTEL 28F016SA
1 4 89A0 2048KB INTEL 28F016SA
2 4 89A0 2048KB INTEL 28F016SA
1 5 89A0 2048KB INTEL 28F016SA
2 5 89A0 2048KB INTEL 28F016SA
The following example shows flash chip information.
Router# show slot0: chips
20480K bytes of processor board PCMCIA Slot0 flash (Read/Write)
1 1 89A0 2048KB INTEL 28F016SA
2 1 89A0 2048KB INTEL 28F016SA
1 2 89A0 2048KB INTEL 28F016SA
2 2 89A0 2048KB INTEL 28F016SA
1 3 89A0 2048KB INTEL 28F016SA
2 3 89A0 2048KB INTEL 28F016SA
1 4 89A0 2048KB INTEL 28F016SA
2 4 89A0 2048KB INTEL 28F016SA
1 5 89A0 2048KB INTEL 28F016SA
2 5 89A0 2048KB INTEL 28F016SA
The following example show the flash detailed directory.
Router# show slot0: detailed
PCMCIA Slot0 flash directory:
1 11081464 c3660-bin-mz.123-9.3.PI5b
[11081528 bytes used, 9627844 available, 20709372 total]
20480K bytes of processor board PCMCIA Slot0 flash (Read/Write)
The following example shows the flash chip erase and write retries.
PCMCIA Slot0 flash directory:
1 11081464 c3660-bin-mz.123-9.3.PI5b
[11081528 bytes used, 9627844 available, 20709372 total]
20480K bytes of processor board PCMCIA Slot0 flash (Read/Write)
Chip Bank Code Size Name erase write
1 1 89A0 2048KB INTEL 28F016SA 0 0
2 1 89A0 2048KB INTEL 28F016SA 0 0
1 2 89A0 2048KB INTEL 28F016SA 0 0
2 2 89A0 2048KB INTEL 28F016SA 0 0
1 3 89A0 2048KB INTEL 28F016SA 0 0
2 3 89A0 2048KB INTEL 28F016SA 0 0
1 4 89A0 2048KB INTEL 28F016SA 0 0
2 4 89A0 2048KB INTEL 28F016SA 0 0
1 5 89A0 2048KB INTEL 28F016SA 0 0
2 5 89A0 2048KB INTEL 28F016SA 0 0
The following example shows the flash partition summary.
Router# show slot0: summary
Partition Size Used Free Bank-Size State Copy Mode
1 20223K 10821K 9402K 4096K Read/Write Direct
20480K bytes of processor board PCMCIA Slot0 flash (Read/Write)
Related Commands
Command
|
Description
|
dir slot0:
|
Directory listing of files on a PCMCIA Flash card located in slot0.
|
dir slot1:
|
Directory listing of files on a PCMCIA Flash card located in slot1.
|
show slot1:
|
Displays information about the PCMCIA flash memory card's file system located in slot 1.
|
show slot
|
Displays information about the PCMCIA flash memory cards.
|
show slot1:
To display information about the PCMCIA flash memory card's file system located in slot 1, use the show slot1: command in user EXEC or privileged EXEC mode.
show slot1: [all | chips | detailed | err | summary]
Syntax Description
all
|
(Optional) Displays all possible flash system information for all PCMCIA flash cards in the system.
|
chips
|
(Optional) Displays flash chip information.
|
detailed
|
(Optional) Displays the flash detailed directory.
|
err
|
(Optional) Displays the flash chip erase and write retries.
|
summary
|
(Optional) Displays the flash partition summary.
|
Command Modes
User EXEC
Privileged EXEC
Command History
Release
|
Modification
|
12.0
|
This command was introduced.
|
Usage Guidelines
Use the show slot1: command to display details about the files in a particular linear PCMCIA flash memory card of less than 20 MB and some 32 MB linear PCMCIA cards located in slot 1.
Note
Use the show disk command for ATA PCMCIA cards. Other forms of this commands are show disk0: and show disk1:.
For more information regarding file systems and flash cards, access the PCMCIA Filesystem Compatibility Matrix and Filesystem Information document at the following URL:
http://www.cisco.com/en/US/partner/products/hw/routers/ps341/products_tech_note09186a00800a7515.shtml
To see which flash cards are used in your router, use the show version command and look at the bottom portion of the output.
The following display indicates an ATA PCMCIA flash disk.
46976K bytes of ATA PCMCIA card at slot 0 (Sector size 512 bytes).
The following display indicates a linear PCMCIA flash card with 20480K bytes of flash memory in card at slot 1 with a sector size of 128K.
20480K bytes of Flash PCMCIA card at slot 1 (Sector size 128K).
Note
In some cases the show slot command will not display the file systems. Use show slot0: or show slot1:.
Examples
The following example displays information about slot 0 using the slot0: command form. The output
is self-explanatory.
PCMCIA Slot1 flash directory:
1 10907068 c3660-bin-mz.123-7.9.PI4
[10907132 bytes used, 5739008 available, 16646140 total]
16384K bytes of processor board PCMCIA Slot1 flash (Read/Write)
Partition Size Used Free Bank-Size State Copy Mode
1 20223K 10821K 9402K 4096K Read/Write Direct
PCMCIA Slot0 flash directory:
1 11081464 c3660-bin-mz.123-9.3.PI5b
[11081528 bytes used, 9627844 available, 20709372 total]
20480K bytes of processor board PCMCIA Slot0 flash (Read/Write)
1 1 89A0 2048KB INTEL 28F016SA
2 1 89A0 2048KB INTEL 28F016SA
1 2 89A0 2048KB INTEL 28F016SA
2 2 89A0 2048KB INTEL 28F016SA
1 3 89A0 2048KB INTEL 28F016SA
2 3 89A0 2048KB INTEL 28F016SA
1 4 89A0 2048KB INTEL 28F016SA
2 4 89A0 2048KB INTEL 28F016SA
1 5 89A0 2048KB INTEL 28F016SA
2 5 89A0 2048KB INTEL 28F016SA
The following example shows flash chip information.
Router# show slot1: chips
20480K bytes of processor board PCMCIA Slot0 flash (Read/Write)
1 1 89A0 2048KB INTEL 28F016SA
2 1 89A0 2048KB INTEL 28F016SA
1 2 89A0 2048KB INTEL 28F016SA
2 2 89A0 2048KB INTEL 28F016SA
1 3 89A0 2048KB INTEL 28F016SA
2 3 89A0 2048KB INTEL 28F016SA
1 4 89A0 2048KB INTEL 28F016SA
2 4 89A0 2048KB INTEL 28F016SA
1 5 89A0 2048KB INTEL 28F016SA
2 5 89A0 2048KB INTEL 28F016SA
The following example show the flash detailed directory.
Router# show slot1: detailed
PCMCIA Slot0 flash directory:
1 11081464 c3660-bin-mz.123-9.3.PI5b
[11081528 bytes used, 9627844 available, 20709372 total]
20480K bytes of processor board PCMCIA Slot0 flash (Read/Write)
The following example shows the flash chip erase and write retries.
PCMCIA Slot0 flash directory:
1 11081464 c3660-bin-mz.123-9.3.PI5b
[11081528 bytes used, 9627844 available, 20709372 total]
20480K bytes of processor board PCMCIA Slot0 flash (Read/Write)
Chip Bank Code Size Name erase write
1 1 89A0 2048KB INTEL 28F016SA 0 0
2 1 89A0 2048KB INTEL 28F016SA 0 0
1 2 89A0 2048KB INTEL 28F016SA 0 0
2 2 89A0 2048KB INTEL 28F016SA 0 0
1 3 89A0 2048KB INTEL 28F016SA 0 0
2 3 89A0 2048KB INTEL 28F016SA 0 0
1 4 89A0 2048KB INTEL 28F016SA 0 0
2 4 89A0 2048KB INTEL 28F016SA 0 0
1 5 89A0 2048KB INTEL 28F016SA 0 0
2 5 89A0 2048KB INTEL 28F016SA 0 0
The following example shows the flash partition summary.
Router# show slot1: summary
Partition Size Used Free Bank-Size State Copy Mode
1 20223K 10821K 9402K 4096K Read/Write Direct
20480K bytes of processor board PCMCIA Slot0 flash (Read/Write)
Related Commands
Command
|
Description
|
dir slot0:
|
Directory listing of files on a PCMCIA Flash card located in slot0.
|
dir slot1:
|
Directory listing of files on a PCMCIA Flash card located in slot1.
|
show slot0:
|
Displays information about the PCMCIA flash memory card's file system located in slot 0.
|
show slot
|
Displays information about the PCMCIA flash memory cards.
|
show snmp
To check the status of Simple Network Management Protocol (SNMP) communications, use the show snmp command in EXEC mode.
show snmp
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
Usage Guidelines
This command provides counter information for SNMP operations. It also displays the chassis ID string defined with the snmp-server chassis-id global configuration command.
Examples
The following is sample output from the show snmp command:
0 Bad SNMP version errors
0 Illegal operation for community name supplied
24 Number of requested variables
0 Number of altered variables
0 Too big errors (Maximum packet size 1500)
Logging to 171.69.58.33.162, 0/10, 13 sent, 0 dropped.
SNMP Manager-role output packets
SNMP Manager-role input packets
Informs in flight 0/25 (current/max)
Logging to 171.69.217.141.162
4 sent, 0 in-flight, 1 retries, 0 failed, 0 dropped
Logging to 171.69.58.33.162
0 sent, 0 in-flight, 0 retries, 0 failed, 0 dropped
Table 160 describes the significant fields shown in the display.
Table 160 show snmp Field Descriptions
Field
|
Description
|
Chassis
|
Chassis ID string.
|
SNMP packets input
|
Total number of SNMP packets input.
|
Bad SNMP version errors
|
Number of packets with an invalid SNMP version.
|
Unknown community name
|
Number of SNMP packets with an unknown community name.
|
Illegal operation for community name supplied
|
Number of packets requesting an operation not allowed for that community.
|
Encoding errors
|
Number of SNMP packets that were improperly encoded.
|
Number of requested variables
|
Number of variables requested by SNMP managers.
|
Number of altered variables
|
Number of variables altered by SNMP managers.
|
Get-request PDUs
|
Number of get requests received.
|
Get-next PDUs
|
Number of get-next requests received.
|
Set-request PDUs
|
Number of set requests received.
|
SNMP packets output
|
Total number of SNMP packets sent by the router.
|
Too big errors
|
Number of SNMP packets which were larger than the maximum packet size.
|
Maximum packet size
|
Maximum size of SNMP packets.
|
No such name errors
|
Number of SNMP requests that specified a MIB object that does not exist.
|
Bad values errors
|
Number of SNMP set requests that specified an invalid value for a MIB object.
|
General errors
|
Number of SNMP set requests that failed due to some other error. (It was not a noSuchName error, badValue error, or any of the other specific errors.)
|
Response PDUs
|
Number of responses sent in reply to requests.
|
Trap PDUs
|
Number of SNMP traps sent.
|
SNMP logging
|
Indicates whether logging is enabled or disabled.
|
sent
|
Number of traps sent.
|
dropped
|
Number of traps dropped. Traps are dropped when the trap queue for a destination exceeds the maximum length of the queue, as set by the snmp-server queue-length global configuration command.
|
SNMP Manager-role output packets
|
Information related to packets sent by the router as an SNMP manager.
|
Get-request PDUs
|
Number of get requests sent.
|
Get-next PDUs
|
Number of get-next requests sent.
|
Get-bulk PDUs
|
Number of get-bulk requests sent.
|
Set-request PDUs
|
Number of set requests sent.
|
Inform-request PDUs
|
Number of inform requests sent.
|
Timeouts
|
Number of request timeouts.
|
Drops
|
Number of requests dropped. Reasons for drops include no memory, a bad destination address, or an unreasonable destination address.
|
SNMP Manager-role input packets
|
Information related to packets received by the router as an SNMP manager.
|
Inform response PDUs
|
Number of inform request responses received.
|
Trap PDUs
|
Number of SNMP traps received.
|
Response PDUs
|
Number of responses received.
|
Responses with errors
|
Number of responses containing errors.
|
SNMP informs
|
Indicates whether SNMP informs are enabled.
|
Informs in flight
|
Current and maximum possible number of informs waiting to be acknowledged.
|
Logging to
|
Destination of the following informs.
|
sent
|
Number of informs sent to this host.
|
in-flight
|
Number of informs currently waiting to be acknowledged.
|
retries
|
Number of inform retries sent.
|
failed
|
Number of informs that were never acknowledged.
|
dropped
|
Number of unacknowledged informs that were discarded to make room for new informs.
|
Related Commands
Command
|
Description
|
show snmp pending
|
Displays the current set of pending SNMP requests.
|
show snmp sessions
|
Displays the current SNMP sessions.
|
snmp-server chassis-id
|
Provides a message line identifying the SNMP server serial number.
|
snmp-server manager
|
Starts the SNMP manager process.
|
snmp-server manager session-timeout
|
Sets the amount of time before a nonactive session is destroyed.
|
snmp-server queue-length
|
Establishes the message queue length for each trap host.
|
show snmp engineID
To display the identification of the local Simple Network Management Protocol (SNMP) engine and all remote engines that have been configured on the router, use the show snmp engineID command in EXEC mode.
show snmp engineID
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Release
|
Modification
|
12.0(3)T
|
This command was introduced.
|
Usage Guidelines
An SNMP engine is a copy of SNMP that can reside on a local or remote device.
Examples
The following example specifies 00000009020000000C025808 as the local engineID and 123456789ABCDEF000000000 as the remote engine ID, 171.69.37.61 as the IP address of the remote engine (copy of SNMP) and 162 as the port from which the remote device is connected to the local device:
Router# show snmp engineID
Local SNMP engineID: 00000009020000000C025808
Remote Engine ID IP-addr Port
123456789ABCDEF000000000 171.69.37.61 162
Table 161 describes the fields shown in the display.
Table 161 show snmp engineID Field Descriptions
Field
|
Definition
|
Local SNMP engine ID
|
A string that identifies the copy of SNMP on the local device.
|
Remote Engine ID
|
A string that identifies the copy of SNMP on the remote device.
|
IP-addr
|
The IP address of the remote device.
|
Port
|
The port number on the local device to which the remote device is connected.
|
Related Commands
Command
|
Description
|
snmp-server engineID local
|
Configures a name for either the local or remote SNMP engine on the router.
|
show snmp group
To display the names of configured SNMP groups, the security model being used, the status of the different views, and the storage type of each group, use the show snmp group command in privileged EXEC mode.
show snmp group
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.0(3)T
|
This command was introduced.
|
Usage Guidelines
SNMP groups are configured using the snmp-server group command.
SNMP groups and users are used in the context of the View-based Access Control Model (VACM) for SNMP (for further information, see the "VACM for SNMP" IETF internet draft document).
Examples
The following example specifies the group name as public, the security model as v1, the read view name as v1default, the notify view name as *tv.FFFFFFFF, and the storage type as volatile:
groupname: ILMI security model:v1
readview : *ilmi writeview: *ilmi
notifyview: <no notifyview specified>
groupname: ILMI security model:v2c
readview : *ilmi writeview: *ilmi
notifyview: <no notifyview specified>
groupname: public security model:v1
readview : <no readview specified> writeview: <no writeview specified>
notifyview: *tv.FFFFFFFF.FFFFFFFF.FFFFFFFF0F
groupname: public security model:v2c
readview : <no readview specified> writeview: <no writeview specified>
notifyview: *tv.FFFFFFFF.FFFFFFFF.FFFFFFFF0F
Table 162 describes the fields shown in the example.
Table 162 show snmp group Field Descriptions
Field
|
Definition
|
groupname
|
The name of the SNMP group, or collection of users that have a common access policy.
|
security model
|
The security model used by the group, either v1, v2c, or v3.
|
readview
|
A string identifying the read view of the group.
• For further information on the SNMP views, use the show snmp view command.
|
writeview
|
A string identifying the write view of the group.
|
notifyview
|
A string identifying the notify view of the group.
The notify view indicates the group for SNMP notifications, and corresponds to the setting of the snmp-server group group-name version notify notify-view command.
|
Related Commands
Command
|
Description
|
snmp-server group
|
Configures a new SNMP group or a table that maps SNMP users to SNMP views.
|
show snmp user
|
Displays the configured characteristics for SNMP users.
|
show snmp view
|
Displays a list of configured SNMP views.
|
show snmp mib
To display a list of the MIB module instance identifiers (OIDs) registered on your system, use the show snmp mib command in EXEC mode.
show snmp mib
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Release
|
Modification
|
12.2, 12.2(2)T
|
This command was introduced.
|
Usage Guidelines
SNMP management information is viewed as a collection of managed objects, residing in a virtual information store, termed the Management Information Base (MIB). Collections of related objects are defined in MIB modules. These modules are written using a subset of OSIs Abstract Syntax Notation One (ASN.1), termed the Structure of Management Information (SMI).
This command is intended for network administrators who are familiar with the SMI and ASN.1 syntax.
While this command can be used to display a list of MIB object identifiers (OIDs) registered on the system, the use of a network management system (NMS) application is the recommended alternative for gathering this information.
The show snmp mib command will display the instance identifiers for all the MIB objects on the system. The instance identifier is the final part of the OID. An object can have one or more instance identifiers. Before displaying the instance identifier, the system attempts to find the best match with the list of table names. The MIB module table names are registered when the system initializes.
The definitions for the OIDs displayed by this command can be found in the relevant RFCs and MIB modules. For example, RFC 1907 defines the system.x, sysOREntry.x, snmp.x, and snmpTrap.x OIDs, and this information is supplemented by the extensions defined in the CISCO-SYSTEM-MIB.
Tip
This command produces a high volume of output if SNMP is enabled on your system. To exit from a --More-- prompt, press Ctrl-Z.
Examples
The following is sample output from the show snmp mib command:
Related Commands
Command
|
Description
|
show snmp mib ifmib ifindex
|
Displays SNMP Interface Index identification numbers (ifIndex values) for all the system interfaces or the specified system interface
|
show snmp mib bulkstat transfer
To display the transfer status of files generated by the Periodic MIB Data Collection and Transfer Mechanism (Bulk Statistics feature), use the show snmp mib bulkstat transfer command in privileged EXEC mode.
show snmp mib bulkstat transfer [transfer-id]
Syntax Description
transfer-id
|
(Optional) Name of a specific bulk statistics transfer configuration. Use this keyword to display only the status of one bulk statistics transfer configuration.
|
Defaults
If the optional transfer-id argument is not used, the status of all configured bulk statistics transfers is displayed.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.0(24)S
|
This command was introduced.
|
12.3(2)T
|
This command was integrated into Cisco IOS Release 12.3(2)T.
|
12.2(25)S
|
This command was integrated into Cisco IOS Release 12.2(25)S.
|
Examples
In the following example, the initial transfer attempt and the first retry for the file
IfMIB_objects_Router_030307_102519739 to the primary and secondary URL has failed, and
four additional retry attempts will be made. The time stamp for this file indicates the
file was created on March 7, 2003, at 10:25:19 a.m.
Router# show snmp mib bulkstat transfer
Transfer Name : IfMIB_objects
Primary URL ftp://user:XXXXXXXX@209.165.200.162/
Secondary ftp://user:XXXXXXXX@209.165.200.163/
File Name :Time Left (in seconds) : STATE
----------------------------------------------------------------------
IfMIB_objects_Router_030307_102519739 : 1196 :Retry(5 Retry attempt(s) Left)
IfMIB_objects_Router_030307_102219739 : 1016 :Retained
IfMIB_objects_Router_030307_101919739 : 836 :Retained
IfMIB_objects_Router_030307_101619739 : 656 :Retained
IfMIB_objects_Router_030307_101319739 : 475 :Retained
IfMIB_objects_Router_030307_101119739 : 295 :Retained
Table 163 describes the significant fields shown in the display.
Table 163 show snmp mib bulkstat transfer Field Descriptions
Field
|
Description
|
Transfer Name
|
The name of the transfer configuration, specified in the snmp mib bulkstat transfer global configuration command.
|
Retained files
|
Indicates that the following output shows the status of files that are in system memory (retained), as opposed to files that have already been set.
|
File Name
|
The name of the bulk statistics file as it will appear after transfer. The filename of the file is generated using the following components:
transfer-name_device-name_date_time-stamp
The transfer-name is the name specified by the corresponding snmp mib bulkstat transfer command. The device-name is the name used in the CLI router prompt. The format of the date and time-stamp depends on your system configuration, but is typically YYMMDD and HHMMSSmmm, where HH is hour, MM is minutes, SS is seconds and mmm is milliseconds.
|
Time Left (in seconds)
|
Indicates how much time is left before the specified file will be deleted (retention period), as specified with the retain Bulk Statistics Transfer configuration command.
Note Regardless of the configured retention period, all retry attempts will be made before the file is deleted.
|
STATE
|
The state of the local bulk statistics file will be one of the following:
Queued—Collection time for this file is completed and the file is waiting for transfer to configured primary and secondary URL.
Retained—The file has been either successfully transferred to its destination or, if all transfer attempts have failed, all retry attempts have been completed.
Retry—The local bulk statistics file will be in this state if an attempt to transfer it to its configured destination fails and one or more retries are pending. The number of retries left will also be displayed in parenthesis.
|
Related Commands
Command
|
Description
|
snmp mib bulkstat transfer
|
Names a bulk statistics transfer configuration and enters Bulk Statistics Transfer configuration mode.
|
show snmp mib ifmib ifindex
To display SNMP Interface Index identification numbers (ifIndex values) for all the system interfaces or the specified system interface, use the show snmp mib ifmib ifindex command in EXEC mode.
show snmp mib ifmib ifindex [interface-type] [slot/][port-adapter/][port]
Syntax Description
interface-type
|
The type of interface. Use the show snmp mib ifmib ifindex ? command to determine the options available on your system. Typical interface-types include async, dialer, ethernet, fastEthernet, serial and so on.
|
slot/
|
The slot number for the interface card, followed by a forward-slash. The availability of this argument depends on your system hardware configuration.
|
port-adapter/
|
The port-adapter number, followed by a forward-slash. The availability of this argument depends on your system hardware configuration.
|
port
|
The interface number.
|
Defaults
The ifIndex values for all interfaces are displayed.
Command Modes
EXEC
Command History
Release
|
Modification
|
12.2(2)T
|
This command was introduced.
|
Usage Guidelines
The show snmp mib ifmib ifindex command allows you to display SNMP Interface Index identification numbers (ifIndex values) assigned to interfaces and subinterfaces using the CLI. This command provides a way to view these values without the need for a Network Management Station.
If a specific interface is not specified using the optional interface-type, slot, port-adapter, and port arguments, the ifDescr and ifIndex pairs of all interfaces and subinterfaces present on the system are shown.
Examples
The following example shows output for a specific interface:
Router# show snmp mib ifmib ifIndex Ethernet2/0
The following examples shows output for all interfaces:
Router# show snmp mib ifmib ifindex
ATM1/0-aal5 layer: Ifindex = 12
ATM1/0-atm layer: Ifindex = 10
ATM1/0.0-aal5 layer: Ifindex = 13
ATM1/0.0-atm subif: Ifindex = 11
ATM1/0.9-aal5 layer: Ifindex = 32
ATM1/0.9-atm subif: Ifindex = 31
ATM1/0.99-aal5 layer: Ifindex = 36
ATM1/0.99-atm subif: Ifindex = 35
Related Commands
Command
|
Description
|
show snmp mib
|
Displays a list of the MIB module instance identifiers (OIDs) registered on the system.
|
snmp ifindex persist
|
Enables ifIndex values in the Interfaces MIB (IF-MIB) that persist across reboots only on a specific interface.
|
snmp ifmib ifalias long
|
Configures the system to handle IfAlias descriptions of up to 256 characters in length.
|
snmp-server ifindex persist
|
Enables ifIndex values in the Interfaces MIB (IF-MIB) that persist across reboots for all interfaces (globally).
|
show snmp mib notification-log
To display information about the state of local SNMP notification logging, use the show snmp mib notification-log command in EXEC mode.
show snmp mib notification-log [all | default]
Syntax Description
all
|
(Optional) Displays all notification log entries stored in the local Notification Log MIB database.
|
default
|
(Optional) Displays summary information for the default (unnamed) SNMP Notification Log.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
12.0(22)S
|
This command was introduced.
|
12.2(13)T
|
This command was integrated into Release 12.2(13)T.
|
Usage Guidelines
The SNMP Notification Log works in conjunction with the NOTIFICATION-LOG-MIB.my MIB module (available at ftp://ftp.cisco.com/pub/mibs/v2/). This MIB module is based on RFC 3014. The local logs can be polled by external network management applications to verify that they have not missed important SNMP notifications (traps and informs).
The show snmp mib notification-log all command displays all logged notification entries currently in the local MIB database. Entries are displayed from the oldest to the newest. The time of entry creation is determined using the system-up-time (sysUpTime) value; this means that the age of the entry is set using the amount of time that has passed since the router was last restarted. Other information for the entries includes the notificationID, and the filters (varbinds) associated with the log, if any.
Examples
The following is sample output from the show snmp mib notification-log command:
Router# show snmp mib notification-log
GlobalAgeout 15, GlobalEntryLimit 500
Total Notifications logged in all logs 0
Log Name"", Log entry Limit 500, Notifications logged 0
Note that in this example, the Log Name of "" indicates the default "null-named" Notification Log.
Related Commands
Command
|
Description
|
snmp mib notification-log default
|
Creates and activates an SNMP Notification Log.
|
snmp mib notification-log globalageout
|
Sets the maximum age for a notification.
|
snmp mib notification-log globalsize
|
Sets the maximum number of notifications allowed in all logs.
|
show snmp pending
To display the current set of pending Simple Network Management Protocol (SNMP) requests, use the show snmp pending command in EXEC mode.
show snmp pending
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Release
|
Modification
|
11.3 T
|
This command was introduced.
|
Usage Guidelines
After the SNMP manager sends a request, the request is "pending" until the manager receives a response or the request timeout expires.
Examples
The following is sample output from the show snmp pending command:
Router# show snmp pending
req id: 47, dest: 171.69.58.33.161, V2C community: public, Expires in 5 secs
req id: 49, dest: 171.69.58.33.161, V2C community: public, Expires in 6 secs
req id: 51, dest: 171.69.58.33.161, V2C community: public, Expires in 6 secs
req id: 53, dest: 171.69.58.33.161, V2C community: public, Expires in 8 secs
Table 164 describes the significant fields shown in the display.
Table 164 show snmp pending Field Descriptions
Field
|
Description
|
req id
|
ID number of the pending request.
|
dest
|
IP address of the intended receiver of the request.
|
V2C community
|
SNMP version 2C community string sent with the request.
|
Expires in
|
Remaining time before request timeout expires.
|
Related Commands
Command
|
Description
|
show snmp
|
Checks the status of SNMP communications.
|
show snmp sessions
|
Displays the current SNMP sessions.
|
snmp-server manager
|
Starts the SNMP manager process.
|
snmp-server manager session-timeout
|
Sets the amount of time before a nonactive session is destroyed.
|
show snmp sessions
To display the current Simple Network Management Protocol (SNMP) sessions, use the show snmp sessions command in EXEC mode.
show snmp sessions [brief]
Syntax Description
brief
|
(Optional) Displays a list of sessions only. Does not display session statistics.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
11.3 T
|
This command was introduced.
|
Usage Guidelines
Sessions are created when the SNMP manager in the router sends SNMP requests, such as inform requests, to a host or receives SNMP notifications from a host. One session is created for each destination host. If there is no further communication between the router and host within the session timeout period, the corresponding session will be deleted.
Examples
The following is sample output from the show snmp sessions command:
Router# show snmp sessions
Destination: 171.69.58.33.162, V2C community: public
Round-trip-times: 0/0/0 (min/max/last)
0 Gets, 0 GetNexts, 0 GetBulks, 0 Sets, 4 Informs
0 Traps, 0 Informs, 0 Responses (0 errors)
Destination: 171.69.217.141.162, V2C community: public, Expires in 575 secs
Round-trip-times: 1/1/1 (min/max/last)
0 Gets, 0 GetNexts, 0 GetBulks, 0 Sets, 4 Informs
0 Traps, 0 Informs, 4 Responses (0 errors)
The following is sample output from the show snmp sessions brief command:
Router# show snmp sessions brief
Destination: 171.69.58.33.161, V2C community: public, Expires in 55 secs
Table 165 describes the significant fields shown in the display.
Table 165 show snmp sessions Field Descriptions
Field
|
Description
|
Destination
|
IP address of the remote agent.
|
V2C community
|
SNMP version 2C community string used to communicate with the remote agent.
|
Expires in
|
Remaining time before the session timeout expires.
|
Round-trip-times
|
Minimum, maximum, and the last round-trip time to the agent.
|
packets output
|
Packets sent by the router.
|
Gets
|
Number of get requests sent.
|
GetNexts
|
Number of get-next requests sent.
|
GetBulks
|
Number of get-bulk requests sent.
|
Sets
|
Number of set requests sent.
|
Informs
|
Number of inform requests sent.
|
Timeouts
|
Number of request timeouts.
|
Drops
|
Number of packets that could not be sent.
|
packets input
|
Packets received by the router.
|
Traps
|
Number of traps received.
|
Informs
|
Number of inform responses received.
|
Responses
|
Number of request responses received.
|
errors
|
Number of responses that contained an SNMP error code.
|
Related Commands
Command
|
Description
|
show snmp
|
Checks the status of SNMP communications.
|
show snmp pending
|
Displays the current set of pending SNMP requests.
|
snmp-server manager
|
Starts the SNMP manager process.
|
snmp-server manager session-timeout
|
Sets the amount of time before a nonactive session is destroyed.
|
show snmp user
To display information about the configured characteristics of Simple Network Management Protocol (SNMP) users, use the show snmp user command in privileged EXEC mode.
show snmp user [username]
Syntax Description
username
|
(Optional) Name of a specific user or users about which to display SNMP information.
|
Defaults
No default behavior or values
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.0(3)T
|
This command was introduced.
|
12.3(2)T
|
The username argument was added. The output for this command was enhanced to show Authentication Protocol (MD5 or SHA) and Group Name.
|
Usage Guidelines
An SNMP user must be part of an SNMP group, as configured using the snmp-server user username group-name command.
When the username argument is not entered, the show snmp user command displays information about all configured users. If you specify the username argument, if one or more users of that name exists, the information pertaining to those users is displayed. Because this command displays users configured with the SNMP engine ID of the local agent and other engine IDs there can be multiple users with the same username.
When configuring SNMP, you may see the logging message "Configuring snmpv3 USM user." USM stands for the User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3). For further information on the USM, see RFC 2574.
Examples
The following example specifies the username as authuser, the engine ID string as 00000009020000000C025808, and the storage type as nonvolatile:
Router# show snmp user authuser
Engine ID: 00000009020000000C025808
storage-type: nonvolatile active access-list: 10
Authentication Protocol: MD5
Group name: VacmGroupName
Table 166 describes the significant fields shown in the display.
Table 166 show snmp user Field Descriptions
Field
|
Description
|
User name
|
A string identifying the name of the SNMP user.
|
Engine ID
|
A string identifying the name of the copy of SNMP on the device.
|
storage-type
|
Indicates whether the settings have been set in volatile or temporary memory on the device, or in nonvolatile or persistent memory where settings will remain after the device has been turned off and on again.
|
access-list:
|
Standard IP access list associated with the SNMP user.
|
Rowstatus:
|
Indicates whether Rowstatus is active or inactive.
|
Authentication Protocol:
|
Identifies which authentication protocol is used. Options are message digest algorithm 5 (MD5) and Secure Hash Algorithm (SHA) packet authentication, or "None."
• If authentication is not supported in your software image, this field will not be displayed.
|
Privacy protocol:
|
Indicates whether Data Encryption Standard (DES) packet encryption is enabled.
• If DES is not supported in your software image, this field will not be displayed.
|
Group name:
|
Indicates the SNMP group the user is a part of.
• SNMP groups are defined in the context of a View-based Access Control Model (VACM).
|
Related Commands
Command
|
Description
|
snmp-server group
|
Configures an SNMP user group.
|
snmp-server user
|
Configures a new user to an SNMP group.
|
show sntp
To show information about the Simple Network Time Protocol (SNTP), use the show sntp command in EXEC mode on a Cisco 1003, Cisco 1004, Cisco 1005, Cisco 1600, Cisco 1720, or Cisco 1750 router.
show sntp
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Release
|
Modification
|
11.2
|
This command was introduced.
|
Examples
The following is sample output from the show sntp command:
SNTP server Stratum Version Last Receive
171.69.118.9 5 3 00:01:02
172.21.28.34 4 3 00:00:36 Synced Bcast
Broadcast client mode is enabled.
Table 167 describes the significant fields shown in the display.
Table 167 show sntp Field Descriptions
Field
|
Description
|
SNTP server
|
Address of the configured or broadcast NTP server.
|
Stratum
|
NTP stratum of the server. The stratum indicates how far away from an authoritative time source the server is.
|
Version
|
NTP version of the server.
|
Last Receive
|
Time since the last NTP packet was received from the server.
|
Synced
|
Indicates the server chosen for synchronization.
|
Bcast
|
Indicates a broadcast server.
|
Related Commands
Command
|
Description
|
sntp broadcast client
|
Configures a Cisco 1003, Cisco 1004, Cisco 1005, Cisco 1600, Cisco 1720, or Cisco 1750 router to use SNTP to accept NTP traffic from any broadcast server.
|
sntp server
|
Configures a Cisco 1003, Cisco 1004, Cisco 1005, Cisco 1600, Cisco 1720, or Cisco 1750 router to use SNTP to request and accept NTP traffic from a time server.
|
show stacks
To monitor the stack usage of processes and interrupt routines, use the show stacks command in EXEC mode.
show stacks
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 display from this command includes the reason for the last system reboot. If the system was reloaded because of a system failure, a saved system stack trace is displayed. This information is of use only to your technical support representative in analyzing crashes in the field. It is included here in case you need to read the displayed statistics to an engineer over the phone.
Examples
The following is sample output from the show stacks command following a system failure:
Level Called Free/Size Name
3 738 900/1000 Multiport Communications Interfaces
5 178 970/1000 Console UART
System was restarted by bus error at PC 0xAD1F4, address 0xD0D0D1A
GS Software (GS3), Version 9.1(0.16), BETA TEST SOFTWARE
Compiled Tue 11-Aug-92 13:27 by jthomas
Stack trace from system failure:
FP: 0x29C158, RA: 0xACFD4
FP: 0x29C184, RA: 0xAD20C
FP: 0x29C1B0, RA: 0xACFD4
FP: 0x29C1DC, RA: 0xAD304
FP: 0x29C1F8, RA: 0xAF774
FP: 0x29C214, RA: 0xAF83E
FP: 0x29C228, RA: 0x3E0CA
FP: 0x29C244, RA: 0x3BD3C
Related Commands
Command
|
Description
|
show processes
|
Displays information about the active processes.
|
show startup-config
The more nvram:startup-config command has been replaced by the show startup-config command. See the description of the more command in the "Cisco IOS File System Commands" chapter for more information.
show subsys
To display the subsystem information, use the show subsys command in privileged EXEC mode.
show subsys [class class | name name]
Syntax Description
class class
|
(Optional) Displays the subsystems of the specified class. Valid classes are driver, kernel, library, management, protocol, and registry.
|
name name
|
(Optional) Displays the specified subsystem. Use the asterisk character (*) as a wildcard at the end of the name to list all subsystems, starting with the specified characters.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
11.1
|
This command was introduced.
|
Usage Guidelines
Use the show subsys command to confirm that all required features are in the running image.
Examples
The following is sample output from the show subsys command:
static_map Kernel 1.000.001
compress Kernel 1.000.001
alignment Kernel 1.000.002
ip_addrpool_sys Library 1.000.001
flash_services Library 1.000.001
ip_localpool_sys Library 1.000.001
nvram_common Driver 1.000.001
oc12suni Driver 1.000.001
Table 168 describes the fields shown in the display.
Table 168 show subsys Field Descriptions
Field
|
Description
|
static_map
|
Name of the subsystem.
|
Class
|
Class of the subsystem. Possible classes include Kernel, Library, Driver, Protocol, Management, Registry, and SystemInit.
|
Version
|
Version of the subsystem.
|
show tcp
To display the status of TCP connections, use the show tcp command in privileged EXEC mode.
show tcp [line-number] [tcb address]
Syntax Description
line-number
|
(Optional) Absolute line number of the line for which you want to display Telnet connection status.
|
tcb address
|
(Optional) Transmission control block (TCB) of the ECN-enabled connection that you want to display. The address argument is the TCB hexidecimal address. The valid range is from 0x0 to 0xFFFFFFFF.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
12.3(7)T
|
The tcb keyword and address argument were added.
|
Examples
The following is sample output from the show tcp command:
tty0, connection 1 to host cider
Connection state is ESTAB, I/O status: 1, unread input bytes: 0
Local host: 172.31.232.17, Local port: 11184
Foreign host: 172.31.1.137, Foreign port: 23
Enqueued packets for retransmit: 0, input: 0, saved: 0
Event Timers (current time is 67341276):
Timer: Retrans TimeWait AckHold SendWnd KeepAlive GiveUp PmtuAger
iss: 67317172 snduna: 67317228 sndnxt: 67317228 sndwnd: 4096
irs: 1064896000 rcvnxt: 1064897597 rcvwnd: 2144 delrcvwnd: 0
SRTT: 317 ms, RTTO: 900 ms, RTV: 133 ms, KRTT: 0 ms
minRTT: 4 ms, maxRTT: 300 ms, ACK hold: 300 ms
Flags: higher precedence, idle user, retransmission timeout
Datagrams (max data segment is 536 bytes):
Rcvd: 41 (out of order: 0), with data: 34, total data bytes: 1596
Sent: 57 (retransmit: 1), with data: 35, total data bytes: 55
Table 169 describes the first five lines of output shown in the preceding display.
Table 169 show tcp Field Descriptions—First Section of Output
Field
|
Description
|
tty
|
Identifying number of the line.
|
connection
|
Identifying number of the TCP connection.
|
to host
|
Name of the remote host to which the connection has been made.
|
Connection state is
|
A connection progresses through a series of states during its lifetime. The states that follow are shown in the order in which a connection progresses through them.
• LISTEN—Waiting for a connection request from any remote TCP and port.
• SYNSENT—Waiting for a matching connection request after having sent a connection request.
• SYNRCVD—Waiting for a confirming connection request acknowledgment after having both received and sent a connection request.
• ESTAB—Indicates an open connection; data received can be delivered to the user. This is the normal state for the data transfer phase of the connection.
• FINWAIT1—Waiting for a connection termination request from the remote TCP or an acknowledgment of the connection termination request previously sent.
|
| |
• FINWAIT2—Waiting for a connection termination request from the remote TCP host.
• CLOSEWAIT—Waiting for a connection termination request from the local user.
• CLOSING—Waiting for a connection termination request acknowledgment from the remote TCP host.
• LASTACK—Waiting for an acknowledgment of the connection termination request previously sent to the remote TCP host.
• TIMEWAIT—Waiting for enough time to pass to be sure that the remote TCP host has received the acknowledgment of its connection termination request.
• CLOSED—Indicates no connection state at all.
For more information, refer to RFC 793, Transmission Control Protocol Functional Specification.
|
I/O status
|
Number that describes the current internal status of the connection.
|
unread input bytes
|
Number of bytes that the lower-level TCP processes have read but that the higher-level TCP processes have not yet processed.
|
Local host
|
IP address of the network server.
|
Local port
|
Local port number, as derived from the following equation: line-number + (512 * random-number). (The line number uses the lower nine bits; the other bits are random.)
|
Foreign host
|
IP address of the remote host to which the TCP connection has been made.
|
Foreign port
|
Destination port for the remote host.
|
Enqueued packets for retransmit
|
Number of packets that are waiting on the retransmit queue. These are packets on this TCP connection that have been sent but that have not yet been acknowledged by the remote TCP host.
|
input
|
Number of packets that are waiting on the input queue to be read by the user.
|
saved
|
Number of received out-of-order packets that are waiting for all packets that comprise the message to be received before they enter the input queue. For example, if packets 1, 2, 4, 5, and 6 have been received, packets 1 and 2 would enter the input queue, and packets 4, 5, and 6 would enter the saved queue.
|

Note
Use the show tcp brief command to display information about the ECN-enabled connections.
The following line of output shows the current elapsed time according to the system clock of the local host. The time shown is the number of milliseconds since the system started.
Event Timers (current time is 67341276):
The following lines of output display the number of times that various local TCP timeout values were reached during this connection. In this example, the local host re-sent data 30 times because it received no response from the remote host, and it sent an acknowledgment many more times because there was no data on which to piggyback.
Timer: Retrans TimeWait AckHold SendWnd KeepAlive GiveUp PmtuAger
Table 170 describes the fields in the preceding lines of output.
Table 170 show tcp Field Descriptions—Second Section of Output
Field
|
Description
|
Timer
|
The names of the timers in the display.
|
Starts
|
The number of times that the timer has been started during this connection.
|
Wakeups
|
The number of keepalives sent without receiving any response. (This field is reset to zero when a response is received.)
|
Next
|
The system clock setting that will trigger the next time this timer will go off.
|
Retrans
|
The Retransmission timer is used to time TCP packets that have not been acknowledged and that are waiting for retransmission.
|
TimeWait
|
The TimeWait timer is used to ensure that the remote system receives a request to disconnect a session.
|
AckHold
|
The Acknowledgment timer is used to delay the sending of acknowledgments to the remote TCP in an attempt to reduce network use.
|
SendWnd
|
The Send Window is used to ensure that there is no closed window due to a lost TCP acknowledgment.
|
KeepAlive
|
The KeepAlive timer is used to control the transmission of test messages to the remote TCP to ensure that the link has not been broken without the local TCP's knowledge.
|
GiveUp
|
The GiveUp timer determines the amount of time a local host will wait for an acknowledgement (or other appropriate reply) of a transmitted message after the the maximum number of retransmissions has been reached. If the timer expires, the local host gives up retransmission attempts and declares the connection dead.
|
PmtuAger
|
The PMTU age timer is a time interval for how often TCP reestimates the path MTU with a larger maximum segment size (MSS). When the age timer is used, TCP path MTU becomes a dynamic process. If the MSS is smaller than what the peer connection can manage, a larger MSS is tried every time the age timer expires. The discovery process stops when the send MSS is as large as the peer negotiated or the timer has been manually disabled by setting it to infinite.
|
The following lines of output display the sequence numbers that TCP uses to ensure sequenced, reliable transport of data. The local host and remote host each use these sequence numbers for flow control and to acknowledge receipt of datagrams.
iss: 67317172 snduna: 67317228 sndnxt: 67317228 sndwnd: 4096
irs: 1064896000 rcvnxt: 1064897597 rcvwnd: 2144 delrcvwnd: 0
Table 171 describes the fields shown in the preceding display.
Table 171 show tcp Field Descriptions—Sequence Numbers
Field
|
Description
|
iss
|
Initial send sequence number.
|
snduna
|
Last send sequence number that the local host sent but for which it has not received an acknowledgment.
|
sndnxt
|
Sequence number that the local host will send next.
|
sndwnd
|
TCP window size of the remote host.
|
irs
|
Initial receive sequence number.
|
rcvnxt
|
Last receive sequence number that the local host has acknowledged.
|
rcvwnd
|
TCP window size of the local host.
|
delrcvwnd
|
Delayed receive window—data that the local host has read from the connection but has not yet subtracted from the receive window that the host has advertised to the remote host. The value in this field gradually increases until it is larger than a full-sized packet, at which point it is applied to the rcvwnd field.
|
The following lines of output display values that the local host uses to keep track of transmission times so that TCP can adjust to the network that it is using.
SRTT: 317 ms, RTTO: 900 ms, RTV: 133 ms, KRTT: 0 ms
minRTT: 4 ms, maxRTT: 300 ms, ACK hold: 300 ms
Flags: higher precedence, idle user, retransmission timeout
Table 172 describes the significant fields shown in the preceding output.
Table 172 show tcp Field Descriptions—Line Beginning with "SRTT"
Field
|
Description
|
SRTT
|
A calculated smoothed round-trip timeout.
|
RTTO
|
Round-trip timeout.
|
RTV
|
Variance of the round-trip time.
|
KRTT
|
New round-trip timeout (using the Karn algorithm). This field separately tracks the round-trip time of packets that have been re-sent.
|
minRTT
|
Smallest recorded round-trip timeout (hard-wire value used for calculation).
|
maxRTT
|
Largest recorded round-trip timeout.
|
ACK hold
|
Time for which the local host will delay an acknowledgment in order to piggyback data on it.
|
Flags
|
Properties of the connection.
|
Note
For more information on the preceding fields, refer to Round Trip Time Estimation, P. Karn & C. Partridge, ACM SIGCOMM-87, August 1987.
The following lines of output display the number of datagrams that are transported with data.
Datagrams (max data segment is 536 bytes):
Rcvd: 41 (out of order: 0), with data: 34, total data bytes: 1596
Sent: 57 (retransmit: 1), with data: 35, total data bytes: 55
Table 173 describes the significant fields shown in the last lines of the show tcp command output.
Table 173 show tcp Field Descriptions—Last Section of Output
Field
|
Description
|
Rcvd
|
Number of datagrams that the local host has received during this connection (and the number of these datagrams that were out of order).
|
with data
|
Number of these datagrams that contained data.
|
total data bytes
|
Total number of bytes of data in these datagrams.
|
Sent
|
Number of datagrams that the local host sent during this connection (and the number of these datagrams that needed to be re-sent).
|
with data
|
Number of these datagrams that contained data.
|
total data bytes
|
Total number of bytes of data in these datagrams.
|
The following is sample output from the show tcp tcb command that displays detailed information by hexidecimal address about an ECN-enabled connection:
Router# show tcp tcb 62CD2BB8
Connection state is LISTEN, I/O status: 1, unread input bytes: 0
Connection is ECN enabled
Local host: 10.10.10.1, Local port: 179
Foreign host: 10.10.10.2, Foreign port: 12000
Enqueued packets for retransmit: 0, input: 0 mis-ordered: 0 (0 bytes)
Event Timers (current time is 0x4F31940):
Timer Starts Wakeups Next
iss: 0 snduna: 0 sndnxt: 0 sndwnd: 0
irs: 0 rcvnxt: 0 rcvwnd: 4128 delrcvwnd: 0
SRTT: 0 ms, RTTO: 2000 ms, RTV: 2000 ms, KRTT: 0 ms
minRTT: 60000 ms, maxRTT: 0 ms, ACK hold: 200 ms
Flags: passive open, higher precedence, retransmission timeout
TCB is waiting for TCP Process (67)
Datagrams (max data segment is 516 bytes):
Rcvd: 6 (out of order: 0), with data: 0, total data bytes: 0
Sent: 0 (retransmit: 0, fastretransmit: 0), with data: 0, total data
Related Commands
Command
|
Description
|
show tcp brief
|
Displays a concise description of TCP connection endpoints.
|
show tcp brief
To display a concise description of TCP connection endpoints, use the show tcp brief command in EXEC mode.
show tcp brief [all]
Syntax Description
all
|
(Optional) Displays status for all endpoints. Without this keyword, endpoints in the LISTEN state are not shown.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
11.2
|
This command was introduced.
|
Examples
The following is sample output from the show tcp brief command while a user has connected into the system via Telnet:
TCB Local Address Foreign Address (state)
609789AC Router.cisco.com.23 cider.cisco.com.3733 ESTAB
Table 174 describes the significant fields shown in the display.
Table 174 show tcp brief Field Descriptions
Field
|
Description
|
TCB
|
An internal identifier for the endpoint.
|
Local Address
|
The local IP address and port.
|
Foreign Address
|
The foreign IP address and port (at the opposite end of the connection).
|
(state)
|
The state of the connection. States are described in the syntax description of the show tcp command.
|
Related Commands
Command
|
Description
|
show tcp
|
Displays the status of TCP connections.
|
show tech-support
To display general information about the router when it reports a problem, use the show tech-support command in privileged EXEC mode.
show tech-support [page] [password] [cef | ipmulticast | isis | mpls | ospf [process-ID | detail] |
rsvp]
Syntax Description
page
|
(Optional) Causes the output to display a page of information at a time. Use the return key to display the next line of output or use the space bar to display the next page of information. If not used, the output scrolls (that is, does not stop for page breaks).
|
password
|
(Optional) Leaves passwords and other security information in the output. If not used, passwords and other security-sensitive information in the output are replaced with the label "<removed>" (this is the default).
|
cef
|
(Optional) Displays show command output specific to Cisco Express Forwarding (CEF).
|
ipc
|
(Optional) Displays show command output specific to Inter-Process Communications (IPC).
|
ipmulticast
|
(Optional) Displays show command output related to the IP Multicast configuration, including Protocol Independent Multicast (PIM) information, Internet Group Management Protocol (IGMP) information, and Distance Vector Multicast Routing Protocol (DVMRP) information.
|
isis
|
(Optional) Displays show command output specific to Connectionless Network Service (CLNS) and Intermediate System-to-Intermediate System Protocol (ISIS).
|
mpls
|
(Optional) Displays show command output specific to Multilayer Switching Protocol (MPLS) forwarding and applications.
|
ospf [ process-ID | detail]
|
(Optional) Displays show command output specific to Open Shortest Path First Protocol (OSPF) networking.
|
rsvp
|
(Optional) Displays show command output specific to Resource Reservation Protocol (RSVP) networking.
|
Defaults
The output scrolls without page breaks.
Passwords and other security information are removed from the output.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
11.2
|
This command was introduced.
|
11.3(7), 11.2(16)
|
The output for this command was expanded to show additional information for boot, bootflash, context, and traffic for all enabled protocols.
|
12.0
|
The output for this command was expanded to show additional information for boot, bootflash, context, and traffic for all enabled protocols. The cef, ipmulticast, isis, mlps, and ospf keywords were added to this command.
|
12.2(13)T
|
Support for AppleTalk EIGRP, Apollo Domain, Banyan VINES, Novell Link-State Protocol, and XNS was removed from Cisco IOS software.
|
12.3(4)T
|
The output of this command was expanded to include the output from the show inventory command.
|
Usage Guidelines
The show tech-support command is useful for collecting a large amount of information about your routing device for troubleshooting purposes. The output of this command can be provided to technical support representatives when reporting a problem.
Note
This command can generate a very large amount of output. You may want to redirect the output to a file using the show inventory | redirect url command syntax extension. Redirecting the output to a file also makes sending this output to your technical support representative easier. See the command documentation for show <command> | redirect for more information on this option.
The show tech-support command displays the output of a number of show commands at once. The output from this command will vary depending on your platform and configuration. For example, access servers will display voice-related show output. Additionally, the show protocol traffic commands will be displayed for only the protocols enabled on your device. The output of the show tech-support command can include the output of the following commands:
•
show apollo traffic
•
show appletalk traffic
•
show bootflash
•
show bootvar
•
show buffers
•
show cdp neighbors
•
show cef
•
show clns traffic
•
show context
•
show controllers
•
show decnet traffic
•
show interfaces
•
show ip cef
•
show ip interface
•
show ip traffic
•
show isis
•
show mpls
•
show novell traffic
•
show processes cpu
•
show processes memory
•
show running-config
•
show stacks
•
show version
•
show vines traffic
•
show xns traffic
•
show file systems
•
dir nvram:
•
show disk0: all
•
show process cpu
•
show pci controller
Use of the optional cef, ipmulticast, ipc, isis, mpls , ospf, or rsvp keywords provides a way to display a number of show commands specific to a particular protocol or process in addition to the show commands listed previously.
For example, if your TAC support representative suspects that you may have a problem in your Cisco Express Forwarding (CEF) configuration, you may be asked to provide the output of the show tech-support cef command. The show tech-support [page] [password] cef command will display the output from the following commands in addition to the output for the standard show tech-support command:
•
show ip cef summary
•
show adjacency summary
•
show ip cef events summary
•
show ip cef inconsistency records detail
•
show cef interface
•
show cef events
•
show cef timers
•
show interfaces stats
•
show cef drop
•
show cef not-cef-switched
Examples
For a sample display of the output from the show tech-support command, refer to the documentation for the show commands listed in the "Usage Guidelines" section.
Related Commands
Command
|
Description
|
show bootflash
|
Displays the contents of boot Flash memory.
|
show bootvar
|
Displays the contents of the BOOT environment variable, the name of the configuration file pointed to by the CONFIG_FILE environment variable, the contents of the BOOTLDR environment variable, and the configuration register setting.
|
show buffers
|
Displays statistics for the buffer pools on the network server.
|
show clns traffic
|
Displays a list of the CLNS packets this router has seen.
|
show <command> | redirect
|
Redirects the output of any show command to a file.
|
show context
|
Displays context data.
|
show controllers
|
Displays information that is specific to the hardware.
|
show controllers tech-support
|
Displays general information about a VIP card for problem reporting.
|
show decnet traffic
|
Displays the DECnet traffic statistics (including datagrams sent, received, and forwarded).
|
show interfaces
|
Displays ALC information.
|
show inventory
|
Displays the product inventory listing and UDI of all Cisco products installed in the networking device.
|
show ip traffic
|
Displays statistics about IP traffic.
|
show processes cpu
|
Displays information about the active processes.
|
show processes memory
|
Displays the amount of memory used.
|
show region
|
Displays region manager status information.
|
show running-config
|
Displays the current configuration of your routing device.
|
show stacks
|
Displays the stack usage of processes and interrupt routines.
|
show version
|
Displays the configuration of the system hardware, the software version, the names and sources of configuration files, and the boot images.
|
show time-range
To display information about configured time ranges, use the show time-range command in user EXEC or privileged EXEC mode.
show time-range
Syntax Description
This command has no arguments or keywords.
Command Default
This command has no default behavior.
Command Modes
User EXEC and Privileged EXEC
Command History
Release
|
Modification
|
12.2
|
This command was introduced.
|
12.2(33)SRA
|
This command was integrated into Cisco IOS Release 12.33(SRA).
|
Usage Guidelines
Use this command to display configured time ranges.
Examples
The following is sample output for the show time-range command. The word (active) indicates that the time range is in effect at that moment; otherwise, the output will indicate (inactive).
time-range entry: test (active)
absolute start 00:00 01 January 2006 end 23:59 31 December 2006
periodic weekdays 8:00 to 20:00
Related Commands
Command
|
Description
|
time-range
|
Specifies a time range by name and allows you configure a range during which an access list, for example, is active.
|
show usb controllers
To display USB host controller information, use the show usb controllers command in Privileged EXEC mode.
show usb controllers [controller-number]
Syntax Description
controller-number
|
(Optional) Displays information only for the specified controller.
|
Defaults
Information about all controllers on the system are displayed.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.3(14)T
|
This command was introduced.
|
Usage Guidelines
Use the show usb controllers command to display content such as controller register specific information, current asynchronous buffer addresses, and period scheduling information. You can also use this command to verify that copy operations are occurring successfully onto a USB flash module.
Examples
The following example is sample output from the show usb controller command:
Router# show usb controllers
Controller Specific Information:
Hardware Interrupt Status:0x24
Hardware Interrupt Enable:0x80000040
Hardware Interrupt Disable:0x80000040
Frame Interval:0x27782EDF
Hardware Configuration:0x3029
Direct Address Length:0x80A00
ATL PTD Skip Map:0xFFFFFFFF
ATL Current Active PTD:0x0
ATL Threshold Timeout:0xFF
Transfer Completion Codes:
No Response :0 Overrun :0
Buffer Overrun :0 Buffer Underrun :0
Canceled Transfers :2 Control Timeout :0
Interrupt Transfer :0 Bulk Transfer :0
Isochronous Transfer :0 Control Transfer:0
Interrupt Transfer :0 Bulk Transfer :26
Isochronous Transfer :0 Control Transfer:894
Enumeration Failures :0 No Class Driver Found:0
USB MSCD SCSI Class Driver Counters:
Good Status Failures :3 Command Fail :0
Good Status Timed out:0 Device not Found:0
Device Never Opened :0 Drive Init Fail :0
Illegal App Handle :0 Bad API Command :0
Invalid Unit Number :0 Invalid Argument:0
Application Overflow :0 Device in use :0
Control Pipe Stall :0 Malloc Error :0
Device Stalled :0 Bad Command Code:0
Device Detached :0 Unknown Error :0
USB Aladdin Token Driver Counters:
Token Inserted :1 Token Removed :0
Send Insert Msg Fail :0 Response Txns :434
Dev Entry Add Fail :0 Request Txns :434
Dev Entry Remove Fail:0 Request Txn Fail:0
Response Txn Fail :0 Command Txn Fail:0
USB Flash File System Counters:
Flash Disconnected :0 Flash Connected :1
Flash Device Fail :0 Flash Ok :1
Flash startstop Fail :0 Flash FS Fail :0
USB Secure Token File System Counters:
Token Inserted :1 Token Detached :0
Token FS success :1 Token FS Fail :0
Token Max Inserted :0 Create Talker Failures:0
Token Event :0 Destroy Talker Failures:0
Watched Boolean Create Failures:0
show usb device
To display USB device information, use the show usb device command in privileged EXEC mode.
show usb device [controller-ID [device-address]]
Syntax Description
controller-ID
|
(Optional) Displays information only for the devices under the specified controller.
|
device-address
|
(Optional) Displays information only for the device with the specified address.
|
Defaults
Information for all devices attached to the system are displayed.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.3(14)T
|
This command was introduced.
|
Usage Guidelines
Use the show usb device command to display information for either a USB flash drive or a USB eToken, as appropriate.
Examples
The following example is sample output from the show usb device command:
Serial Number:0750D84030316868
USB Version Compliance:2.0
Max. Packet Size of Endpoint Zero:64
Number of Configurations:1
Transfer Direction:Device to Host
Transfer Direction:Host to Device
Description:eToken Pro 4254
USB Version Compliance:1.0
Max. Packet Size of Endpoint Zero:8
Number of Configurations:1
Table 175 describes the significant fields shown in the display.
Table 175 show usb device Field Descriptions
Field
|
Description
|
Device handle
|
Internal memory handle allocated to the device.
|
Device Class code
|
The class code supported by the device.
This number is allocated by the USB-IF. If this field is reset to 0, each interface within a configuration specifies its own class information, and the various interfaces operate independently. If this field is set to a value between 1 and FEH, the device supports different class specifications on different interfaces, and the interfaces may not operate independently. This value identifies the class definition used for the aggregate interfaces. If this field is set to FFH, the device class is vendor-specific.
|
Device Subclass code
|
The subclass code supported by the device. This number is allocated by the USB-IF.
|
Device Protocol
|
|