-
Cisco IOS Network Management Command Reference
-
Introduction
-
absolute through action snmp-trap
-
action string compare through buffers tune automatic
-
calendar set through clock update-calendar
-
cns aaa authentication through discover (cns)
-
emm through event manager scheduler script
-
event manager scheduler suspend through hw-module logging onboard (Cat 6K)
-
idle-timeout (WSMA) through ip director server weights
-
ip dns server through kron policy-list
-
line-cli through logging userinfo
-
major rising through ntp update-calendar
-
object id (action notification) through rmon queuesize
-
sample (expression) through show ethernet oam status
-
show event manager detector through show event manager session cli username
-
show facility-alarm through show ntp status
-
show odm-format through show rmon topn
-
show snmp through snmp mib event sample
-
snmp mib event trigger owner through snmp-server enable informs
-
snmp-server enable traps through snmp-server enable traps ospf cisco-specific retransmit
-
snmp-server enable traps ospf cisco-specific state-change through snmp-server enable traps voice poor-qov
-
snmp-server engineID local through snmp trap link-status
-
sntp broadcast client through xsm vdm
-
Feedback
Table Of Contents
scripting tcl trustpoint untrusted
sample (event trigger)
To specify the type of object sampling to use for an event, use the sample command in event trigger configuration mode. To disable teh configured settings, use the no form of this command.
sample {absolute | delta | changed}
no sample {absolute | delta | changed}
Syntax Description
Command Default
The default sampling method is absolute.
Command Modes
Event trigger configuration (config-event-trigger)
Command History
Usage Guidelines
The sample command enables the specified sampling method for the object. You can specify the following sampling methods.
•
Absolute
•
•
Absolute sampling uses the value of the MIB object during sampling. The default sampling method is absolute.
Delta sampling uses the last sampling value maintained in the application. This method requires applications to do continuous sampling.
The changed sampling method uses the changed value of the object since the last sample.
Examples
The following example shows how to specify the sampling method as absolute:
Router(config)# snmp mib event trigger owner owner1 name triggerARouter(config-event-trigger)# sample absoluteRelated Commands
sample (expression)
To specify the method of sampling the object, use the sample command in expression object configuration mode. To disable the specified method of object sampling, use the no form of this command.
sample {absolute | delta | changed}
no sample
Syntax Description
Command Default
The default sampling method is absolute.
Command Modes
Expression object configuration (config-expression-object)
Command History
Usage Guidelines
The Expression MIB allows you to create expressions based on a combination of objects. The expressions are evaluated according to the sampling method. The Expression MIB supports the following types of object sampling:
•
•
•
The sample command enables the specified sampling method for the object. If there are no delta or changed values in an expression, the expression is evaluated when a requester attempts to read the value of the expression. In this case, all requesters get a newly calculated value.
For expressions with delta or change values, the evaluation is performed for every sampling. In this case, requesters get the value as of the last sample period.
Examples
The following example shows how to specify the sampling method as absolute:
Router(config)# snmp mib expression owner owner1 name expressionARouter(config-expression)# object 32Router(config-expression-object)# sample absoluteRelated Commands
scheduler heapcheck process
To perform a "sanity check" for corruption in memory blocks when a process switch occurs, use the scheduler heapcheck process command in global configuration mode. To disable this feature, use the no form of this command.
scheduler heapcheck process [memory [fast] [io] [multibus] [pci] [processor] [checktype {all | data | magic | mlite-data | pointer | refcount | lite-chunks}]]
no scheduler heapcheck process
Syntax Description
Defaults
This command is disabled by default. If no keywords are specified, a sanity check will be performed on all the memory blocks and memory pools.
Command Modes
Global configuration (config)
Command History
12.2(15)T
This command was introduced.
12.3(11)T
The lite-chunks keyword was added.
12.4(20)T
The data and mlite-data keywords were added.
Usage Guidelines
When configuring this command, you can choose none or all memory block keywords (fast, io, multibus, pci, processor, and checktype).
Enabling this command has a significant impact on router performance.
Examples
The following example shows how to sanity check for corruption in the I/O memory block when a process switch occurs. In this example, the values of only the block magic, red zone, and size will be checked.
scheduler heapcheck process memory io checktype magicThe following example shows how to sanity check for corruption in the processor memory block when a process switch occurs. In this example, the values of only the next and previous pointers will be checked.
scheduler heapcheck process memory processor checktype pointerRelated Commands
memory lite
Enables the malloc_lite feature.
memory sanity
Performs a "sanity check" for corruption in buffers and queues.
schema
To specify the bulk statistics schema to be used in a specific bulk statistics transfer configuration, use the schema command in Bulk Statistics Transfer configuration mode. To remove a previously configured schema from a specific bulk statistics transfer configuration, use the no form of this command.
schema schema-name
no schema schema-name
Syntax Description
Command Default
No bulk statistics schema is specified.
Command Modes
Bulk Statistics Transfer configuration (config-bulk-tr)
Command History
Usage Guidelines
Repeat this command as desired for a specific bulk statistics transfer configuration. Multiple schemas can be associated with a single transfer configuration; all collected data will be in a single bulk statistics data file (VFile).
Examples
In the following example, the bulk statistics schemas ATM2/0-IFMIB and ATM2/0-CAR are associated with the bulk statistics transfer configuration called bulkstat1:
Router(config)# snmp mib bulkstat transfer bulkstat1Router(config-bulk-tr)# schema ATM2/0-IFMIBRouter(config-bulk-tr)# schema ATM2/0-CARRouter(config-bulk-tr)# url primary ftp://user:pswrd@host/folder/bulkstat1Router(config-bulk-tr)# retry 2Router(config-bulk-tr)# retain 10Router(config-bulk-tr)# exitRelated Commands
snmp mib bulkstat transfer
Names a bulk statistics transfer configuration and enters Bulk Statistics Transfer configuration mode.
scripting tcl encdir
To specify the default location of external encoding files used by the Tool Command Language (Tcl) shell, use the scripting tcl encdir command in global configuration mode. To remove the default location, use the no form of this command.
scripting tcl encdir location-url
no scripting tcl encdir
Syntax Description
Defaults
Tcl does not use external encoding files.
Command Modes
Global configuration
Command History
Usage Guidelines
Character strings in Tcl are encoded using 16-bit Unicode characters. Different operating system interfaces or applications can generate character strings using other encoding methods. Use the scripting tcl encdir command to configure a location URL for the external Tcl character encoding files to support the Tcl encoding command.
Tcl contains only a few character sets within the Tcl shell. Additional characters sets are loaded, as needed, from external files.
Examples
The following example shows how to specify a default location for external encoding files to be used by Tcl:
Router# configure terminalRouter(config)# scripting tcl encdir tftp://10.18.117.23/file2/Related Commands
scripting tcl init
Specifies an initialization script for the Tcl shell.
tclsh
Enables the Tcl shell and enters Tcl configuration mode.
scripting tcl init
To specify an initialization script for the Tool Command Language (Tcl) shell, use the scripting tcl init command in global configuration mode. To remove the initialization script, use the no form of this command.
scripting tcl init init-url
no scripting tcl init
Syntax Description
Defaults
Tcl does not run an initialization script.
Command Modes
Global configuration
Command History
Usage Guidelines
Use the scripting tcl init command when you want to predefine Tcl procedures to run in an initialization script. The initialization script runs when the Tcl shell is entered and saves manual sourcing of the individual scripts.
Examples
The following example shows how to specify an initialization script to run when the Tcl shell is enabled:
Router# configure terminalRouter(config)# scripting tcl init ftp://user:password@172.17.40.3/tclscript/initfile3.tclRelated Commands
scripting tcl encdir
Specifies the default location of external encoding files used by the Tcl shell.
tclsh
Enables the Tcl shell and enters Tcl configuration mode.
scripting tcl low-memory
To set a low memory threshold for free memory for Tool Command Language (Tcl)-based applications, use the scripting tcl low-memory command in global configuration mode. To remove the specific low memory threshold and return to using the default value, use the no form of this command.
scripting tcl low-memory bytes
no scripting tcl low-memory
Syntax Description
bytes
Specifies the low memory threshold. The memory threshold can be set from 0 to 4294967295 bytes.
Defaults
The default value is 25 percent of the available free memory at start up when Tcl initializes.
Note
Command Modes
Global configuration (config)
Command History
Usage Guidelines
Use the scripting tcl low-memory command to set the threshold for free memory. If minimum free RAM drops below this threshold, Tcl aborts the current script. This prevents the Tcl interpreter from allocating too much RAM and crashing the router.
Examples
The following example shows how to set the threshold for free memory when the Tcl shell is initialized:
Router# configure terminalRouter(config)# scripting tcl low-memory 33117513Related Commands
scripting tcl secure-mode
To enable signature verification of the interactive Tool Command Language (Tcl) scripts, use the scripting tcl secure-mode command in global configuration mode. To disable signature verification of the interactive Tcl scripts, use the no form of this command.
scripting tcl secure-mode
no scripting tcl secure-mode
Syntax Description
This command has no arguments or keywords.
Command Default
The signature verification of the interactive Tcl scripts is disabled.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
Use the scripting tcl secure-mode command to enable signature verification of all Tcl scripts run on the router. By default, the signature verification of the interactive Tcl scripts is disabled. You must enable the signature verification in order to verify whether the Tcl scripts match their digital signature. That would indicate they have not been altered since the digital signature was generated. If the script does not contain the digital signature, the script may run in a limited mode for untrusted script (that is, a script that has failed signature verification) or may not run at all. After receiving the results from the signature verification, the scripts are executed.
A Cisco IOS Crypto image software is required to enable this command and configure the Signed Tcl Scripts feature. The Crypto configuration commands enable the Cisco x.509 certificate storage. The scripting tcl secure-mode command can be enabled after the Crypto configuration trustpoint commands are enabled.
The scripting tcl trustpoint name command must be configured with the scripting tcl secure-mode command to verify the integrity of Tcl script signatures run on the router. Both commands must be configured to fully operate the feature; otherwise, a syslog message is generated:
*Jun 13 17:35:14.219: %SYS-6-SCRIPTING_TCL_INVALID_OR_MISSING_SIGNATURE: tcl signing validation failed on script signed with trustpoint name mytrust, cannot run the signed TCL script.In addition, the crypto pki trustpoint name command provided should contain a certificate that matches the certificate that was originally used to generate the digital signature on the Tcl script.
Examples
The following example shows how to enable signature verification of the interactive Tcl scripts:
Router(config)# crypto pki trustpoint mytrustRouter(ca-trustpoint)# enrolment terminalRouter(ca-trustpoint)# exitRouter(config)# crypto pki authenticate mytrustEnter the base 64 encoded CA certificate.End with a blank line or the word "quit" on a line by itselfMIIEuDCCA6CgAwIBAgIBADANBgkqhkiG9w0BAQQFADCBnjELMAkGA1UEBhMCVVMxEzARBgNVBAgTCkNhbGlmb3JuaWExETAPBgNVBAcTCFNhbiBKb3NlMRwwGgYDVQQKExNDaXNjbyBTeXN0ZW1zLCBJbmMuMQ4wDAYDVQQLEwVOU1NURzEWMBQGA1UEAxMNSm9obiBMYXV0bWFubjEhMB8GCSqGSIb3DQEJARYSamxhdXRtYW5AY2lzY28uY29tMB4XDTA2MTExNzE3NTgwMVoXDTA5MTExNjE3NTgwMVowgZ4xCzAJBgNVBAYTAlVTMRMwEQYDVQQIEwpDYWxpZm9ybmlhMREwDwYDVQQHEwhTYW4gSm9zZTEcMBoGA1UEChMTQ2lzY28gU3lzdGVtcywgSW5jLjEOMAwGA1UECxMFTlNTVEcxFjAUBgNVBAMTDUpvaG4gTGF1dG1hbm4xITAfBgkqhkiG9w0BCQEWEmpsYXV0bWFuQGNpc2NvLmNvbTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBALxtqTMCirMb+CdyWLuHoWAM8CEJDwQggL7MWBhoi3TSMd/ww2XBB9biBtdlH6jHsjCiOwAR5OorakwfPyf7mvRJ2PqJALs+Vn93VBKIG6rZUl4+wdOx686BVddIZvEJQPbROiYTzfazWV70aLMVbd7/B7vF1SG1YK9y1tX9p9nZyZ0x47OAXetwOaGinvlG7VNuTXaASBLUjCRZsIlzSBrXXedBzZ6+BuoWm1FK45EYSlag5Rt9RGXXMBqzx91iyhrJ3zDDmkExa45yKJETmAgDVMcpeteJtif47UDZJK30g4MbMyx/c8WGhmJ54qRL9BZEPmDxMQkNP10l8MAlQ8sCAwEAAaOB/jCB+zAdBgNVHQ4EFgQU9/ToDvbMR3JfJ4xEa4X47oNFq5kwgcsGA1UdIwSBwzCBwIAU9/ToDvbMR3JfJ4xEa4X47oNFq5mhgaSkgaEwgZ4xCzAJBgNVBAYTAlVTMRMwEQYDVQQIEwpDYWxpZm9ybmlhMREwDwYDVQQHEwhTYW4gSm9zZTEcMBoGA1UEChMTQ2lzY28gU3lzdGVtcywgSW5jLjEOMAwGA1UECxMFTlNTVEcxFjAUBgNVBAMTDUpvaG4gTGF1dG1hbm4xITAfBgkqhkiG9w0BCQEWEmpsYXV0bWFuQGNpc2NvLmNvbYIBADAMBgNVHRMEBTADAQH/MA0GCSqGSIb3DQEBBAUAA4IBAQBtEs/4MQeN9pT+XPCPg2ObQU8y2AadI+I34YK+fDHsFOh68hZhpszTN2VpNEvkFXpADhgr7DkNGtwTCla481v70iNFViQVL+inNrZwWMxoTnUNCK7Hc5kHkXt6cj0mvsefVUzxXl70mauhESRVlmYWrJxSsrEILerZYsuv5HbFdand+/rErmP2HVyfdntLnKdSzmXJ5lwE/Et2QtYNGor0OBlLesowfslR3LhHi4wn+5is7mALgNw/NuTiUr1zH18OeB4mwcpBIJsLaJu6ZUJQl7IqdswSa3fHd5qq0/k8P9z0YAYrf3+MFQr4ibvsYvHlO087o2Js1gW4qz34pqNhCertificate has the following attributes:Fingerprint MD5: 1E327DBB 330936EB 2FB8EACB 4FD1133EFingerprint SHA1: EE7FF9F4 05148842 B9D50FAC D76FDC9C E0703246% Do you accept this certificate? [yes/no]: yesTrustpoint CA certificate accepted.% Certificate successfully importedRouter(config)# scripting tcl secure-modeRouter(config)# scripting tcl trustpoint name mytrustRelated Commands
scripting tcl trustpoint name
Associates an existing configured trustpoint name with a certificate to verify Tcl scripts.
scripting tcl trustpoint name
To associate an existing configured trustpoint name with a certificate to verify Tool Command Language (Tcl) scripts, use the scripting tcl trustpoint name command in global configuration mode. To remove an existing configured trustpoint name, use the no form of this command.
scripting tcl trustpoint name name
no scripting tcl trustpoint name name
Syntax Description
name
Name of the configured trustpoint name associated with a certificate. Only one name can be associated with one certificate.
Command Default
A trustpoint name is not associated with a certificate to verify the Tcl scripts.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
Use the scripting tcl trustpoint name command to associate an existing configured trustpoint name with a certificate to verify Tcl scripts. This way, Tcl identifies which certificate is used for verifying the Tcl scripts. The name must match an existing configured trustpoint name, otherwise, the command is rejected with an error message on the console. You can enter the command multiple times and configure multiple trustpoint names. Once you enter the command, you cannot modify the trustpoint name. However, you can remove the trustpoint name using the no form of the command. You must individually remove each name. When the last name is removed, no signature checking is performed, and the untrusted script (that is, a script that has failed signature verification) action configured by the scripting tcl trustpoint untrusted command is also removed.
A Cisco IOS Crypto image software is required to enable this command and configure the Signed Tcl Scripts feature. The Crypto configuration commands enable the Cisco x.509 certificate storage. The scripting tcl trustpoint name command can be enabled after the Crypto configuration trustpoint commands are enabled.
The scripting tcl secure-mode command must be configured with the scripting tcl trustpoint name command to verify the integrity of Tcl script signatures run on the router. Both commands must be configured to fully operate this feature; otherwise, a syslog message is generated:
*Jun 13 17:53:31.659: %SYS-6-SCRIPTING_TCL_SECURE_TRUSTPOINT: scripting tcl secure-mode is enabled, however no scripting tcl trustpoint names configured, cannot verify signed TCL script.In addition, the crypto pki trustpoint name command provided should contain a certificate that matches the certificate that was originally used to generate the digital signature on the Tcl script.
Examples
The following example shows how the scripting tcl trustpoint name command is used to associate existing trustpoint names. Different names can be used for different departments with certificates:
Router(config)# crypto pki trustpoint mytrustRouter(ca-trustpoint)# enrolment terminalRouter(ca-trustpoint)# exitRouter(config)# crypto pki authenticate mytrustEnter the base 64 encoded CA certificate.End with a blank line or the word "quit" on a line by itselfMIIEuDCCA6CgAwIBAgIBADANBgkqhkiG9w0BAQQFADCBnjELMAkGA1UEBhMCVVMxEzARBgNVBAgTCkNhbGlmb3JuaWExETAPBgNVBAcTCFNhbiBKb3NlMRwwGgYDVQQKExNDaXNjbyBTeXN0ZW1zLCBJbmMuMQ4wDAYDVQQLEwVOU1NURzEWMBQGA1UEAxMNSm9obiBMYXV0bWFubjEhMB8GCSqGSIb3DQEJARYSamxhdXRtYW5AY2lzY28uY29tMB4XDTA2MTExNzE3NTgwMVoXDTA5MTExNjE3NTgwMVowgZ4xCzAJBgNVBAYTAlVTMRMwEQYDVQQIEwpDYWxpZm9ybmlhMREwDwYDVQQHEwhTYW4gSm9zZTEcMBoGA1UEChMTQ2lzY28gU3lzdGVtcywgSW5jLjEOMAwGA1UECxMFTlNTVEcxFjAUBgNVBAMTDUpvaG4gTGF1dG1hbm4xITAfBgkqhkiG9w0BCQEWEmpsYXV0bWFuQGNpc2NvLmNvbTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBALxtqTMCirMb+CdyWLuHoWAM8CEJDwQggL7MWBhoi3TSMd/ww2XBB9biBtdlH6jHsjCiOwAR5OorakwfPyf7mvRJ2PqJALs+Vn93VBKIG6rZUl4+wdOx686BVddIZvEJQPbROiYTzfazWV70aLMVbd7/B7vF1SG1YK9y1tX9p9nZyZ0x47OAXetwOaGinvlG7VNuTXaASBLUjCRZsIlzSBrXXedBzZ6+BuoWm1FK45EYSlag5Rt9RGXXMBqzx91iyhrJ3zDDmkExa45yKJETmAgDVMcpeteJtif47UDZJK30g4MbMyx/c8WGhmJ54qRL9BZEPmDxMQkNP10l8MAlQ8sCAwEAAaOB/jCB+zAdBgNVHQ4EFgQU9/ToDvbMR3JfJ4xEa4X47oNFq5kwgcsGA1UdIwSBwzCBwIAU9/ToDvbMR3JfJ4xEa4X47oNFq5mhgaSkgaEwgZ4xCzAJBgNVBAYTAlVTMRMwEQYDVQQIEwpDYWxpZm9ybmlhMREwDwYDVQQHEwhTYW4gSm9zZTEcMBoGA1UEChMTQ2lzY28gU3lzdGVtcywgSW5jLjEOMAwGA1UECxMFTlNTVEcxFjAUBgNVBAMTDUpvaG4gTGF1dG1hbm4xITAfBgkqhkiG9w0BCQEWEmpsYXV0bWFuQGNpc2NvLmNvbYIBADAMBgNVHRMEBTADAQH/MA0GCSqGSIb3DQEBBAUAA4IBAQBtEs/4MQeN9pT+XPCPg2ObQU8y2AadI+I34YK+fDHsFOh68hZhpszTN2VpNEvkFXpADhgr7DkNGtwTCla481v70iNFViQVL+inNrZwWMxoTnUNCK7Hc5kHkXt6cj0mvsefVUzxXl70mauhESRVlmYWrJxSsrEILerZYsuv5HbFdand+/rErmP2HVyfdntLnKdSzmXJ5lwE/Et2QtYNGor0OBlLesowfslR3LhHi4wn+5is7mALgNw/NuTiUr1zH18OeB4mwcpBIJsLaJu6ZUJQl7IqdswSa3fHd5qq0/k8P9z0YAYrf3+MFQr4ibvsYvHlO087o2Js1gW4qz34pqNhCertificate has the following attributes:Fingerprint MD5: 1E327DBB 330936EB 2FB8EACB 4FD1133EFingerprint SHA1: EE7FF9F4 05148842 B9D50FAC D76FDC9C E0703246% Do you accept this certificate? [yes/no]: yesTrustpoint CA certificate accepted.% Certificate successfully importedRouter(config)# scripting tcl secure-modeRouter(config)# scripting tcl trustpoint name mytrustRouter(config)# scripting tcl trustpoint name dept_accountingRouter(config)# scripting tcl trustpoint name dept_hrRelated Commands
scripting tcl secure-mode
Enables signature verification of the interactive Tcl scripts.
scripting tcl trustpoint untrusted
To allow the interactive Tool Command Language (Tcl) scripts to run regardless of the scripts failing the signature check, use the scripting tcl trustpoint untrusted command in global configuration mode. To disallow the interactive Tcl scripts to run regardless of the scripts failing the signature check, use the no form of this command.
scripting tcl trustpoint untrusted {execute | safe-execute | terminate}
no scripting tcl trustpoint untrusted
Syntax Description
Command Default
No script that fails signature verification can run; the script immediately stops.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
Use the scripting tcl trustpoint untrusted command to allow the interactive Tcl scripts to run regardless of the scripts failing the signature check or in untrusted mode. The untrusted script (that is, a script that has failed signature verification) is not safe to use.
Caution
The execute keyword is provided for internal testing purposes and to provide flexibility. For example in a situation where a certificate has expired but the other configurations are valid and you want to work with the existing configuration, then you can use the execute keyword to work around the expired certificate.
The safe-execute keyword allows the script to run in safe mode. You can use the tclsafe command and also enter the interactive Tcl shell safe mode to explore the safe mode Tcl commands that are available. In order to get a better understanding of what is available in this limited safe mode, use the tclsafe Exec command to explore the options.
The terminate keyword stops any script from running and reverts to default behavior. The default policy is to terminate. When the last trustpoint name is removed, the untrusted action is also removed. The untrusted action cannot be entered until at least one trustpoint name is configured for Tcl.
Note
Examples
The following example shows how to execute the Tcl script in safe mode if the signature verification fails:
Router(config)# scripting tcl trustpoint untrusted safe-executeRelated Commands
server (boomerang)
To configure the server address for a specified boomerang domain, use the server command in boomerang configuration mode. To remove this command from the configuration file and restore the system to its default condition with respect to this command, use the no form of this command.
server server-ip-address
no server server-ip-address
Syntax Description
Command Default
No default behavior or values.
Command Modes
Boomerang configuration
Command History
Usage Guidelines
The server command can be used only on a Director Response Protocol (DRP) agent. The boomerang client is the Director Response Protocol (DRP) agent.
Use the server command to specify a server address that is to be associated with a given domain name. This configuration overrides the server-to-DRP agent association that is configured on DistributedDirector.
Examples
The following example configures the server for a domain named www.boom1.com. The server address for www.boom1.com is 172.16.101.101:
Router(config)# ip drp domain www.boom1.comRouter(config-boomerang)# server 172.16.101.101Router# show running-config...ip drp domain www.boom1.comcontent-server 172.16.101.101Related Commands
set (EEM)
To set the value of a local Embedded Event Manager (EEM) applet variable, use the set command in applet configuration mode. To remove the value of an EEM applet variable, use the no form of this command.
set label _exit_status exit-value
no set label _exit_status exit-value
Syntax Description
Command Default
No EEM applet variable values are set.
Command Modes
Applet configuration
Command History
Usage Guidelines
In EEM applet configuration mode, three types of configuration statements are supported. The event commands are used to specify the event criteria to trigger the applet to run, the action commands are used to specify an action to perform when the EEM applet is triggered, and the set command is used to set the value of an EEM applet variable. Currently only the _exit_status variable is supported for the set command.
Examples
The following example shows how to set the _exit_status variable to represent a successful status after an event has occurred three times and an action has been performed:
Router(config)# event manager applet cli-matchRouter(config-applet)# event cli pattern {.*interface loopback*} sync yes occurs 3Router(config-applet)# action 1.0 cli command "no shutdown"Router(config-applet)# set 1.0 _exit_status 0Related Commands
event manager applet
Registers an event applet with the Embedded Event Manager and enters applet configuration mode.
set platform software trace
To set the trace level for a specific module within a process, use the set platform software trace command privileged EXEC or diagnostic mode command.
set platform software trace process hardware-module slot module trace-level
Syntax Description
Command Modes
Privileged EXEC (#)
Diagnostic (diag)Defaults
The default tracing level for all modules on the Cisco ASR 1000 series routers is critical.
Command History
Usage Guidelines
The module options vary by process and by hardware-module. Use the ? option when entering this command to see which module options are available with each keyword sequence.
Use the show platform software trace message command to view trace messages.
Trace files are stored in the tracelogs directory in the harddisk: file system. These files can be deleted without doing any harm to your router operation.
Trace file output is used for debugging. The trace level is a setting that determines how much information about a module should be stored in trace files. The levels are documented in Table 35.
Table 35 Tracing Levels and Descriptions
Trace level settings are leveled, meaning that every setting will contain all messages from the lower setting plus the messages from its own setting. For instance, setting the trace level to 3(error) ensures that the trace file will contain all output for the 0 (emergencies), 1 (alerts), 2 (critical), and 3 (error) settings. Setting the trace level to 4 (verbose) will ensure that all trace output for the specific module will be included in that trace file.
All trace levels are not user-configurable. Specifically, the alert, critical, and notice tracing levels cannot be set by users. If you wish to trace these messages, set the trace level to a higher level that will collect these messages.
Caution
Caution
Examples
In the following example, the trace level for the ACL module in the Forwarding Manager of the ESP processor in slot 0 is set to the informational tracing level (info).
set platform software trace forwarding-manager F0 acl infoRelated Commands
show platform software trace level
Displays trace levels for specified modules.
show platform software trace message
Displays trace messages.
shell environment load
To download Cisco IOS Shell (IOS.sh) environment from a specified file to the current TTY, use the shell environment load command in privileged EXEC mode.
shell environment load filename:URL {merge | replace}
Syntax Description
filename:URL
The URL of the shell environment file.
merge
Merge into the current shell environment.
replace
Replace the current shell environment
Command Modes
Privileged EXEC (#)
Command History
15.1(4)M
This command was introduced.
15.1(2)S
This command was integrated into Cisco IOS Release 15.1(2)S.
Usage Guidelines
Use the shell environment load command to download the Cisco IOS.sh environment from a specified file to the current terminal. Use the shell environment save command to save this specific file prior to loading the file using the shell environment load command.
Examples
This example shows how to save and then load a Cisco IOS.sh environment file and merge it into the current shell environment:
Router> enableRouter# configure terminalRouter(config)#Enter configuration commands, one per line. End with CNTL/Z.Router(config)# shell processing fullRouter# exitRouter# shell environment save disk0:URLRouter# shell environment load disk0:URL mergeRelated Commands
shell environment save
Saves a Cisco IOS.sh environment functions to a specific file.
show shell environment
Displays a Cisco IOS.sh environment information.
shell environment save
To save all current Cisco IOS Shell (IOS.sh) environment functions to a specific file, use the shell environment save command in privileged EXEC mode.
shell environment save filename:URL
Syntax Description
Command Modes
Privileged EXEC (#)
Command History
15.1(4)M
This command was introduced.
15.1(2)S
This command was integrated into Cisco IOS Release 15.1(2)S.
Usage Guidelines
Use the shell environment save command to save all current shell environment, except built-in shell functions, to a specified file. Then only you can use the shell environment load command to load the Cisco IOS.sh environment in the specific file on the current terminal.
Examples
This example shows how to save a Cisco IOS.sh environment file:
Router> enableRouter# configure terminalRouter(config)#Enter configuration commands, one per line. End with CNTL/Z.Router(config)# shell processing fullRouter# exitRouter# shell environment save disk0:URLRelated Commands
shell environment load
Downloads a Cisco IOS.sh environment from a specified file to the current TTY.
show shell environment
Displays a Cisco IOS.sh environment information.
shell init
To enable Cisco IOS Shell (IOS.sh) initialization options, use the shell init command in global configuration mode. To disable the Cisco IOS.sh initialization options, use the no form of this command.
shell init {filename:URL no-exec}
no shell init
Syntax Description
filename:URL
The URL of the shell environment file.
no-exec
Stores the initialization filename and loads the saved environment from that file at the next rebooting of the router.
Defaults
Cisco IOS.sh initialization is disabled.
Command Modes
Global configuration (config)
Command History
15.1(4)M
This command was introduced.
15.1(2)S
This command was integrated into Cisco IOS Release 15.1(2)S.
Usage Guidelines
Use the shell init command to provide Cisco IOS.sh environment access to everyone who logs on to the router. If this command is configured, during system boot up, the router automatically reads and loads the content of the shell configuration from the given file which includes the user-defined variables and functions created previously. It copies the saved files into the Cisco IOS.sh environment. When you use the no-exec keyword, it allows you to store the initialization filename and loads the saved environment from that file at the next rebooting of the router.
Note
Examples
This example shows how to enable Cisco IOS.sh processing in all IOS modes:
Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# shell processing fullRouter(config)# shell init disk0:URLRelated Commands
shell processing
To restore the default behavior of Cisco IOS Shell (IOS.sh) processing, use the shell processing command in global configuration mode. To disable the Cisco IOS.sh functions, use the no form of this command.
shell processing {full}
no shell processing
Syntax Description
Defaults
Cisco IOS.sh processing is enabled for other applications to use the shell functions.
Command Modes
Global configuration (config)
Command History
15.1(4)M
This command was introduced.
15.1(2)S
This command was integrated into Cisco IOS Release 15.1(2)S.
Usage Guidelines
To enable shell processing and access all its functions, it is recommended that you use the shell processing full command. This allows you the ability to use shell processing in the configuration level without entering the terminal shell command on your terminal at the EXEC level. Use the no shell processing command to disable Cisco IOS.sh processing on the router. To restore the default Cisco IOS.sh processing, use the shell processing command. To reenable shell processing and access all its functions, it is recommended that you use the shell processing full command.
You can turn shell processing on the terminal by using the terminal shell EXEC command. However shell processing feature is only on while the terminal is running. Once the terminal is turned off, shell processing is off. When the terminal shell command is used, shell processing is not visible in the running configuration because it is only on the terminal level and is not in the configuration level. It is convenient to use the terminal shell command at the terminal level to quickly access the Cisco IOS.sh man commands.
To enable shell processing and access all its functions in the configuration, it is recommended that you use the shell processing full command.
Examples
This example shows how to enable Cisco IOS.sh processing in all Cisco IOS configuration modes:
Router> enableRouter# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# shell processing full
show buffers leak
To display the details of all the buffers that are older than one minute in the system, use the show buffers leak command in user EXEC or privileged EXEC mode.
show buffers leak [resource user]
Syntax Description
resource user
(Optional) Displays the resource user information to which the leaked buffers belong to.
Command Modes
User EXEC (>)
Privileged EXEC (#)Command History
12.3(14)T
This command was introduced.
12.2(33)SRB
This command was integrated into Cisco IOS Release 12.2(33)SRB.
Examples
The following is sample output from the show buffers leak command:
Router# show buffers leakHeader DataArea Pool Size Link Enc Flags Input Output User6488F464 E000084 Small 74 0 0 10 None None EEM ED Sy6488FB5C E000304 Small 74 0 0 10 None None EEM ED Sy648905D0 E0006C4 Small 61 0 0 0 None None EEM ED Sy648913C0 E000BC4 Small 74 0 0 10 None None EEM ED Sy6489173C E000D04 Small 74 0 0 10 None None EEM ED Sy648921B0 E0010C4 Small 60 0 0 0 None None Init6489252C E001204 Small 103 0 0 10 None None EEM ED Sy64892C24 E001484 Small 74 0 0 10 None None EEM ED Sy64892FA0 E0015C4 Small 74 0 0 10 None None EEM ED Sy64893A14 E001984 Small 74 0 0 10 None None EEM ED Sy64893D90 E001AC4 Small 61 0 0 0 None None EEM ED Sy64894804 E001E84 Small 61 0 0 0 None None EEM ED Sy6517CB64 E32F944 Small 74 0 0 10 None None EEM ED Sy6517D25C E176D44 Small 74 0 0 10 None None EEM ED Sy6517D5D8 E176E84 Small 74 0 0 10 None None EEM ED Sy6517D954 E209A84 Small 74 0 0 10 None None EEM ED Sy6517E744 E209D04 Small 61 0 0 0 None None EEM ED Sy6517EE3C E29CBC4 Small 61 0 0 0 None None EEM ED Sy65180324 E177844 Small 74 0 0 10 None None EEM ED Sy65180D98 E177C04 Small 61 0 0 0 None None EEM ED Sy65E1F3A0 E4431A4 Small 102 0 0 0 None None EEM ED Sy64895278 E002644 Middl 191 0 0 10 None None EEM ED Sy64895CEC E003004 Middl 173 0 0 10 None None EEM ED Sy64896068 E003344 Middl 176 0 0 10 None None EEM ED Sy648963E4 E003684 Middl 191 0 0 10 None None EEM ED Sy64896E58 E004044 Middl 109 0 0 10 None None EEM ED Sy64897C48 E004D44 Middl 194 0 0 10 None None EEM ED Sy65181F04 E330844 Middl 173 0 0 10 None None EEM ED Sy65183070 E3C3644 Middl 105 0 0 10 None None EEM ED Sy65DF9558 E4746E4 Middl 107 0 0 0 None None EEM ED Sy65DFA6C4 E475724 Middl 116 0 0 0 None None EEM ED Sy65DFADBC E475DA4 Middl 115 0 0 0 None None EEM ED Sy65DFC620 E477464 Middl 110 0 0 0 None None EEM ED Sy64C64AE0 0 FS He 0 0 3 0 None None Init64C64E5C 0 FS He 0 0 3 0 None None Init64C651D8 0 FS He 0 0 3 0 None None Init64C65554 0 FS He 0 0 0 0 None None Init64C658D0 0 FS He 0 0 0 0 None None Init64C65C4C 0 FS He 0 0 0 0 None None Init64C65FC8 0 FS He 0 0 0 0 None None Init64C66344 0 FS He 0 0 0 0 None None Init64D6164C 0 FS He 0 0 0 0 None None Init64EB9D10 0 FS He 0 0 0 0 None None Init6523EE14 0 FS He 0 0 0 0 None None Init65413648 0 FS He 0 0 0 0 None None InitThe following is sample output from the show buffers leak resource user command:
Router# show buffers leak resource userResource User: EEM ED Syslog count: 32Resource User: Init count: 2Resource User: *Dead* count: 2Resource User: IPC Seat Manag count: 11Resource User: XDR mcast count: 2Table 36 describes the significant fields shown in the display.
Related Commands
buffer public
Enters the buffer owner configuration mode and sets thresholds for buffer usage.
buffer tune automatic
Enables automatic buffer tuning.
show buffers tune
To display the details of automatic tuning of buffers, use the show buffers tune command in user EXEC or privileged EXEC mode.
show buffers tune
Syntax Description
This command has no arguments or keywords.
Command Modes
User EXEC (>)
Privileged EXEC (#)Command History
12.3(14)T
This command was introduced.
12.2(33)SRB
This command was integrated into Cisco IOS Release 12.2(33)SRB.
Examples
The following is sample output from the show buffers tune command:
Router# show buffers tuneTuning happened for the pool SmallTuning happened at 20:47:25Oldvaluespermanent:50 minfree:20 maxfree:150Newvaluespermanent:61 minfree:15 maxfree:76Tuning happened for the pool MiddleTuning happened at 20:47:25Oldvaluespermanent:25 minfree:10 maxfree:150Newvaluespermanet:36 minfree:9 maxfree:45Table 37 describes the significant fields shown in the display.
Related Commands
show buffers usage
To display the details of the buffer usage pattern in a specified buffer pool, use the show buffers usage command in user EXEC or privileged EXEC mode.
show buffers usage [pool pool-name]
Syntax Description
Command Modes
User EXEC (>)
Privileged EXEC (#)Command History
12.3(14)T
This command was introduced.
12.2(33)SRB
This command was integrated into Cisco IOS Release 12.2(33)SRB.
Examples
The following is sample output from the show buffers usage command:
Router# show buffers usageStatistics for the Small poolCaller pc : 0x626BA9E0 count: 20Resource User: EEM ED Sys count: 20Caller pc : 0x60C71F8C count: 1Resource User: Init count: 1Number of Buffers used by packets generated by system: 62Number of Buffers used by incoming packets: 0Statistics for the Middle poolCaller pc : 0x626BA9E0 count: 12Resource User: EEM ED Sys count: 12Number of Buffers used by packets generated by system: 41Number of Buffers used by incoming packets: 0Statistics for the Big poolNumber of Buffers used by packets generated by system: 50Number of Buffers used by incoming packets: 0Statistics for the VeryBig poolNumber of Buffers used by packets generated by system: 10Number of Buffers used by incoming packets: 0Statistics for the Large poolNumber of Buffers used by packets generated by system: 0Number of Buffers used by incoming packets: 0Statistics for the Huge poolNumber of Buffers used by packets generated by system: 0Number of Buffers used by incoming packets: 0Statistics for the IPC poolNumber of Buffers used by packets generated by system: 2Number of Buffers used by incoming packets: 0Statistics for the Header poolNumber of Buffers used by packets generated by system: 511Number of Buffers used by incoming packets: 0Statistics for the FS Header poolCaller pc : 0x608F68FC count: 9Resource User: Init count: 12Caller pc : 0x61A21D3C count: 1Caller pc : 0x60643FF8 count: 1Caller pc : 0x61C526C4 count: 1Number of Buffers used by packets generated by system: 28Number of Buffers used by incoming packets: 0The following is sample output from the show buffers usage pool command for the pool named small:
Router# show buffers usage pool smallStatistics for the Small poolCaller pc : 0x626BA9E0 count: 20Resource User: EEM ED Sys count: 20Caller pc : 0x60C71F8C count: 1Resource User: Init count: 1Number of Buffers used by packets generated by system: 62Number of Buffers used by incoming packets: 0Related Commands
buffer public
Enters buffer owner configuration mode and sets thresholds for buffer usage.
show buffers leak
Displays details of the buffers that have leaked.
show calendar
To display the current time and date setting for the hardware clock, use the show calendar command in EXEC mode:
show calendar
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Usage Guidelines
Some platforms have a hardware clock (calendar) which is separate from the software clock. The hardware clock is battery operated, and runs continuously, even if the router is powered off or rebooted.
You can compare the time and date shown with this command with the time and date listed via the show clock EXEC command to verify that the hardware clock and software clock are synchronized with each other. The time displayed is relative to the configured time zone.
Examples
In the following sample display, the hardware clock indicates the time stamp of 12:13:44 p.m. on Friday, July 19, 1996:
Router> show calendar12:13:44 PST Fri Jul 19 1996Related Commands
show cdp
To display global Cisco Discovery Protocol (CDP) information, including timer and hold-time information, use the show cdp command in privileged EXEC mode.
show cdp [vlan vlan]
Syntax Description
vlan vlan
(Optional) Specifies a VLAN. Limits the display of switch port information to the specified VLAN. Range: 1 to 4094.
Command Default
No default behavior or values.
Command Modes
EXEC (#)
Privileged EXEC (>)Command History
Usage Guidelines
Cisco IOS Release 12.2(33)SXI and later releases allow you to limit the display of switch port information to the specified VLAN.
Examples
The following example shows that the current router is sending CDP advertisements every 1 minute (the default setting for the cdp timer global configuration command). Also shown is that the current router directs its neighbors to hold its CDP advertisements for 3 minutes (the default for the cdp holdtime global configuration command), and that the router is enabled to send CDP Version 2 advertisements:
Router# show cdpGlobal CDP information:Sending CDP packets every 60 secondsSending a holdtime value of 180 secondsSending CDPv2 advertisements is enabledThe following example shows how to limit the displayed CDP information to a specific VLAN:
Router# show cdp vlan 11Global CDP information:Sending CDP packets every 60 secondsSending a holdtime value of 180 secondsSending CDPv2 advertisements is enabledTable 38 describes the significant fields shown in the display.
Related Commands
show cdp entry
To display information about a specific neighboring device discovered using Cisco Discovery Protocol (CDP), use the show cdp entry command in privileged EXEC mode.
show cdp entry {* | device-name[*]} [version] [protocol]
Syntax Description
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the show cdp entry command. Information about the neighbor device.cisco.com is displayed, including device ID, protocols and addresses, platform, interface, hold time, and version.
Router# show cdp entry device.cisco.comDevice ID: device.cisco.comEntry address(es):IP address: 10.1.17.24IPv6 address: FE80::203:E3FF:FE6A:BF81 (link-local)IPv6 address: 4000::BC:0:0:C0A8:BC06 (global unicast)CLNS address: 490001.1111.1111.1111.00Platform: cisco 3640, Capabilities: RouterInterface: Ethernet0/1, Port ID (outgoing port): Ethernet0/1Holdtime : 160 secVersion :Cisco Internetwork Operating System SoftwareIOS (tm) 3600 Software (C3640-A2IS-M), Experimental Version 12.2Copyright (c) 1986-2001 by cisco Systems, Inc.Compiled Wed 08-Aug-01 12:39 by joeuserThe following is sample output from the show cdp entry version command. Only information about the version of software running on device.cisco.com is displayed.
Router# show cdp entry device.cisco.com versionVersion information for device.cisco.com:Cisco Internetwork Operating System SoftwareIOS (tm) 3600 Software (C3640-A2IS-M), Experimental Version 12.2Copyright (c) 1986-2001 by cisco Systems, Inc.Compiled Wed 08-Aug-01 12:39 by joeuserThe following is sample output from the show cdp entry protocol command. Only information about the protocols enabled on device.cisco.com is displayed.
Router# show cdp entry device.cisco.com protocolProtocol information for device.cisco.com:IP address: 10.1.17.24IPv6 address: FE80::203:E3FF:FE6A:BF81 (link-local)IPv6 address: 4000::BC:0:0:C0A8:BC06 (global unicast)CLNS address: 490001.1111.1111.1111.00Related Commands
show cdp interface
To display information about the interfaces on which Cisco Discovery Protocol (CDP) is enabled, use the show cdp interface command in privileged EXEC mode.
show cdp interface [type number]
Syntax Description
type
(Optional) Type of interface about which you want information.
number
(Optional) Number of the interface about which you want information.
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the show cdp interface command. Status information and information about CDP timer and hold-time settings is displayed for all interfaces on which CDP is enabled.
Router# show cdp interfaceSerial0 is up, line protocol is up, encapsulation is SMDSSending CDP packets every 60 secondsHoldtime is 180 secondsEthernet0 is up, line protocol is up, encapsulation is ARPASending CDP packets every 60 secondsHoldtime is 180 secondsThe following is sample output from the show cdp interface command with an interface specified. Status information and information about CDP timer and hold-time settings is displayed for Ethernet interface 0 only.
Router# show cdp interface ethernet 0Ethernet0 is up, line protocol is up, encapsulation is ARPASending CDP packets every 60 secondsHoldtime is 180 secondsRelated Commands
show cdp neighbors
To display detailed information about neighboring devices discovered using Cisco Discovery Protocol, use the show cdp neighbors command in privileged EXEC mode.
show cdp neighbors [type number] [detail]
Syntax Description
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
The vlan keyword is supported in Catalyst 6500 series switches that are configured with a Supervisor Engine 2.
The port-channel values are from 0 to 282; values from 257 to 282 are supported on the call switching module (CSM) and the firewall services module (FWSM) only.
Examples
The following is sample output from the show cdp neighbors command:
Router# show cdp neighborsCapability Codes:R - Router, T - Trans Bridge, B - Source Route Bridge S - Switch,H - Host, I - IGMP, r - RepeaterDevice ID Local Intrfce Holdtme Capability Platform Port IDjoe Eth 0 133 R 4500 Eth 0sam Eth 0 152 R AS5200 Eth 0terri Eth 0 144 R 3640 Eth0/0maine Eth 0 141 RP1 Eth 0/0sancho Eth 0 164 7206 Eth 1/0Table 39 describes the fields shown in the display.
The following is sample output for one neighbor from the show cdp neighbors detail command. Additional detail is shown about neighbors, including network addresses, enabled protocols, and software version.
Router# show cdp neighbors detailDevice ID: device.cisco.comEntry address(es):IPv6 address: FE80::203:E3FF:FE6A:BF81 (link-local)IPv6 address: 4000::BC:0:0:C0A8:BC06 (global unicast)Platform: cisco 3640, Capabilities: RouterInterface: Ethernet0/1, Port ID (outgoing port): Ethernet0/1Holdtime : 160 secVersion :Cisco Internetwork Operating System SoftwareIOS (tm) 3600 Software (C3640-A2IS-M), Version 12.2(25)SEB4, RELE)Duplex Mode: halfNative VLAN: 42VTP Management Domain: `Accounting Group'Table 40 describes the fields shown in the display.
Related Commands
show cdp tlv
To display information about Cisco Discovery Protocol (CDP) Type-Length-Values (TLVs), use the show cdp tlv command in privileged EXEC mode.
show cdp tlv {app interface type number | location [all | civic | elin] [interface type number] | location-server [interface type number]}
Syntax Description
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
You can use the show cdp tlv command to verify the TLVs configured on CDP. The show cdp tlv command displays location-specific information for an interface, if an interface is specified; otherwise, it displays location-specific information for all interfaces. You can also choose to display location-specific information for civic, ELIN, or all TLVs.
Examples
The following example shows how to display location-specific information for all TLVs:
Router# show cdp tlv location civic interface gigabitEthernet 3/0/2No CIVIC Location received from neighbor(switch1)Interface (GigabitEthernet3/0/2), Civic country code: USCA type: 3, Len: 9, Value: bangaloreCA type: 24, Len: 6, Value: 560087CA type: 25, Len: 18, Value: CessnaBusinessParkCA type: 34, Len: 13, Value: OuterRingRoadTable 41 describes the significant fields shown in the display.
Related Commands
show cdp traffic
To display information about traffic between devices gathered using Cisco Discovery Protocol (CDP), use the show cdp traffic command in privileged EXEC mode.
show cdp traffic
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Examples
The following is sample output from the show cdp traffic command:
Router# show cdp trafficTotal packets output: 543, Input: 333Hdr syntax: 0, Chksum error: 0, Encaps failed: 0No memory: 0, Invalid: 0, Fragmented: 0CDP version 1 advertisements output: 191, Input: 187CDP version 2 advertisements output: 352, Input: 146Table 42 describes the significant fields shown in the display.
Related Commands
show clock
To display the time and date from the system software clock, use the show clock command in user EXEC or privileged EXEC mode.
show clock [detail]
Syntax Description
detail
(Optional) Indicates the clock source (NTP, VINES, hardware clock, and so on) and the current summer-time setting (if any).
Command Modes
User EXEC
Privileged EXECCommand History
Usage Guidelines
The software clock keeps an "authoritative" flag that indicates whether the time is authoritative (believed to be accurate). If the software clock has been set by a timing source (for example, via NTP), the flag is set. If the time is not authoritative, it will be used only for display purposes. Until the clock is authoritative and the "authoritative" flag is set, the flag prevents peers from synchronizing to the software clock.
The symbol that precedes the show clock display indicates the following:
These symbols are also used in NTP-based timestamping, such as for syslog (SEM) messages.
Note
Examples
The following sample output shows that the current clock is authoritative and that the time source is NTP:
Router> show clock detail15:29:03.158 PST Tue Feb 25 2003Time source is NTPThe following example shows the current clock is authoritative, but NTP is not yet synchronized:
Router> show clock.16:42:35.597 UTC Tue Feb 25 2003Related Commands
clock set
Manually sets the software clock.
show calendar
Displays the current time and date setting of the system hardware clock.
show cns config connections
To display the status of the Cisco Networking Services (CNS) event agent connection, use the show cns config connections command in privileged EXEC mode.
show cns config connections
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC (#)
Command History
12.2(8)T
This command was introduced. This command replaces the show cns config status command.
Usage Guidelines
Use the show cns config connections command to determine whether the CNS event agent is connecting to the gateway, connected, or active, and to display the gateway used by the event agent and its IP address and port number.
Examples
The following is sample output from the show cns config connections command:
Router# show cns config connectionsThe partial configuration agent is enabled.Configuration server: 10.1.1.1Port number: 80Encryption: disabledConfig id: test1Connection Status: Connection not active.Related Commands
show cns config outstanding
To display information about incremental (partial) Cisco Networking Services (CNS) configurations that have started but not yet completed, use the show cns config outstanding command in privileged EXEC mode.
show cns config outstanding
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
Use the show cns config outstanding command to display information about outstanding incremental (partial) configurations that have started but not yet completed, including the following:
•
•
•
Examples
The following is sample output from the show cns config outstanding command:
Router# show cns config outstandingThe outstanding configuration information:queue id identifier config-id1 identifierREAD config_idREADRelated Commands
show cns config stats
To display statistics about the Cisco Networking Services (CNS) configuration agent, use the show cns config stats command in privileged EXEC mode.
show cns config stats
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
This command displays the following statistics on the CNS configuration agent:
•
•
•
•
•
•
•
Examples
The following is sample output from the show cns config stats command:
Router# show cns config stats6 configuration requests received.4 configurations completed.1 configurations failed.1 configurations pending.0 configurations cancelled.The time of last received configuration is *May 5 2003 10:42:15 UTC.Initial Config received *May 5 2003 10:45:15 UTC.Related Commands
show cns config status
Note
To display the status of the Cisco Networking Services (CNS) Configuration Agent, use the show cns config status command in EXEC mode.
show cns config status
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC (>)
Command History
Usage Guidelines
This command displays the status of the Configuration Agent. Use this option to display the following information about the Configuration Agent:
•
•
•
Related Commands
show cns event connections
To display the status of the Cisco Networking Services (CNS) event agent connection, use the show cns event connections command in privileged EXEC mode.
show cns event connections
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
Use the show cns event connections command to display the status of the event agent connection—such as whether it is connecting to the gateway, connected, or active—and to display the gateway used by the event agent and its IP address and port number.
Examples
The following example displays the IP address and port number of the primary and backup gateways:
Router# show cns event connectionsThe currently configured primary event gateway:hostname is 10.1.1.1.port number is 11011.Event-Id is Internal test1Keepalive setting:none.Connection status:Connection Established.The currently configured backup event gateway:none.The currently connected event gateway:hostname is 10.1.1.1.port number is 11011.Related Commands
show cns event stats
Displays statistics about the CNS event agent connection.
show cns event subject
Displays a list of subjects about the CNS event agent connection.
show cns event gateway
To display information about the Cisco Networking Services (CNS) Event Agent, use the show cns event gateway command in EXEC mode.
show cns event gateway
Syntax Description
This command has no arguments or keywords.
Command Default
No default behavior or values.
Command Modes
EXEC
Command History
12.2(2)T
This command was introduced.
12.0(18)ST
This command was integrated into Cisco IOS Release 12.0 (18)ST
Usage Guidelines
Use this command to display the following information about CNS gateways:
•
–
–
•
–
–
•
–
–
Related Commands
show cns event stats
To display statistics about the Cisco Networking Services (CNS) event agent connection, use the show cns event stats command in privileged EXEC mode.
show cns event stats
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
Use this command to display the following statistics for the CNS event agent:
•
•
•
•
•
•
•
•
•
•
Examples
The following example displays statistics for the CNS event agent:
Router# show cns event stats0 events received.1 events sent.0 events not processed.0 events in the queue.0 events sent to other IOS applications.Event agent stats last cleared at Apr 4 2003 00:55:25 UTCNo events received since stats clearedThe time stamp of the last received event is *Mar 30 2003 11:04:08 UTCThe time stamp of the last sent event is *Apr 11 2003 22:21:23 UTC3 applications are using the event agent.0 subjects subscribed.1 subjects produced.0 subjects replied.Related Commands
show cns event status
To display information about the Cisco Networking Services (CNS) Event Agent, use the show cns event status command in EXEC mode.
show cns event status
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
12.2(2)T
This command was introduced.
12.0(18)ST
This command was integrated into Cisco IOS Release 12.0 (18)ST.
Usage Guidelines
Use this command to display the following information about the CNS Event Agent:
•
–
–
•
–
–
•
Related Commands
show cns event subject
To display a list of subjects about the Cisco Networking Services (CNS) event agent connection, use the show cns event subject command in privileged EXEC mode.
show cns event subject [name]
Syntax Description
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
Use the show cns event subject command to display a list of subjects of the event agent that are subscribed to by applications.
Examples
The following example displays the IP address and port number of the primary and backup gateways:
Router# show cns event subjectThe list of subjects subscribed by applications.cisco.cns.mibaccess:requestcisco.cns.config.loadcisco.cns.config.rebootcisco.cns.exec.cmdRelated Commands
show cns event connections
Displays the status of the CNS event agent connection.
show cns event stats
Displays statistics about the CNS event agent connection.
show cns image connections
To display the status of the Cisco Networking Services (CNS) image management server HTTP connections, use the show cns image connections command in privileged EXEC mode.
show cns image connections
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
Use the show cns image connections command when troubleshooting HTTP connection problems with the CNS image server. The output displays the following information:
•
•
•
Examples
The following is sample output from the show cns image connections command:
Router# show cns image connectionsCNS Image Agent: HTTP connectionsConnection attempts 1never connected:0 Abrupt disconnect:0Last successful connection at 11:45:02.000 UTC Mon May 6 2003Related Commands
show cns image inventory
Displays inventory information about the CNS image agent.
show cns image status
Displays status information about the CNS image agent.
show cns image inventory
To provide a dump of Cisco Networking Services (CNS) image inventory information in extensible markup language (XML) format, use the show cns image inventory command in privileged EXEC mode.
show cns image inventory
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
To view the XML output in a better format, paste the content into a text file and use an XML viewing tool.
Examples
The following is sample output from the show cns image inventory command:
Router# show cns image inventoryInventory Report<imageInventoryReport><deviceName><imageID>Router</imageID><hostName>Router</hoIOS (tm) C2600 Software (C2600-I-M), Experimental Version 12.3(20030414:081500)]Copyright (c) 1986-2003 by cisco Systems, Inc.Compiled Mon 14-Apr-03 02:03 by engineer</versionString><imageFile>tftp://10.25>Related Commands
show cns image connections
Displays connection information for the CNS image agent.
show cns image status
Displays status information about the CNS image agent.
show cns image status
To display status information about the Cisco Networking Services (CNS) image agent, use the show cns image status command in privileged EXEC mode.
show cns image 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 status information about the CNS image agent:
•
•
•
•
•
•
•
Examples
The following is sample output from the show cns image status command:
Router# show cns image statusLast upgrade started at 11:45:02.000 UTC Mon May 6 2003Last upgrade ended at 11:56:04.000 UTC Mon May 6 2003 status SUCCESSLast successful upgrade ended at 00:00:00.000 UTC Mon May 6 2003Last failed upgrade ended at 00:00:00.000 UTC Wed Apr 16 2003Number of failed upgrades: 2Number of successful upgrades: 6messages received: 12receive errors: 5Transmit StatusTX Attempts:4Successes:3 Failures 2Related Commands
show cns image connections
Displays connection information for the CNS image agent.
show cns image inventory
Displays image inventory information in XML format.
show ethernet oam status
To display Ethernet operations, maintenance, and administration (OAM) configurations for all interfaces or for a specific interface, use the show ethernet oam status command in privileged EXEC mode.
show ethernet oam status [interface type slot/[subslot/]port | vlan vlan]
Syntax Description
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
Use this command to display the runtime settings of link-monitoring and general OAM operations for all interfaces or for a specific interface.
OAM must be operational on the interface or interfaces before you issue this command.
Cisco IOS Release 12.2(33)SXI and later releases allow you to limit the display of switch port information to the specified VLAN.
Examples
The following example shows output from a show ethernet oam status command for interface GigabitEthernet 6/11:
Router# show ethernet oam status interface gigabitethernet 6/11GigabitEthernet6/11General-------Mode: activePDU max rate: 10 packets per secondPDU min rate: 1 packet per 1 secondLink timeout: 5 secondsHigh threshold action: no actionLink Monitoring---------------Status: supported (on)Symbol Period ErrorWindow: 1 million symbolsLow threshold: 1 error symbol(s)High threshold: noneFrame ErrorWindow: 10 x 100 millisecondsLow threshold: 1 error frame(s)High threshold: noneFrame Period ErrorWindow: 1 x 100,000 framesLow threshold: 1 error frame(s)High threshold: noneFrame Seconds ErrorWindow: 600 x 100 millisecondsLow threshold: 1 error second(s)High threshold: noneTable 43 describes the significant fields shown in the display.
Related Commands
