-
Cisco IOS Configuration Fundamentals and Network Management Command Reference, Release 12.3
-
Introduction
-
CFR Commands: absolute -- clock timezone
-
CFR Commands: clock update-calendar -- escape-character
-
CFR Commands: exception core-file -- ip ftp passive
-
CFR Commands: ip ftp password -- lsr-path
-
CFR Commands: memory sanity -- periodic
-
CFR Commands: ping -- service sequence numbers
-
CFR Commands: service slave-log -- show
tee -
CFR Commands: show context -- show ip http server
-
CFR Commands: show kron schedule -- show rtr enhanced-history
-
12.3 CF CR Commands: show rtr distributions-statistics -- snmp-server enable informs
-
CFR Commands: snmp-server enable traps -- statistics-distribution-interval
-
CFR Commands: stopbits -- ttl ip
-
CFR Commands: type dhcp - xsm vdm
-
CFR Appendix: ASCII Character Set and Hex Values
-
Table Of Contents
show rtr distributions-statistics
show rtr enhanced-history collection-statistics
show rtr enhanced-history distribution-statistics
show snmp mib notification-log
snmp mib notification-log default
snmp mib notification-log default disable
snmp mib notification-log globalageout
snmp mib notification-log globalsize
show rtr distributions-statistics
To display statistic distribution information (captured response times) for all Service Assurance Agent (SAA) operations or the specified operation, use the show rtr distributions-statistics command in EXEC mode.
show rtr distributions-statistics [operation] [tabular | full]
Syntax Description
Defaults
Tabular format for all operations is displayed.
Command Modes
EXEC
Command History
11.2
This command was introduced.
12.3(01)
This command integrated in Release 12.3
12.3(14)T
This command was replaced by the show ip sla monitor statistics command.
Usage Guidelines
The distributions statistics consist of the following:
•
The sum of completion times (used to calculate the mean)
•
•
•
You can also use the show rtr collection-statistics and show rtr totals-statistics commands to display additional statistical information.
For enhanced-history distribution statistics, see the show rtr enhanced-history distribution-statistics command.
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-statisticsCaptured StatisticsMultiple Lines per EntryLine 1Entry = Entry NumberStartT = Start Time of Entry (hundredths of seconds)Pth = Path IndexHop = Hop in Path IndexDst = Time Distribution IndexComps = Operations CompletedOvrTh = Operations Completed Over ThresholdsSumCmp = Sum of Completion Times (milliseconds)Line 2SumCmp2L = 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 SumCmpSumCmp2L SumCmp2H TMax TMin1 17417068 1 1 1 2 0 1288192 0 64 64The following example shows the output as it appears on a single line:
Entry StartT Pth Hop Dst Comps OvrTh SumCmp SumCmp2L SumCmp2H TMax TMin10 3581 1 1 1 0 0 0 0 0 0 0Related Commands
show rtr enhanced-history collection-statistics
To display enhanced history statistics for all collected history buckets for the specified Service Assurance Agent (SAA) operation, use the show rtr enhanced-history collection-statistics command in user EXEC or privileged EXEC mode.
show rtr enhanced-history collection-statistics [operation-number] [interval seconds]
Syntax Description
Command Modes
User EXEC
Privileged EXEC
Command History
12.2(15)T
This command was introduced in Early Deployment Release 12.2T.
12.3(01)
This command was integrated in Release 12.3.
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 SAA RTR configuration mode 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 aggregation interval 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 SAA operations.
Output for SLM Controller Operation
Router# show rtr configuration 1 | include TypeType of operation to perform: slm controllerReaction Type: NoneRouter# show running-config | begin rtr...rtr 1type slm controller T1 0enhanced-history interval 900 buckets 100rtr schedule 1 start-time now life forever...Router# show rtr enhanced-history collection-statistics 1Entry number: 1Aggregation Interval: 900Bucket Index: 1Aggregation start time 00:15:00.003 UTC Thur May 1 2003Target Address:Number of failed operations due to a Disconnect: 0Number of failed operations due to a Timeout: 0Number of failed operations due to a Busy: 0Number of failed operations due to a No Connection: 0Number of failed operations due to an Internal Error: 0Number of failed operations due to a Sequence Error: 0Number of failed operations due to a Verify Error: 0Ds1StatRxLineStatus: 16385Ds1StatRxBPVs: 0, Ds1StatRxCrcFrameErrors: 0Ds1StatRxErrSecs: 0, Ds1StatRxSevereErrSecs: 0Ds1StatRxUnavailSecs: 0, Ds1StatRxBurstyErrSecs: 0Sample Index = 1Bucket Index: 2...Table 103 describes the significant fields shown in the display.
Output for SLM Frame Relay OperationRouter# show rtr configuration 2 | include TypeType of operation to perform: Slm Frame-relay InterfaceReaction Type: NoneRouter#Router# show rtr ennhanced-history collection-statistics 2Entry number: 2Aggregation Interval: 900Bucket Index: 1Aggregation start time 00:15:00.003 UTC Mon Mar 1 1993Target Address:Number of failed operations due to a Disconnect: 0Number of failed operations due to a Timeout: 0Number of failed operations due to a Busy: 0Number of failed operations due to a No Connection: 0Number of failed operations due to an Internal Error: 0Number of failed operations due to a Sequence Error: 0Number of failed operations due to a Verify Error: 0LinkState :1Tx Total Frames: 24 Rx Total Frames: 24Tx Total Octets: 312 Rx Total Octets: 344Tx FCSAlignErrors: 0 Rx FCSAlignErrors: 0Tx Aborted Frames: 0 Rx Aborted Frames: 0Tx Long Frames: 0 Rx Long Frames: 0Tx Short Frames: 0 Rx Short Frames: 0Tx MaxThroughput: 88 Rx MaxThroughput: 152Tx MaxUtilization: 0 Rx MaxUtilization: 0Tx MaxFramesSec: 1 Rx MaxFramesSec: 1UnavailSecs: 0 Drop Events: 0Tx OverFlowOctets: 0 Rx OverFlowOctets: 0Tx Burst Percent1(sec): 238 Rx Burst Percent1(sec): 238Tx Burst Percent2(sec): 0 Rx Burst Percent2(sec): 0Tx Burst Percent3(sec): 0 Rx Burst Percent3(sec): 0Tx Burst Percent4(sec): 0 Rx Burst Percent4(sec): 0Tx Burst Percent5(sec): 0 Rx Burst Percent5(sec): 0Sample Index = 1Bucket Index: 2...Table 104 describes the significant fields shown in the display. In the output "Tx" indicates "transmitted," "Rx" indicates "received."
show rtr enhanced-history distribution-statistics
To display enhanced history distribution statistics for Service Assurance Agent (SAA) 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
Command Modes
User Exec
Privileged Exec
Command History
Usage Guidelines
Enhanced history statistics (recorded in milliseconds instead of centiseconds) are enabled using the enhanced-history command when configuring the SAA operation.
The distribution statistics consist of the following:
•
•
•
•
You can also use the following commands to display additional statistics or history information, or to view the status of the operation:
•
•
Tip
Examples
The following is sample output from the show rtr enhanced-history distribution-statistics command for an SLM Frame Relay Circuit (Slm Frame-relay Pvc) operation. Please note the following:
•
•
•
•
Router# show rtr configuration 3 | include TypeType of operation to perform: Slm Frame-relay PvcReaction Type: NoneRouter# show rtr enhanced-history distribution-statistics 3Point by point Enhanced HistoryEntry = Entry NumberInt = Aggregation Interval (seconds)BucI = Bucket IndexStartT = Aggregation Start TimePth = Path indexHop = Hop in path indexComps = Operations completedOvrTh = Operations completed over thresholdsSumCmp = 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 TMin3 900 1 257850000 1 1 3 0 43 617 0 15 143 900 2 258750002 1 1 3 0 45 677 0 16 143 900 3 259650000 1 1 3 0 44 646 0 15 143 900 4 260550002 1 1 3 0 42 594 0 15 123 900 5 261450003 1 1 3 0 42 590 0 15 133 900 6 262350001 1 1 3 0 46 706 0 16 153 900 7 263250003 1 1 3 0 46 708 0 16 14...
Related Commands
show rtr group schedule
To display the group schedule details of the Service Assurance Agent (SAA) operations, use the show rtr group schedule command in user EXEC or privileged EXEC mode.
show rtr group schedule [group-operation-number]
Syntax Description
Command Modes
User EXEC
Privileged EXEC
Command History
Note
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 SAA operations are multiple scheduled (TRUE):
Router# show rtr group scheduleMulti-Scheduling Configuration:Group Entry Number: 1Probes to be scheduled: 2,3,4,9-30,89Schedule period :60Group operation frequency: 30Multi-scheduled: TRUEThe 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 scheduleGroup Entry Number: 1Probes to be scheduled: 3,4,6-10Total number of probes: 7Schedule period: 20Group operation frequency: Equals schedule periodStatus of entry (SNMP RowStatus): ActiveNext Scheduled Start Time: Start Time already passedLife (seconds): 3600Entry Ageout (seconds): neverTable 106 describes the significant fields shown in the displays.
Related Commands
show rtr history
To display history collected for all Service Assurance Agent (SAA) operations or for a specified operation, use the show rtr history command in EXEC mode.
show rtr history [operation-number] [tabular | full]
Syntax Description
Defaults
Tabular format history for all operations is displayed.
Command Modes
EXEC
Command History
Usage Guidelines
Table 131 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.
Examples
The following is sample output from the show rtr history command in tabular format:
Router# show rtr historyPoint by point HistoryMultiple Lines per EntryLine 1Entry = Entry NumberLifeI = Life IndexBucketI = Bucket IndexSampleI = Sample IndexSampleT = Sample Start TimeCompT = Completion Time (milliseconds)Sense = Response Return CodeLine 2 has the Target AddressEntry LifeI BucketI SampleI SampleT CompT Sense2 1 1 1 17436548 16 1AB 45 A0 162 1 2 1 17436551 4 1AC 12 7 292 1 2 2 17436551 1 1AC 12 5 222 1 2 3 17436552 4 1AB 45 A7 222 1 2 4 17436552 4 1AB 45 A0 16Related Commands
show rtr configuration
Displays configuration values including all defaults for all SAA operations or the specified operation.
show rtr operational-state
Note
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
Defaults
Displays output for all running IP SLAs operations.
Command Modes
EXEC
Command History
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-stateCurrent Operational StateEntry Number: 3Modification Time: *22:15:43.000 UTC Sun Feb 11 2001Diagnostics Text:Last Time this Entry was Reset: NeverNumber of Octets in use by this Entry: 1332Number of Operations Attempted: 2Current Seconds Left in Life: 3511Operational State of Entry: activeLatest Completion Time (milliseconds): 544Latest Operation Start Time: *22:16:43.000 UTC Sun Feb 11 2001Latest Oper Sense: okLatest Sense Description: 200 OKTotal RTT: 544DNS RTT: 12TCP Connection RTT: 28HTTP Transaction RTT: 504HTTP Message Size: 9707The 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 1Entry number: 1Modification time: 13:18:38.012 PST Mon Jun 24 2002Number of Octets Used by this Entry: 10392Number of operations attempted: 2Number of operations skipped: 0Current seconds left in Life: ForeverOperational state of entry: ActiveLast time this entry was reset: NeverConnection loss occurred: FALSETimeout occurred: FALSEOver thresholds occurred: FALSELatest RTT (milliseconds): 2Latest operation start time: *13:18:42.896 PST Mon Jun 24 2002Latest operation return code: OKVoice Scores:ICPIF Value: 0 MOS score: 0RTT Values:NumOfRTT: 61 RTTAvg: 2 RTTMin: 2 RTTMax: 3RTTSum: 123 RTTSum2: 249Packet Loss Values:PacketLossSD: 0 PacketLossDS: 0PacketOutOfSequence: 0 PacketMIA: 0 PacketLateArrival: 0InternalError: 0 Busies: 0 PacketSkipped: 39 <<<<<<==========Jitter Values:MinOfPositivesSD: 1 MaxOfPositivesSD: 1NumOfPositivesSD: 1 SumOfPositivesSD: 1 Sum2PositivesSD: 1MinOfNegativesSD: 1 MaxOfNegativesSD: 1NumOfNegativesSD: 1 SumOfNegativesSD: 1 Sum2NegativesSD: 1MinOfPositivesDS: 0 MaxOfPositivesDS: 0NumOfPositivesDS: 0 SumOfPositivesDS: 0 Sum2PositivesDS: 0MinOfNegativesDS: 0 MaxOfNegativesDS: 0NumOfNegativesDS: 0 SumOfNegativesDS: 0 Sum2NegativesDS: 0Interarrival jitterout: 0 Interarrival jitterin: 0One Way Values:NumOfOW: 0OWMinSD: 0 OWMaxSD: 0 OWSumSD: 0 OWSum2SD: 0OWMinDS: 0 OWMaxDS: 0 OWSumDS: 0 OWSum2DS: 0The 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 108 describes the significant fields shown in this output.
Related Commands
show rtr configuration
Displays configuration values including all defaults for all IP SLAs operations or the specified operation.
show rtr reaction-trigger
To display the reaction trigger information for all Service Assurance Agent (SAA) operations or the specified operation, use the show rtr reaction-trigger command in EXEC mode.
show rtr reaction-trigger [operation-number] [tabular | full]
Syntax Description
Defaults
Full format for all operations
Command Modes
EXEC
Command History
11.2
This command was introduced.
12.3
This command was integrated in Release 12.3.
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 in full format:
Router# show rtr reaction-trigger 1Reaction TableEntry Number: 1Target Entry Number: 2Status of Entry (SNMP RowStatus): activeOperational State: pendingRelated Commands
show rtr configuration
Displays configuration values including all defaults for all SAA operations or the specified operation.
show rtr responder
To display Service Assurance Agent (SAA) Response Time Report (RTR) 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
12.0(3)T
This command was introduced.
12.3
This command was integrated in Release 12.3.
Usage Guidelines
Use the show rtr responder command to display information about recent sources of SAA 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 responderRTR Responder is: EnabledNumber of control message received: 19 Number of errors: 1Recent sources: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]Recent error sources:4.0.0.1 [19:10:49.023 UTC Sat Dec 2 1995] RTT_AUTH_FAILRelated Commands
show rtr totals-statistics
To display the total statistical values (accumulation of error counts and completions) for all Service Assurance Agent (SAA) operations or the specified operation, use the show rtr totals-statistics command in EXEC mode.
show rtr totals-statistics [number] [tabular | full]
Syntax Description
Defaults
Full format for all operations
Command Modes
EXEC
Command History
Usage Guidelines
The total statistics consist of the following items:
•
•
•
•
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-statisticsStatistic TotalsEntry Number: 1Start Time Index: *17:15:41.000 UTC Thu May 16 1996Age of Statistics Entry (hundredths of seconds): 48252Number of Initiations: 10Related Commands
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
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
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 1Building configuration...Current configuration:!interface Serial1no ip addressno ip directed-broadcastno ip route-cacheno ip mroute-cacheshutdownendThe 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 linenumBuilding configuration...Current configuration : 104 bytes1 : !2 : interface Ethernet0/03 : ip address 10.4.2.63 255.255.255.04 : no ip route-cache5 : no ip mroute-cache6 : endThe 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 1010 : boot-start-marker11 : boot-end-marker12 : !13 : no logging buffered14 : enable password #####15 : !16 : spe 1/0 1/717 : firmware location bootflash:mica-modem-pw.2.7.1.0.bin18 : !19 : !20 : resource-pool disable21 : !22 : no aaa new-model23 : ip subnet-zero24 : ip domain name cisco.com25 : ip name-server 172.16.11.4826 : ip name-server 172.16.2.13327 : !28 : !29 : isdn switch-type primary-5ess30 : !...126 : endRelated Commandsdoc-rtr53-02#show running-conf linenum | begin 10
Related Commands 10 : boot-start-marker
Related Commands 11 : boot-end-marker
Related Commands 12 : !
Related Commands 13 : no logging buffered
Related Commands 14 : enable password #1writer
Related Commands 15 : !
Related Commands 16 : spe 1/0 1/7
Related Commands 17 : firmware location bootflash:mica-modem-pw.2.7.1.0.bin
Related Commands 18 : !
Related Commands 19 : !
Related Commands 20 : resource-pool disable
Related Commands 21 : !
Related Commands 22 : no aaa new-model
Related Commands 23 : ip subnet-zero
Related Commands 24 : ip domain name cisco.com
Related Commands 25 : ip name-server 172.16.11.48
Related Commands 26 : ip name-server 172.16.2.133
Related Commands 27 : !
Related Commands 28 : !
Related Commands 29 : isdn switch-type primary-5ess
Related Commands 30 : !
Related Commands 31 : !
Related Commands
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
Defaults
Displays all map-class configuration in the running configuration file.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the show running-config map-class command to display the following information from the running configuration file:
•
•
•
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-classBuilding configuration...Current configuration:!map-class frame-relay cir60frame-relay bc 16000frame-relay adaptive-shaping becn!map-class frame-relay cir70no frame-relay adaptive-shapingframe-relay priority-group 2!map-class atm vc100atm aal5mux!map-class dialer dialer1dialer idle-timeout 10endAll Frame Relay Map Classes Example
The following example displays all Frame Relay map classes on the router:
Router# show running-config map-class frame-relayBuilding configuration...Current configuration:!map-class frame-relay cir60frame-relay bc 16000frame-relay adaptive-shaping becn!map-class frame-relay cir70no frame-relay adaptive-shapingframe-relay priority-group 2endA 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 linenumBuilding configuration...Current configuration:1 : !2 : map-class frame-relay boy3 : no frame-relay adaptive-shaping4 : frame-relay cir 10005 : endRelated Commands
show saa apm cache
To display the amount of memory available in the Service Assurance Agent (SAA) 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
12.2(2)T
This command was introduced.
12.3(01)
This command was integrated in Release 12.3.
Usage Guidelines
SAA APM script and scheduler files are kept in an area of system memory called the SAA APM cache.
Examples
The following is sample output from the show saa apm cache command:
Router# show saa apm cacheCache Size (bytes): 100000Cache used (bytes): 6849TimeCreated TimeAccessed Size Ref Loc Type SBit FileName03/21 13:31:25 03/21 13:31:48 1170 0 1 SCR 0 user/scripts/ldap-rem.scr03/21 13:31:23 03/21 13:31:48 38 0 1 DAT 0 user/data/ldap-rem.dat03/21 13:31:22 03/21 13:31:27 69 1 0 DAT 0 user/data/ldap.dat03/21 13:31:20 03/21 13:31:27 1513 1 0 SCR 0 user/scripts/ldap.scr03/21 13:31:19 03/21 13:31:27 2500 1 0 SCH 0 user/scheduler/master.sch03/21 13:31:17 03/21 13:31:27 256 1 0 CFG 0 apm.cfg.103/21 13:31:17 03/21 13:31:17 568 1 0 CFG 0 user/config/ldap.cf03/20 14:29:13 03/20 14:29:36 735 0 1 SCR 0 user/scripts/udp-rem.scrTable 109 describes the significant fields shown in the display.
Related Commands
show saa apm information
To display details about Service Assurance Agent (SAA) 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
Examples
The following is sample output from the show saa apm information command:
Router# show saa apm informationService Assurance Agent: Application Performance MonitorAPM Engine Version: 1.0Max Number of oper supported: 50Number of configurable oper: 50Number of oper configured: 0Number of files in cache: 0Cache Size (bytes): 100000Cache used (bytes): 0APM low memory water-mark: 6708828Related Commands
saa apm lowWaterMark
Specifies the lowest amount of free memory that must be available on the system to allow additional SAA APM operations to be configured.
show saa apm operation
To display details about Service Assurance Agent (SAA) Application Performance Monitor (APM) operation, use the show saa apm operation command in EXEC mode.
show saa apm operation [operation-number]
Syntax Description
Defaults
Information for all APM operations is displayed.
Command Modes
EXEC
Command History
Examples
The following is sample output from the show saa apm operation command:
Router# show saa apm operationOperation Information:Operation ID: 1234567Owner: CLIControlFile URL: ftp://user:password@saa-nms/apm/config/smtp-1000.cfgSNMP Row Status: activeLatest Operation Time: *08:13:40.000 UTC Mon Oct 08 2001Latest Operation Status: 0show saa apm results
To display the accumulated data for Service Assurance Agent (SAA) 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
Usage Guidelines
SAA APM script and scheduler files are kept in an area of system memory called the SAA APM cache.
Examples
The following is sample output from the show saa apm results command:
Router# show saa apm resultsCache Size (bytes): 100000Cache used (bytes): 14188File Name TimeCreated TimeAccessed ref Type stickyapm/data/ldap-13.dat 13:37:20 13:37:25 1 DAT 0apm.cf.9 13:37:18 13:37:25 1 CFG 0apm/config/ldap-13.cf 13:37:18 00:00:00 1 CFG 0apm/data/ldap-12.dat 13:37:15 13:37:20 1 DAT 0apm.cf.8 13:37:14 13:37:20 1 CFG 0apm/config/ldap-12.cf 13:37:14 00:00:00 1 CFG 0apm/data/ldap-11.dat 13:37:11 13:37:16 1 DAT 0apm.cf.7 13:37:11 13:37:16 1 CFG 0apm/config/ldap-11.cf 13:37:11 00:00:00 1 CFG 0apm/scripts/ldap.scr 13:37:07 13:37:29 3 SCR 0apm/data/iptv-2.dat 13:36:49 13:36:54 1 DAT 0apm/config/iptv-2.cf 13:36:48 00:00:00 1 CFG 0apm/scripts/iptv.scr 13:36:47 13:37:08 1 SCR 0apm/scheduler/master.sch 13:36:45 13:37:34 4 SCH 0Table 110 describes the significant fields shown in the display.
Related Commands
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
Command Modes
User EXEC
Privileged EXECCommand History
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
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.
Router# show version..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.
Router# show version..20480K bytes of Flash PCMCIA card at slot 1 (Sector size 128K).
Note
Examples
The following example displays information about slot 0. The output is self-explanatory.
Router# show slotPCMCIA Slot0 flash directory:File Length Name/status1 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.
Router# show slot allPartition Size Used Free Bank-Size State Copy Mode1 20223K 10821K 9402K 4096K Read/Write DirectPCMCIA Slot0 flash directory:File Length Name/statusaddr fcksum ccksum1 11081464 c3660-bin-mz.123-9.3.PI5b0x40 0x5EA3 0x5EA3[11081528 bytes used, 9627844 available, 20709372 total]20480K bytes of processor board PCMCIA Slot0 flash (Read/Write)Chip Bank Code Size Name1 1 89A0 2048KB INTEL 28F016SA2 1 89A0 2048KB INTEL 28F016SA1 2 89A0 2048KB INTEL 28F016SA2 2 89A0 2048KB INTEL 28F016SA1 3 89A0 2048KB INTEL 28F016SA2 3 89A0 2048KB INTEL 28F016SA1 4 89A0 2048KB INTEL 28F016SA2 4 89A0 2048KB INTEL 28F016SA1 5 89A0 2048KB INTEL 28F016SA2 5 89A0 2048KB INTEL 28F016SAThe following example shows flash chip informationRouter# show slot chips20480K bytes of processor board PCMCIA Slot0 flash (Read/Write)Chip Bank Code Size Name1 1 89A0 2048KB INTEL 28F016SA2 1 89A0 2048KB INTEL 28F016SA1 2 89A0 2048KB INTEL 28F016SA2 2 89A0 2048KB INTEL 28F016SA1 3 89A0 2048KB INTEL 28F016SA2 3 89A0 2048KB INTEL 28F016SA1 4 89A0 2048KB INTEL 28F016SA2 4 89A0 2048KB INTEL 28F016SA1 5 89A0 2048KB INTEL 28F016SA2 5 89A0 2048KB INTEL 28F016SAThe following example show the flash detailed directory.
Router# show slot detailedPCMCIA Slot0 flash directory:File Length Name/statusaddr fcksum ccksum1 11081464 c3660-bin-mz.123-9.3.PI5b0x40 0x5EA3 0x5EA3[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.
Router# show slot errPCMCIA Slot0 flash directory:File Length Name/status1 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 write1 1 89A0 2048KB INTEL 28F016SA 0 02 1 89A0 2048KB INTEL 28F016SA 0 01 2 89A0 2048KB INTEL 28F016SA 0 02 2 89A0 2048KB INTEL 28F016SA 0 01 3 89A0 2048KB INTEL 28F016SA 0 02 3 89A0 2048KB INTEL 28F016SA 0 01 4 89A0 2048KB INTEL 28F016SA 0 02 4 89A0 2048KB INTEL 28F016SA 0 01 5 89A0 2048KB INTEL 28F016SA 0 02 5 89A0 2048KB INTEL 28F016SA 0 0The following example shows the flash partition summary.
Router# show slot summaryPartition Size Used Free Bank-Size State Copy Mode1 20223K 10821K 9402K 4096K Read/Write Direct20480K bytes of processor board PCMCIA Slot0 flash (Read/Write)Related Commands
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
Command Modes
User EXEC
Privileged EXECCommand History
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
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.
Router# show version..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.
Router# show version..20480K bytes of Flash PCMCIA card at slot 1 (Sector size 128K).
Note
Examples
The following example displays information about slot 0. The output is self-explanatory.
Router# show slot0:PCMCIA Slot0 flash directory:File Length Name/status1 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)Router# show slot0: allPartition Size Used Free Bank-Size State Copy Mode1 20223K 10821K 9402K 4096K Read/Write DirectPCMCIA Slot0 flash directory:File Length Name/statusaddr fcksum ccksum1 11081464 c3660-bin-mz.123-9.3.PI5b0x40 0x5EA3 0x5EA3[11081528 bytes used, 9627844 available, 20709372 total]20480K bytes of processor board PCMCIA Slot0 flash (Read/Write)Chip Bank Code Size Name1 1 89A0 2048KB INTEL 28F016SA2 1 89A0 2048KB INTEL 28F016SA1 2 89A0 2048KB INTEL 28F016SA2 2 89A0 2048KB INTEL 28F016SA1 3 89A0 2048KB INTEL 28F016SA2 3 89A0 2048KB INTEL 28F016SA1 4 89A0 2048KB INTEL 28F016SA2 4 89A0 2048KB INTEL 28F016SA1 5 89A0 2048KB INTEL 28F016SA2 5 89A0 2048KB INTEL 28F016SAThe following example shows flash chip information.Router# show slot0: chips20480K bytes of processor board PCMCIA Slot0 flash (Read/Write)Chip Bank Code Size Name1 1 89A0 2048KB INTEL 28F016SA2 1 89A0 2048KB INTEL 28F016SA1 2 89A0 2048KB INTEL 28F016SA2 2 89A0 2048KB INTEL 28F016SA1 3 89A0 2048KB INTEL 28F016SA2 3 89A0 2048KB INTEL 28F016SA1 4 89A0 2048KB INTEL 28F016SA2 4 89A0 2048KB INTEL 28F016SA1 5 89A0 2048KB INTEL 28F016SA2 5 89A0 2048KB INTEL 28F016SAThe following example show the flash detailed directory.
Router# show slot0: detailedPCMCIA Slot0 flash directory:File Length Name/statusaddr fcksum ccksum1 11081464 c3660-bin-mz.123-9.3.PI5b0x40 0x5EA3 0x5EA3[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.
Router# show slot0: errPCMCIA Slot0 flash directory:File Length Name/status1 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 write1 1 89A0 2048KB INTEL 28F016SA 0 02 1 89A0 2048KB INTEL 28F016SA 0 01 2 89A0 2048KB INTEL 28F016SA 0 02 2 89A0 2048KB INTEL 28F016SA 0 01 3 89A0 2048KB INTEL 28F016SA 0 02 3 89A0 2048KB INTEL 28F016SA 0 01 4 89A0 2048KB INTEL 28F016SA 0 02 4 89A0 2048KB INTEL 28F016SA 0 01 5 89A0 2048KB INTEL 28F016SA 0 02 5 89A0 2048KB INTEL 28F016SA 0 0The following example shows the flash partition summary.
Router# show slot0: summaryPartition Size Used Free Bank-Size State Copy Mode1 20223K 10821K 9402K 4096K Read/Write Direct20480K bytes of processor board PCMCIA Slot0 flash (Read/Write)Related Commands
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
Command Modes
User EXEC
Privileged EXECCommand History
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
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.
Router# show version..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.
Router# show version..20480K bytes of Flash PCMCIA card at slot 1 (Sector size 128K).
Note
Examples
The following example displays information about slot 0 using the slot0: command form. The output is self-explanatory.Router# show slot1:PCMCIA Slot1 flash directory:File Length Name/status1 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)Router# show slot1: allPartition Size Used Free Bank-Size State Copy Mode1 20223K 10821K 9402K 4096K Read/Write DirectPCMCIA Slot0 flash directory:File Length Name/statusaddr fcksum ccksum1 11081464 c3660-bin-mz.123-9.3.PI5b0x40 0x5EA3 0x5EA3[11081528 bytes used, 9627844 available, 20709372 total]20480K bytes of processor board PCMCIA Slot0 flash (Read/Write)Chip Bank Code Size Name1 1 89A0 2048KB INTEL 28F016SA2 1 89A0 2048KB INTEL 28F016SA1 2 89A0 2048KB INTEL 28F016SA2 2 89A0 2048KB INTEL 28F016SA1 3 89A0 2048KB INTEL 28F016SA2 3 89A0 2048KB INTEL 28F016SA1 4 89A0 2048KB INTEL 28F016SA2 4 89A0 2048KB INTEL 28F016SA1 5 89A0 2048KB INTEL 28F016SA2 5 89A0 2048KB INTEL 28F016SAThe following example shows flash chip information.Router# show slot1: chips20480K bytes of processor board PCMCIA Slot0 flash (Read/Write)Chip Bank Code Size Name1 1 89A0 2048KB INTEL 28F016SA2 1 89A0 2048KB INTEL 28F016SA1 2 89A0 2048KB INTEL 28F016SA2 2 89A0 2048KB INTEL 28F016SA1 3 89A0 2048KB INTEL 28F016SA2 3 89A0 2048KB INTEL 28F016SA1 4 89A0 2048KB INTEL 28F016SA2 4 89A0 2048KB INTEL 28F016SA1 5 89A0 2048KB INTEL 28F016SA2 5 89A0 2048KB INTEL 28F016SAThe following example show the flash detailed directory.
Router# show slot1: detailedPCMCIA Slot0 flash directory:File Length Name/statusaddr fcksum ccksum1 11081464 c3660-bin-mz.123-9.3.PI5b0x40 0x5EA3 0x5EA3[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.
Router# show slot1: errPCMCIA Slot0 flash directory:File Length Name/status1 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 write1 1 89A0 2048KB INTEL 28F016SA 0 02 1 89A0 2048KB INTEL 28F016SA 0 01 2 89A0 2048KB INTEL 28F016SA 0 02 2 89A0 2048KB INTEL 28F016SA 0 01 3 89A0 2048KB INTEL 28F016SA 0 02 3 89A0 2048KB INTEL 28F016SA 0 01 4 89A0 2048KB INTEL 28F016SA 0 02 4 89A0 2048KB INTEL 28F016SA 0 01 5 89A0 2048KB INTEL 28F016SA 0 02 5 89A0 2048KB INTEL 28F016SA 0 0The following example shows the flash partition summary.
Router# show slot1: summaryPartition Size Used Free Bank-Size State Copy Mode1 20223K 10821K 9402K 4096K Read/Write Direct20480K bytes of processor board PCMCIA Slot0 flash (Read/Write)Related Commands
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
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:
Router# show snmpChassis: 0150619937 SNMP packets input0 Bad SNMP version errors4 Unknown community name0 Illegal operation for community name supplied0 Encoding errors24 Number of requested variables0 Number of altered variables0 Get-request PDUs28 Get-next PDUs0 Set-request PDUs78 SNMP packets output0 Too big errors (Maximum packet size 1500)0 No such name errors0 Bad values errors0 General errors24 Response PDUs13 Trap PDUsSNMP logging: enabledLogging to 172.16.58.33.162, 0/10, 13 sent, 0 dropped.SNMP Manager-role output packets4 Get-request PDUs4 Get-next PDUs6 Get-bulk PDUs4 Set-request PDUs23 Inform-request PDUs30 Timeouts0 DropsSNMP Manager-role input packets0 Inform response PDUs2 Trap PDUs7 Response PDUs1 Responses with errorsSNMP informs: enabledInforms in flight 0/25 (current/max)Logging to 172.16.217.141.1624 sent, 0 in-flight, 1 retries, 0 failed, 0 droppedLogging to 172.16.58.33.1620 sent, 0 in-flight, 0 retries, 0 failed, 0 droppedTable 111 describes the significant fields shown in the display.
Related Commands
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
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, 172.16.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 engineIDLocal SNMP engineID: 00000009020000000C025808Remote Engine ID IP-addr Port123456789ABCDEF000000000 172.16.37.61 162Table 112 describes the fields shown in the display.
Related Commands
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 groups on the router and the security model, the status of the different views, and the storage type of each group, use the show snmp group command in EXEC mode.
show snmp group
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
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:
router# show snmp groupgroupname: public security model:v1readview:v1defaultwriteview: no writeview specifiednotifyview: *tv.FFFFFFFFstorage-type: volatileTable 113 describes the fields shown in the example.
Related Commands
snmp-server group
Configures a new SNMP group or a table that maps SNMP users to 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
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.
Tips
Examples
The following is sample output from the show snmp mib command:
Router# show snmp mibsystem.1system.2sysUpTimesystem.4system.5system.6system.7system.8sysOREntry.2sysOREntry.3sysOREntry.4interfaces.1ifEntry.1ifEntry.2ifEntry.3ifEntry.4ifEntry.5ifEntry.6ifEntry.7ifEntry.8ifEntry.9ifEntry.10ifEntry.11--More--...captureBufferEntry.2captureBufferEntry.3captureBufferEntry.4captureBufferEntry.5captureBufferEntry.6captureBufferEntry.7capture.3.1.1eventEntry.1eventEntry.2eventEntry.3eventEntry.4eventEntry.5eventEntry.6eventEntry.7logEntry.1logEntry.2logEntry.3logEntry.4rmon.18.1.1.2rmon.18.1.1.3rmon.18.1.1.4rmon.18.1.1.5rmon.18.1.1.6rmon.18.1.1.7rmon.18.2.1.2rmon.18.2.1.3rmon.18.3.1.2--More--...rmon.19.11.1.1rmon.19.11.1.2rmon.19.11.1.3rmon.19.12rmon.19.13.1.2rmon.19.13.1.3rmon.19.13.1.4rmon.19.13.1.5rmon.19.13.1.6rmon.19.14.1.2rmon.19.14.1.3rmon.19.14.1.4rmon.19.14.1.5rmon.19.14.1.6rmon.19.14.1.7rmon.19.14.1.8rmon.19.14.1.9rmon.19.15rmon.19.16dot1dBase.1dot1dBase.2dot1dBase.3dot1dBasePortEntry.1dot1dBasePortEntry.2dot1dBasePortEntry.3dot1dBasePortEntry.4--More--...ifXEntry.1ifXEntry.2ifXEntry.3ifXEntry.4ifXEntry.5ifXEntry.6ifXEntry.7ifXEntry.8ifXEntry.9ifXEntry.10ifXEntry.11ifXEntry.12ifXEntry.13ifXEntry.14ifXEntry.15ifXEntry.16ifXEntry.17ifXEntry.18ifXEntry.19ifStackEntry.3ifTestEntry.1ifTestEntry.2--More--...Related Commands
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 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
Defaults
The ifIndex values for all interfaces are displayed.
Command Modes
EXEC
Command History
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/0Ethernet2/0: Ifindex = 2The following examples shows output for all interfaces:
Router# show snmp mib ifmib ifindexATM1/0: Ifindex = 1ATM1/0-aal5 layer: Ifindex = 12ATM1/0-atm layer: Ifindex = 10ATM1/0.0-aal5 layer: Ifindex = 13ATM1/0.0-atm subif: Ifindex = 11ATM1/0.9-aal5 layer: Ifindex = 32ATM1/0.9-atm subif: Ifindex = 31ATM1/0.99-aal5 layer: Ifindex = 36ATM1/0.99-atm subif: Ifindex = 35Ethernet2/0: Ifindex = 2Ethernet2/1: Ifindex = 3Ethernet2/2: Ifindex = 4Ethernet2/3: Ifindex = 5Null0: Ifindex = 14Serial3/0: Ifindex = 6Serial3/1: Ifindex = 7Serial3/2: Ifindex = 8Serial3/3: Ifindex = 9Related Commands
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
Command Modes
EXEC
Command History
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-logGlobalAgeout 15, GlobalEntryLimit 500Total Notifications logged in all logs 0Log Name"", Log entry Limit 500, Notifications logged 0Logging status enabledCreated by cliNote that in this example, the Log Name of "" indicates the default "null-named" Notification Log.
Related Commands
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
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 pendingreq id: 47, dest: 172.16.58.33.161, V2C community: public, Expires in 5 secsreq id: 49, dest: 172.16.58.33.161, V2C community: public, Expires in 6 secsreq id: 51, dest: 172.16.58.33.161, V2C community: public, Expires in 6 secsreq id: 53, dest: 172.16.58.33.161, V2C community: public, Expires in 8 secsTable 114 describes the significant fields shown in the display.
Related Commands
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
Command Modes
EXEC
Command History
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 sessionsDestination: 172.16.58.33.162, V2C community: publicRound-trip-times: 0/0/0 (min/max/last)packets output0 Gets, 0 GetNexts, 0 GetBulks, 0 Sets, 4 Informs0 Timeouts, 0 Dropspackets input0 Traps, 0 Informs, 0 Responses (0 errors)Destination: 172.16.217.141.162, V2C community: public, Expires in 575 secsRound-trip-times: 1/1/1 (min/max/last)packets output0 Gets, 0 GetNexts, 0 GetBulks, 0 Sets, 4 Informs0 Timeouts, 0 Dropspackets input0 Traps, 0 Informs, 4 Responses (0 errors)Table 115 describes the significant fields shown in the output.The following is sample output from the show snmp sessions brief command:
Router# show snmp sessions briefDestination: 172.16.58.33.161, V2C community: public, Expires in 55 secsTable 115 describes the significant fields shown in the display.
Related Commands
show snmp user
To display information on each Simple Network Management Protocol (SNMP) username in the group username table, use the show snmp user command in EXEC mode.
show snmp user
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Usage Guidelines
An SNMP user is a remote user for which an SNMP management operation is performed. For example, inform operations can be sent to a user on a remote SNMP engine. The user is designated using the snmp-server user command.
Examples
The following example specifies the username as authuser, the engine ID string as 00000009020000000C025808, and the storage-type as nonvolatile:
Router# show snmp userUser name: authuserEngine ID: 00000009020000000C025808storage-type: nonvolatileTable 116 describes the fields shown in the display.
Related Commands
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
Examples
The following is sample output from the show sntp command:
Router> show sntpSNTP server Stratum Version Last Receive172.16.118.9 5 3 00:01:02172.21.28.34 4 3 00:00:36 Synced BcastBroadcast client mode is enabled.Table 117 describes the significant fields shown in the display.
Related Commands
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
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:
Router# show stacksMinimum process stacks:Free/Size Name652/1000 Router Init726/1000 Init744/1000 BGP Open686/1200 Virtual ExecInterrupt level stacks:Level Called Free/Size Name1 0 1000/1000 env-flash3 738 900/1000 Multiport Communications Interfaces5 178 970/1000 Console UARTSystem was restarted by bus error at PC 0xAD1F4, address 0xD0D0D1AGS Software (GS3), Version 9.1(0.16), BETA TEST SOFTWARECompiled Tue 11-Aug-92 13:27 by jthomasStack trace from system failure:FP: 0x29C158, RA: 0xACFD4FP: 0x29C184, RA: 0xAD20CFP: 0x29C1B0, RA: 0xACFD4FP: 0x29C1DC, RA: 0xAD304FP: 0x29C1F8, RA: 0xAF774FP: 0x29C214, RA: 0xAF83EFP: 0x29C228, RA: 0x3E0CAFP: 0x29C244, RA: 0x3BD3CRelated Commands
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
Command Modes
Privileged EXEC
Command History
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:
Router# show subsysClass Versionstatic_map Kernel 1.000.001arp Kernel 1.000.001ether Kernel 1.000.001compress Kernel 1.000.001alignment Kernel 1.000.002monvar Kernel 1.000.001slot Kernel 1.000.001oir Kernel 1.000.001atm Kernel 1.000.001ip_addrpool_sys Library 1.000.001chat Library 1.000.001dialer Library 1.000.001flash_services Library 1.000.001ip_localpool_sys Library 1.000.001nvram_common Driver 1.000.001ASP Driver 1.000.001sonict Driver 1.000.001oc3suni Driver 1.000.001oc12suni Driver 1.000.001ds3suni Driver 1.000.001...Table 118 describes the fields shown in the display.
show tcp
To display the status of TCP connections, use the show tcp command in EXEC mode.
show tcp [line-number]
Syntax Description
line-number
(Optional) Absolute line number of the line for which you want to display Telnet connection status.
Command Modes
EXEC
Command History
Examples
The following is sample output from the show tcp command:
Router# show tcptty0, connection 1 to host ciderConnection state is ESTAB, I/O status: 1, unread input bytes: 0Local host: 172.31.232.17, Local port: 11184Foreign host: 172.31.1.137, Foreign port: 23Enqueued packets for retransmit: 0, input: 0, saved: 0Event Timers (current time is 67341276):Timer: Retrans TimeWait AckHold SendWnd KeepAlive GiveUp PmtuAgerStarts: 30 0 32 0 0 0 0Wakeups: 1 0 14 0 0 0 0Next: 0 0 0 0 0 0 0iss: 67317172 snduna: 67317228 sndnxt: 67317228 sndwnd: 4096irs: 1064896000 rcvnxt: 1064897597 rcvwnd: 2144 delrcvwnd: 0SRTT: 317 ms, RTTO: 900 ms, RTV: 133 ms, KRTT: 0 msminRTT: 4 ms, maxRTT: 300 ms, ACK hold: 300 msFlags: higher precedence, idle user, retransmission timeoutDatagrams (max data segment is 536 bytes):Rcvd: 41 (out of order: 0), with data: 34, total data bytes: 1596Sent: 57 (retransmit: 1), with data: 35, total data bytes: 55Table 119 describes the first five lines of output shown in the display.
The following line of output shows the current time according to the system clock of the local host:
Event Timers (current time is 67341276):The time shown is the number of milliseconds since the system started.
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 PmtuAgerStarts: 30 0 32 0 0 0 0Wakeups: 1 0 14 0 0 0 0Next: 0 0 0 0 0 0 0Table 120 describes the fields in the preceding lines of output.
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: 4096irs: 1064896000 rcvnxt: 1064897597 rcvwnd: 2144 delrcvwnd: 0Table 121 describes the fields shown in the display.
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 it is using.
SRTT: 317 ms, RTTO: 900 ms, RTV: 133 ms, KRTT: 0 msminRTT: 4 ms, maxRTT: 300 ms, ACK hold: 300 msFlags: higher precedence, idle user, retransmission timeoutTable 122 describes the significant fields shown in the output.
For more information on these fields, refer to Round Trip Time Estimation, P. Karn & C. Partridge, ACM SIGCOMM-87, August 1987.
Datagrams (max data segment is 536 bytes):Rcvd: 41 (out of order: 0), with data: 34, total data bytes: 1596Sent: 57 (retransmit: 1), with data: 35, total data bytes: 55Table 123 describes the significant fields shown in the last lines of the show tcp command output.
Related Commands
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
Examples
The following is sample output from the show tcp brief command while a user has connected into the system via Telnet:
Router> show tcp briefTCB Local Address Foreign Address (state)609789AC Router.cisco.com.23 cider.cisco.com.3733 ESTABTable 124 describes the significant fields shown in the display.
Related Commands
show tdm data
To display a snapshot of the time-division multiplexing (TDM) bus data memory in Cisco Access Servers, use the show tdm data command in EXEC mode.
show tdm data [motherboard | slot slot-number]
Syntax Description
motherboard
(Optional) Displays data for the motherboard (system plane).
slot slot-number
(Optional) Displays data for the specified interface (slot number).
Command Modes
EXEC
Command History
Usage Guidelines
The data memory for all TDM bus connections in the access server is displayed if you do not specify a motherboard or slot number.
Examples
In the following example, a snapshot of TDM memory is shown where the normal ISDN idle pattern (0x7E) is present on all channels of the TDM device resident on the motherboard:
AS5200# show tdm data motherboardMT8980 motherboard unit 0, Control Register = 0x1F, ODE Register = 0x06Data Memory for ST0:Ch0: 0x7E, Ch1: 0x7E, Ch2: 0x7E, Ch3: 0x7ECh4: 0x7E, Ch5: 0x7E, Ch6: 0x7E, Ch7: 0x7ECh8: 0x7E, Ch9: 0x7E, Ch10: 0x7E, Ch11: 0x7ECh12: 0x7E, Ch13: 0x7E, Ch14: 0x7E, Ch15: 0x7ECh16: 0x7E, Ch17: 0x7E, Ch18: 0x7E, Ch19: 0x7ECh20: 0x7E, Ch21: 0x7E, Ch22: 0x7E, Ch23: 0x7ECh24: 0x7E, Ch25: 0x7E, Ch26: 0x7E, Ch27: 0x7ECh28: 0x7E, Ch29: 0x7E, Ch30: 0x7E, Ch31: 0x7EData Memory for ST1:Ch0: 0x7E, Ch1: 0x7E, Ch2: 0x7E, Ch3: 0x7ECh4: 0x7E, Ch5: 0x7E, Ch6: 0x7E, Ch7: 0x7ECh8: 0x7E, Ch9: 0x7E, Ch10: 0x7E, Ch11: 0x7ECh12: 0x7E, Ch13: 0x7E, Ch14: 0x7E, Ch15: 0x7ECh16: 0x7E, Ch17: 0x7E, Ch18: 0x7E, Ch19: 0x7ECh20: 0x7E, Ch21: 0x7E, Ch22: 0x7E, Ch23: 0x7ECh24: 0x7E, Ch25: 0x7E, Ch26: 0x7E, Ch27: 0x7ECh28: 0x7E, Ch29: 0x7E, Ch30: 0x7E, Ch31: 0x7ERelated Commands
show tdm connections
Displays data about the TDM bus connection memory in a Cisco AS5200 access server.
show tech-support
To display general information about the router when reporting a problem, use the show tech-support privileged EXEC command.
show tech-support [page] [password] [cef | ipmulticast | isis | mpls | ospf [process-ID | detail] | rsvp]
Syntax Description
Defaults
The output scrolls without page breaks.
Passwords and other security information are removed from the output.Command Modes
Privileged EXEC
Command History
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.
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:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
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:
•
•
•
•
•
•
•
•
•
•
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
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
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).
Router# show time-rangetime-range entry: test (active)absolute start 00:00 01 January 2006 end 23:59 31 December 2006periodic weekdays 8:00 to 20:00Related Commands
time-range
Specifies a time range by name and allows you configure a range during which an access list, for example, is active.
show version
To display information about the currently loaded software version along with hardware and device information, use the show version command in EXEC mode.
show version
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
User EXEC
Privileged EXEC
Command History
9.0
This command was introduced.
12.3(4)T
The output format of this command was updated.
12.2(25)S
The output format of this command was updated.
Usage Guidelines
This command displays information about the Cisco IOS software version currently running on a routing device, the ROM Monitor and Bootflash software versions, and information about the hardware configuration, including the amount of system memory. Because this command displays both software and hardware information, the output of this command is the same as the output of the show hardware command. (The show hardware command is a command alias for the show version command.)
Specifically, the show version command provides the following information:
•
–
–
–
–
•
–
–
–
–
–
•
–
–
–
–
–
–
–
The output of this command uses the following format:
Cisco IOS Software, <platform> Software (<image-id>), Version <software-version>, <software-type>TAC Support: http://www.cisco.com/tacCopyright (c) <date-range> by Cisco Systems, Inc.Compiled <day> <date> <time> by <compiler-id>ROM: System Bootstrap, Version <software-version>, <software-type>BOOTLDR: <platform> Software (image-id), Version <software-version>, <software-type><router-name> uptime is <w> weeks, <d> days, <h> hours, <m> minutesSystem returned to ROM by reload at <time> <day> <date>System image file is "<filesystem-location>/<software-image-name>"Last reload reason: <reload-reason>Cisco <platform-processor-type> processor (revision <processor-revision-id>) with <free-DRAM-memory>K/<packet-memory>K bytes of memory.Processor board ID <ID-number><CPU-type> CPU at <clock-speed>Mhz, Implementation <number>, Rev <Revision-number>, <kilobytes-Processor-Cache-Memory>KB <cache-Level> CacheSee the Examples section for descriptions of the fields in this output.
Examples
The following is sample output from the show version command issued on a Cisco 3660 running Cisco IOS Release 12.3(4)T:
Router# show versionCisco IOS Software, 3600 Software (C3660-I-M), Version 12.3(4)TTAC Support: http://www.cisco.com/tacCopyright (c) 1986-2003 by Cisco Systems, Inc.Compiled Thu 18-Sep-03 15:37 by ccaiROM: System Bootstrap, Version 12.0(6r)T, RELEASE SOFTWARE (fc1)ROM:C3660-1 uptime is 1 week, 3 days, 6 hours, 41 minutesSystem returned to ROM by power-onSystem image file is "slot0:tftpboot/c3660-i-mz.123-4.T"Cisco 3660 (R527x) processor (revision 1.0) with 57344K/8192K bytes of memory.Processor board ID JAB055180FFR527x CPU at 225Mhz, Implementation 40, Rev 10.0, 2048KB L2 Cache3660 Chassis type: ENTERPRISE2 FastEthernet interfaces4 Serial interfacesDRAM configuration is 64 bits wide with parity disabled.125K bytes of NVRAM.16384K bytes of processor board System flash (Read/Write)Flash card inserted. Reading filesystem...done.20480K bytes of processor board PCMCIA Slot0 flash (Read/Write)Configuration register is 0x2102The following is sample output from the show version command issued on a Cisco 7200 router running Cisco IOS Release 12.4(4)T. This output shows the total bandwidth capacity and the bandwith capacity that is configured on the Cisco 7200. Displaying bandwidth capacity is available in Cisco IOS Release 12.2 and later releases.
Router# show versionCisco IOS Software, 7200 Software (C7200-JS-M), Version 12.4(4)T, RELEASE SOFTW)Technical Support: http://www.cisco.com/techsupportCopyright (c) 1986-2005 by Cisco Systems, Inc.Compiled Thu 27-Oct-05 05:58 by ccaiROM: System Bootstrap, Version 12.1(20000710:044039) [nlaw-121E_npeb 117], DEVEEBOOTLDR: 7200 Software (C7200-KBOOT-M), Version 12.3(16), RELEASE SOFTWARE (fc4)router uptime is 5 days, 18 hours, 2 minutesSystem returned to ROM by reload at 02:45:12 UTC Tue Feb 14 2006System image file is "disk0:c7200-js-mz.124-4.T"Last reload reason: Reload CommandCisco 7206VXR (NPE400) processor (revision A) with 491520K/32768K bytes of memo.Processor board ID 26793934R7000 CPU at 350MHz, Implementation 39, Rev 3.2, 256KB L2 Cache6 slot VXR midplane, Version 2.6Last reset from power-onPCI bus mb0_mb1 (Slots 0, 1, 3 and 5) has a capacity of 600 bandwidth points.Current configuration on bus mb0_mb1 has a total of 440 bandwidth points.This configuration is within the PCI bus capacity and is supported.PCI bus mb2 (Slots 2, 4, 6) has a capacity of 600 bandwidth points.Current configuration on bus mb2 has a total of 390 bandwidth pointsThis configuration is within the PCI bus capacity and is supported.Please refer to the following document "Cisco 7200 Series Port AdaptorHardware Configuration Guidelines" on Cisco.com <http://www.cisco.com>for c7200 bandwidth points oversubscription and usage guidelines.4 Ethernet interfaces2 FastEthernet interfaces2 ATM interfaces125K bytes of NVRAM.62976K bytes of ATA PCMCIA card at slot 0 (Sector size 512 bytes).125952K bytes of ATA PCMCIA card at slot 1 (Sector size 512 bytes).8192K bytes of Flash internal SIMM (Sector size 256K).Configuration register is 0x2002Router#For information about PCI buses and bandwidth calculation, go to /en/US/docs/routers/7200/configuration/7200_port_adapter_config_guidelines/3875In.html#wp1057192.
Table 125 describes the significant fields shown in the display.
Table 125 show version Field Descriptions
Cisco IOS Software, <platform> Software (<image-id>), Version <software-version>, <release-type>
Example:Cisco IOS Software, 7200 Software (C7200-G4JS-M), Version 12.3(4)T
platform—Cisco hardware device name.
image-id—The coded software image identifier, in the format platform-features-format (for example, "c7200-g4js-mz".
software-version—The Cisco IOS software release number, in the format x.y(z)A, where x.y is the main release identifier, z is the maintenance release number, and A, where applicable, is the special release train identifier. For example, 12.3(4)T indicates the fourth maintenance release of the 12.3T special technology release train.
Note
release-type—The description of the release type. Possible values include MAINTENANCE [for example, 12.3(3)] or INTERIM [for example, 12.3(3.2)].
TipsCisco IOS is a registered trademark (R) of Cisco Systems, Inc.
Copyright (c) <date-range> by Cisco Systems, Inc.
The Cisco Technical Assistance Center (TAC) contains more than 30,000 pages of searchable technical content, including links to products, technologies, solutions, technical tips, and tools. Registered Cisco.com users can log in from this page to access even more content.
Cisco IOS software, including the source code, user-help, and documentation, is copyrighted by Cisco Systems, Inc. It is Cisco's policy to enforce its copyrights against any third party who infringes on its copyright.
ROM: System Bootstrap, Version 12.0(6r)T, RELEASE SOFTWARE (fc1)
The system "bootstrap" software, stored in ROM memory.
BOOTFLASH:
The system "bootflash" software, stored in Flash memory (if applicable).
C3660-1 uptime is 1 week, 3 days, 6 hours, 41 minutes
The amount of time the system has been up and running.
System returned to ROM by <reload-reason> at <time> <day> <date>
Example:System returned to ROM by reload at 20:56:53 UTC Tue Nov 4 2003Shows the last recorded reason for a system reload, and time of last reload.
Shows the last recorded reason for a system reload.
Shows the last recorded reason for a system reset. Possible reset-reason values include:
•
•
•
•
•
•
(This field was formerly labeled as the "System restarted by" field.")
System image file is "<file-location/file-name>"
Example:System image file is "slot0:tftpboot/c3660-i-mz.1 23-3.9.T2"Displays the file location (local or remote filesystem) and the system image name.
Cisco 3660 (R527x) processor (revision 1.0) with 57344K/8192K bytes of memory.
This line can be used to determine how much Dynamic RAM (DRAM) is installed on your system, in order to determine if you meet the "Min. Memory" requirement for a software image. DRAM (including SDRAM) is used for system processing memory and for packet memory.
Two values, separated by a slash, are given for DRAM: The first value tells you how DRAM is available for system processing, and the second value tells you how much DRAM is being used for Packet memory.
The first value, Main Processor memory, is either:
•
•
The second value, Packet memory, is either:
•
•
Note
Separate DRAM and Packet Memory
The 4000, 4500, 4700, and 7500 series routers have separate DRAM and Packet memory, so you only need to look at the first number to determine total DRAM. In the example to the left for the Cisco RSP4, the first value shows that the router has 65536K (65,536 kilobytes, or 64 megabytes) of DRAM. The second value, 8192K, is the Packet memory.
Combined DRAM and Packet Memory
The 2500, 2600, 3600, and 7200 series routers require a minimum amount of I/O memory to support certain interface processors.
The 1600, 2500, 2600, 3600, and 7200 series routers use a fraction of DRAM as Packet memory, so you need to add both numbers to find out the real amount of DRAM. In the example to the left for the Cisco 3660, the router has 57,344 kilobytes (KB) of free DRAM and 8,192 KB dedicated to Packet memory. Adding the two numbers together gives you 57,344K + 8,192K = 65,536K, or 64 megabytes (MB) of DRAM.
For more details on memory requirements, see the document "How to Choose a Cisco IOS® Software Release" on Cisco.com.
Shows the current configured hex value of the software configuration register. If the value has been changed with the config-register command, the register value that will be used at the next reload is displayed in parenthesis.
The boot field (final digit) of the software configuration register dictates what the system will do after a reset.
For example, when the boot field of the software configuration register is set to 00 (for example, 0x0), and you press the NMI button on a Performance Route Processor (PRP), the user-interface remains at the ROM monitor prompt (rommon>) and waits for a user command to boot the system manually. But if the boot field is set to 01 (for example, 0x1), the system automatically boots the first Cisco IOS image found in the onboard Flash memory SIMM on the PRP.
The factory-default setting for the configuration register is 0x2102. This value indicates that the router will attempt to load a Cisco IOS software image from Flash memory and load the startup configuration file.
Related Commands
show whoami
To display information about the terminal line of the current user, including host name, line number, line speed, and location, use the show whoami command in EXEC mode.
show whoami [text]
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
If text is included as an argument in the command, that text is displayed as part of the additional data about the line.
To prevent the information from being lost if the menu display clears the screen, this command always displays a --More-- prompt before returning. Press the space bar to return to the prompt.
Examples
The following example is sample output from the show whoami command:
Router> show whoamiComm Server "Router", Line 0 at 0bps. Location "Second floor, West"--More--Router>show xsm status
To display information and subscription status of the XML Subscription Manager (XSM) server and clients (such as VPN Device Manager [VDM]), and to display a list of XML data from the XSM server, use the show xsm status command in privileged EXEC mode.
show xsm status
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command to display the following information: which subsystems and histories are enabled or disabled (XSM, Embedded Device Manager [EDM], VDM), XSM client version, number of XSM sessions, duration of XSM session, session IDs, client version and IP address, configuration and monitor privilege levels, and list of subscribed XML Request Descriptors (XRDs).
Examples
The following example shows one XSM session (Session ID = 2) active on the Cisco device for the XSM client at IP address 172.17.129.134, and how long this session has been connected to the XSM server (Session 2: Connected since 22:47:07 UTC Mon Jan 8 2001). The output shows that the XSM, VDM, and EDM subsystems, and EDM and VDM history collecting are enabled. XSM configuration privilege level is set at 15, with XSM monitor privilege level set at 1.
This output also shows the active XRDs (and their version) for Session 2:
Router# show xsm statusXSM subsystem is Enabled.VDM subsystem is Enabled.EDM subsystem is Enabled.EDM History is Enabled.VDM History is Enabled.XSM privilege configuration level 15.XSM privilege monitor level 1.Number of XSM Sessions : 1.Session ID = 2.XSM Client v0.0(0.0)- @ 172.17.129.134Connected since 22:47:07 UTC Mon Jan 8 2001List of subscribed xrds:0 ) device-about v1.01 ) ios-image v1.02 ) if-list v1.03 ) device-health v1.04 ) ike-stats v1.05 ) ike v1.06 ) ipsec-topn-tunnels-by-traffic v1.07 ) ipsec-topn-tunnels-by-duration v1.08 ) ipsec-stats v1.09 ) crypto-maps v1.010) ipsec v1.0Table 126 describes the significant fields shown in the display. (See Table 127 in the documentation of the show xsm xrd-list command for a full description of subscribed XRDs).
Related Commands
show xsm xrd-list
To display all XML Request Descriptors (XRDs) for XML Subscription Manager (XSM) clients (such as the VPN Device Manager [VDM]) made available by subscription to the XSM server and to identify the required privilege levels, use the show xsm xrd-list command in privileged EXEC mode.
show xsm xrd-list
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command to display the XRD version and minimum privilege level and type (configuration or monitor) required to view each XRD.
Examples
The following example shows some active XRDs on the XSM server. The end of each line displays the following:
•
•
This example displays all available XRDs because both relevant commands (xsm edm and xsm vdm) have been configured. However, if one command is not configured, only an abbreviated XRD list will appear.
Router# show xsm xrd-listList of all available xrds:0 ) vlan-db v1.0 privilege=configuration1 ) entity v1.0 privilege=configuration2 ) ip v1.0 privilege=configuration3 ) ios-users v1.0 privilege=configuration4 ) device-about v1.0 privilege=monitor5 ) ios-image v1.0 privilege=configuration6 ) if-stats v1.0 privilege=monitor7 ) if-list v1.0 privilege=configuration8 ) device-health v1.0 privilege=monitor9 ) time v1.0 privilege=monitor10) access-lists v1.0 privilege=configuration11) ike-topn-tunnels-by-traffic v1.0 privilege=monitor12) ike-topn-tunnels-by-errors v1.0 privilege=monitor13) ike-topn-tunnels-by-duration v1.0 privilege=monitor14) ike-stats v1.0 privilege=monitor15) ike v1.0 privilege=configuration16) certificate-authorities v1.0 privilege=configuration17) ipsec-topn-tunnels-by-traffic v1.0 privilege=monitor18) ipsec-topn-tunnels-by-errors v1.0 privilege=monitor19) ipsec-topn-tunnels-by-duration v1.0 privilege=monitor20) ipsec-stats v1.0 privilege=monitor21) crypto-maps v1.0 privilege=configuration22) ipsec v1.0 privilege=configuration23) vdm-history v1.0 privilege=configuration24) gre-tunnels v1.0 privilege=monitorend list.Table 127 describes (in alphabetical order) typical XRDs shown in the display.
Related Commands
showmon
To show both the ReadOnly and the Upgrade ROMmon image versions when you are in ROMmon mode, as well as which ROMmon image is running on the Cisco 7200 VXR or Cisco 7301 router, use the showmon command in ROMmon mode.
showmon
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
ROMmon
Command History
Usage Guidelines
Use the showmon command when you are in ROMmon mode. Use the show rom-monitor command when you are in Cisco IOS.
Examples
The following example, applicable to both the Cisco 7200 VXR and Cisco 7301 routers, uses the showmon command in ROMmon to display both ROMmon images and to verify that the Upgrade ROMmon image is running:
rommon 1 > showmonReadOnly ROMMON version is:System Bootstrap, Version 12.2(20031011:151758) [biff]Copyright (c) 2004 by Cisco Systems, Inc.Upgrade ROMMON version is:System Bootstrap, Version 12.2(20031011:151758) [biff]Copyright (c) 2004 by Cisco Systems, Inc.Upgrade ROMMON currently runningUpgrade ROMMON is selected for next bootrommon 2 >Related Commands
rommon-pref
Selects a ReadOnly or Upgrade ROMmon image to be booted on the next reload of a Cisco 7200 VXR or Cisco 7301 when you are in ROMmon.
snmp ifmib ifalias long
To configure the system to handle IfAlias descriptions of up to 256 characters, use the snmp ifmib ifalias long command in global configuration mode. To limit the IfAlias description to 64 characters, use the no form of this command.
snmp ifmib ifalias long
no snmp ifmib ifalias long
Syntax Description
This command has no arguments or keywords.
Defaults
The ifAlias description is limited to 64 characters.
Command Modes
Global configuration
Command History
Usage Guidelines
The ifAlias object (ifXEntry 18) of the Interfaces MIB (IF-MIB) is called the Interface Alias. The Interface Alias (ifAlias) is a user-specified description of an interface used for Simple Network Management Protocol (SNMP) network management. The ifAlias is an object in the Interfaces Group MIB (IF-MIB) which can be set by a network manager to "name" an interface.
The ifAlias value for an interface or subinterface can be set using the description command in interface configuration mode or subinterface configuration mode, or by using a Set operation from an NMS. Prior to the introduction of this command, ifAlias descriptions for subinterfaces were limited to 64 characters. (The OLD-CISCO-INTERFACES-MIB allows up to 255 characters for the locIfDescr MIB variable, but this MIB does not support subinterfaces.) IfAlias descriptions appear in the output of the show interfaces EXEC mode command, and in the output of the more system: running-config or show running-config EXEC mode commands.
Examples
In the following example, the system is configured to retain and return ifAlias values of up to 256 characters in length:
Router(config)# snmp ifmib ifalias longRelated Commands
snmp mib notification-log default
To create an unnamed Simple Network Management Protocol (SNMP) notification log, use the snmp mib notification-log default command in global configuration mode. To delete the log, use the no form of this command.
snmp mib notification-log default [size number]
no snmp mib notification-log default [size number]
Syntax Description
Defaults
500 entries
Command Modes
Global configuration
Command History
12.0(22)S
This command was introduced.
12.2(13)T
This command was integrated into Cisco IOS Release 12.2(13)T.
Usage Guidelines
This command creates a default unnamed SNMP notification log. The default log has a zero length string as its name (appears in the output of the show snmp mib notification-log command as Log Name"").
Creation and removal of the default log can only be performed using the Command Line Interface (CLI). Creation of named logs using the CLI or SNMP tools (SET operations) is not currently supported. No filters (varbinds) can be associated with the default log.
SNMP notification logging is enabled by default, but logging does not start until a specific log is created and defined using this command, or a named log is created using an SNMP Set operation from a network management station (NMS).
The no form of this command deletes the default notification log and removes the notifications that were a part of this log from the Notification Log MIB database (recursively deletes the log and all of its entries).
Examples
