Feedback
Table Of Contents
Fundamentals Command Reference
copy running-config startup-config
copy startup-config running-config
show hardware internal inventory
Fundamentals Command Reference
Revised: September 2011This chapter includes the Cisco MXE-OS commands used for basic operating system configurations and settings.
banner motd
To configure the message-of-the-day (MOTD) banner that displays when a user logs in to the device, use the banner motd command. To revert to the default, use the no form of this command.
banner motd delimiting-character message delimiting-character
no banner motd
Syntax Description
Defaults
None
Command Modes
Global configuration
Supported User Rolesnetwork-admin
Command History
Usage Guidelines
To create a multiple-line MOTD banner, press Enter before typing the delimiting character to start a new line.
Examples
This example shows how to configure a single-line MOTD banner:
mxe# configure terminalmxe(config)# banner motd #Unauthorized access to this device is prohibited!#This example shows how to configure a multiple-line MOTD banner:
mxe# configure terminalmxe(config)# banner motd #Welcome to authorized users!> Unauthorized access prohibited.#This example shows how to revert to the default MOTD banner:
mxe# configure terminalmxe(config)# no banner motdRelated Commands
clear cli history
To clear the command history, use the clear cli history command.
clear cli history
Syntax Description
This command has no arguments or keywords.
Defaults
None
Command Modes
EXEC
Supported User Rolesnetwork-admin
network-operatorCommand History
Usage Guidelines
Use the show cli history command to display the history of the commands that you entered at the command-line interface (CLI).
Examples
This example shows how to clear the command history:
mxe# clear cli historyRelated Commands
clear cli history-size
To clear the command history size, use the clear cli history-size command.
clear cli history-size
Syntax Description
This command has no arguments or keywords.
Defaults
None
Command Modes
EXEC
Supported User Rolesnetwork-admin
network-operatorCommand History
Usage Guidelines
Use the clear cli history-size command to reset the history size to the default, 10. The clear cli history command clears the entire buffer.
Examples
This example shows how to clear the command history and reset the history size to 10:
mxe# clear cli history-sizeRelated Commands
Clears all command history.
Configures the maximum number of lines stored in the command history.
Displays the command history.
clear system reset-reason
To clear the system reset history and the reset reasons, use the clear system reset-reason command.
clear system reset-reason
Syntax Description
This command has no arguments or keywords.
Defaults
None
Command Modes
EXEC
Supported User Rolesnetwork-admin
network-operatorCommand History
Usage Guidelines
None
Examples
This example shows how to clear the reset history:
mxe# clear system reset-reasonRelated Commands
cli history-size
To set the maximum number of lines stored in the command history, use the cli history-size command.
cli history-size [number]
Syntax Description
number
(Optional) Specify the maximum number of lines that can be stored in the command history. The range is 2 to 512; the default is 10.
Defaults
10 lines
Command Modes
EXEC
Supported User Rolesnetwork-admin
network-operatorCommand History
Usage Guidelines
Use the show cli history command to display the history of the commands that you entered at the command-line interface (CLI). The cli history-size command sets the maximum number of stored command lines. The clear cli history command clears all entries, the clear cli history-size command resets cli history-size to the default (10).
Examples
This example shows how to set the command history to a maximum of 50 lines:
mxe# cli history-size 50Related Commands
Clears all command history.
Clears the command history and resets the maximum number of stored commands to the default (10).
Displays the command history.
clock set
To manually set the clock on a Cisco MXE-OS device, use the clock set command. To remove the clocks set configuration, use the no form of this command.
clock set time day month year
no clock set time day month year
Syntax Description
Defaults
None
Command Modes
Global configuration
Supported User Rolesnetwork-admin
Command History
Usage Guidelines
Use this command when you cannot synchronize your device with an outside clock source, such as NTP.
You can use this command only when NTP is disabled.
Examples
This example shows how to manually configure the clock:
mxe# configure terminalmxe(config)# clock set 09:00:00 1 June 2008Related Commands
clock summer-time
To configure the summertime (daylight saving time) offset, use the clock summer-time command. To remove the summertime offset configuration, use the no form of this command.
clock summer-time zone-name start-week start-day start-month start-time end-week end-day end-month end-time offset-minutes
no clock summer-time
Syntax Description
Defaults
No summertime offset
Command Modes
Global configuration
Supported User Rolesnetwork-admin
Command History
Usage Guidelines
None
Examples
This example shows how to configure the offset for summer-time or daylight saving time:
mxe# configure terminalmxe(config)# clock summer-time PDT 1 Sunday March 02:00 1 Sunday November 02:00 60This example shows how to remove a summer-time offset configuration:
mxe# configure terminalmxe(config)# no clock summer-timeRelated Commands
clock timezone
To configure the time-zone offset from Coordinated Universal Time (UTC), use the clock timezone command. To remove the timezone offset, use the no form of this command.
clock timezone zone-name offset-hours offset-minutes
no clock timezone
Syntax Description
Defaults
No time-zone offset
Command Modes
Global configuration
Supported User Rolesnetwork-admin
Command History
1.0
This command was introduced.
1.2
Table 1-1 was added.
1.3
Table 1-2 was added.
Usage Guidelines
Use this command to offset the device clock from UTC.
When you are using a Cisco TelePresence System (CTS) Manager, you should apply the same time-zone offset value on the CTS Manager and on the Cisco MXE-OS device.
Table 1-1 lists the world time-zone offset values. Table 1-2 lists the Internet Engineering Task Force (IETF) time-zone offset values.
Examples
This example shows how to configure the time zone offset from UTC to 5 hours and 0 minutes:
mxe# configure terminalmxe(config)# clock timezone EST 5 0This example shows how to remove a time-zone offset:
mxe# configure terminalmxe(config)# no clock timezoneRelated Commands
configure terminal
To enter global configuration mode, use the configure terminal command.
configure terminal
Syntax Description
This command has no arguments or keywords.
Defaults
None
Command Modes
EXEC
Supported User Rolesnetwork-admin
Command History
Usage Guidelines
Use this command to enter global configuration mode. The commands that you enter in this mode are written to the running configuration file after you press the Enter key.
Examples
This example shows how to enter global configuration mode:
mxe# configure terminalmxe(config)#Related Commands
copy
To copy the startup or running configuration file to or from a destination, use the copy command.
copy source-url destination-url
Syntax Description
Defaults
None
Command Modes
EXEC
Supported User Rolesnetwork-admin
Command History
1.0
This command was introduced.
1.2
The ftp, sftp, and tftp keywords were added. The copy running-config and the copy startup-config commands were replaced by the copy command.
Usage Guidelines
The copy command allows you to copy a file (such as a system image or configuration file) from one location to another location. The source and destination for the file is specified by using a Cisco MXE-OS file system URL, which allows you to specify a local or remote file location. The file system being used (such as a local memory source or a remote server) determines the syntax used in the command.
You can enter on the command line all necessary source- and destination-URL information and the username to use, or you can enter the copy command and have the CLI prompt you for any missing information.
You can use the copy command to backup the startup configuration and to save the running configuration. If the running configuration is not saved to the startup configuration before a system reload, the latest changes are lost.
The entire copying process may take several minutes, depending on the network conditions and the size of the file, and differs from protocol to protocol and from network to network.
The colon character (:) is required after the file system URL prefix keywords.
In the URL syntax for ftp:, sftp:, and tftp:, the server is either an IPv4 address or a hostname.
Copying a Configuration File from a Server to the Running ConfigurationUse the copy {ftp: | sftp: | tftp:} source-url running-config command to download a configuration file from a network server to the running configuration of the device. The configuration is added to the running configuration as if the commands were typed in the CLI. The resulting configuration file is a combination of the previous running configuration and the downloaded configuration file. The downloaded configuration file has precedence over the previous running configuration.
Copying the Running or Startup Configuration to a ServerUse the copy running-config {ftp: | sftp: | tftp:} destination-url command to copy the current configuration file to a network server. Use the copy startup-config {ftp: | sftp: | tftp:} destination-url command to copy the startup configuration file to a network server. You can use the copied configuration file as a backup.
Examples
This example shows how to copy the running configuration to the startup configuration:
mxe# copy running-config startup-configThese examples show how to copy the running configuration to a file by using TFTP:
This example shows how to copy the running configurationmxe56# copy running-config tftp://10.10.1.1/runcfg.txtTrying to connect to tftp server......!!!!!!!!!!!TFTP put operation was successful5145 bytes copiedmxe56# copy running-config tftp:Enter hostname for the tftp server[]? 10.10.1.1Enter the destination filename[]? [running-config] runcfg2.txtTrying to connect to tftp server......!!!!!!!!!!!TFTP put operation was successful5145 bytes copiedThese examples show how to copy a file from a remote server to the Cisco MXE-OS running configuration:
mxe56# copy tftp: running-configEnter source filename[]? runcfg2.txtAddress or name of remote host[]? 10.10.1.1Trying to connect to tftp server......!!!!!!!!!!!TFTP get operation was successful5145 bytes copiedmxe56# copy tftp://10.10.1.1/runcfg.txt running-configTrying to connect to tftp server......!!!!!!!!!!!TFTP get operation was successful5145 bytes copiedRelated Commands
copy running-config startup-config
To copy the running configuration to the startup configuration, use the copy running-config startup-config command.
copy running-config startup-config
Syntax Description
This command has no arguments or keywords.
Defaults
None
Command Modes
EXEC
Supported User Rolesnetwork-admin
Command History
1.0
This command was introduced.
1.2
This command was replaced by the copy command.
Usage Guidelines
Use this command to save your configuration changes in the running configuration to the startup configuration in internal memory.
Examples
This example shows how to copy the running configuration to the startup configuration:
mxe# copy running-config startup-configRelated Commands
copy startup-config running-config
To copy the startup configuration to the running configuration, use the copy startup-config running-config command.
copy startup-config running-config
Syntax Description
This command has no arguments or keywords.
Defaults
None
Command Modes
EXEC
Supported User Rolesnetwork-admin
Command History
1.0
This command was introduced.
1.2
This command was replaced by the copy command.
Usage Guidelines
Use this command to save your configuration changes in the startup configuration to the running configuration in internal memory.
Examples
This example shows how to copy the startup configuration to the running configuration:
mxe# copy startup-config running-configRelated Commands
end
To exit a configuration mode and return to EXEC mode, use the end command.
end
Syntax Description
This command has no arguments or keywords.
Defaults
None
Command Modes
Any command mode except EXEC
Supported User Rolesnetwork-admin
Command History
Usage Guidelines
None
Examples
This example shows how to return to EXEC mode from global configuration mode:
mxe(config)# endmxe#This example shows how to return to EXEC mode from interface configuration mode:
mxe(config-if)# endmxe#Related Commands
exec-timeout
To configure the inactive session timeout on the console port or the virtual terminal, use the exec-timeout command. To revert to the default, use the no form of this command.
exec-timeout minutes
no exec-timeout
Syntax Description
minutes
Number of minutes. The range is from 0 to 525600. A setting of 0 minutes disables the timeout.
Defaults
0 minutes
Command Modes
Console port configuration
Line configurationSupported User Rolesnetwork-admin
Command History
Usage Guidelines
You can configure the console ports only from a session on the console port.
Examples
This example shows how to configure the inactive session timeout for the console port:
mxe# configure terminalmxe(config)# line consolemxe(config-console)# exec-timeout 30This example shows how to configure the inactive session timeout for the virtual terminal:
mxe# configure terminalmxe(config)# line vtymxe(config-vty)# exec-timeout 30This example shows how to revert to the default inactive session timeout for the console port:
mxe# configure terminalmxe(config)# line consolemxe(config-console)# no exec-timeoutThis example shows how to revert to the default inactive session timeout for the virtual terminal:
mxe# configure terminalmxe(config)# line vtymxe(config-line)# no exec-timeoutRelated Commands
Displays the running configuration.
Specifies the console port and enters console port configuration mode.
Specifies the virtual terminal and enters line configuration mode.
exit
To exit a configuration mode and return to the previous configuration mode, use the exit command.
exit
Syntax Description
This command has no arguments or keywords.
Defaults
None
Command Modes
Any command mode
Supported User Rolesnetwork-admin
network-operatorCommand History
Usage Guidelines
None
Examples
This example shows how to return to EXEC mode from global configuration mode:
mxe(config)# exitmxe#This example shows how to return to global configuration mode from interface configuration mode:
mxe(config-if)# exitmxe(config)#Related Commands
hostname
To configure the host name for the device, use the hostname command. To revert to the default, use the no form of this command.
hostname name
no hostname
Syntax Description
name
Name for the device. The name is alphanumeric, case sensitive, can contain special characters, and can have a maximum of 32 characters. Do not use > < " or ? in the name.
Defaults
No host name
Command Modes
Global configuration
Supported User Rolesnetwork-admin
Command History
Usage Guidelines
The Cisco MXE-OS software uses the hostname in command-line interface (CLI) prompts and in default configuration filenames.
Examples
This example shows how to configure the device hostname Engineering2:
mxe# configure terminalmxe(config)# hostname Engineering2Engineering2(config)#This example shows how to revert to the default device hostname:
mxe# configure terminalEngineering2(config)# no hostnamemxe(config)#Related Commands
hw-module
To configure a chassis slot for a module type, use the hw-module command. To remove the configuration, use the no form of this command.
hw-module {slot slot-number type model-name}
no hw-module {slot slot-number type model-name}
Syntax Description
slot slot-number
Specifies a chassis slot number. The range is 3 to 8.
type model-name
The type model name is MXE-MPM-K9.
Defaults
None
Command Modes
Global configuration
Supported User Rolesnetwork-admin
Command History
Usage Guidelines
The Cisco MXE MPM occupies two slots in the chassis: 3-4, 5-6, and 7-8. For this module, the valid slot numbers are 3, 5, and 7. The module is not supported if installed in slot 2-3, 4-5, or 6-7. Always install the module in the lowest available slot.
The no form of this command returns the specified slot (3 to 8) to the nonprovisioned mode.
Examples
This example shows how to configure slot 5 to be an MPM slot:
mxe# configure terminalEnter configuration commands, one per line. End with CNTL/Z.mxe(config)# hw-module slot 5 type MXE-MPM-K9Slot type configured successfully.Related Commands
license clear
To remove a license entry from license storage, use the license clear command.
license clear feature-name
Syntax Description
Defaults
None
Command Modes
Global configuration
Supported User Rolesnetwork-admin
Command History
Usage Guidelines
The license clear command verifies that the license line is valid and explicitly installed. Only licenses that have been added using the license install command are removed. Evaluation licenses are not removed.
If a license line is in use, the license clear command fails.
Examples
This example shows how to display all licenses and how to clear the mxe-interop license:
mxe# configure terminalmxe(config)# license clear ?mxe-interop MXE Interop featuremxe-port MXE Port featuremxe(config)# license clear mxe-interopFeature: mxe-interop1 License Type: PermanentLicense State: Active, Not in UseLicense Addition: ExclusiveLicense Count: Non-CountedComment:Store Index: 1Store Name: Primary License StorageAre you sure you want to clear? (yes/[no]): yesRelated Commands
license comment
To add or delete a comment about a feature license, use the license comment command.
license comment {add feature-name comment | delete}
Syntax Description
Defaults
None
Command Modes
Global configuration
Supported User Rolesnetwork-admin
Command History
Usage Guidelines
This command is useful for tracking a license when multiple licenses are stored on a device and for adding or deleting information about a specific license. You can also use the license comment command to verify that a license associated with the specified feature is present in license storage.
When issued, the license comment command performs these operations:
•
Verifies that the license associated with the specified feature is present in the license storage.
•
•
•
Examples
The following example shows how to add the comment "Permanent License" to a license file called mxe-interop.
mxe# configure terminalmxe# license comment add mxe-interop "Permanent License"Related Commands
license eval activate
To activate a feature evaluation license, use the license eval activate command.
license eval activate {feature-name}
Syntax Description
Defaults
Evaluation licenses are disabled.
Command Modes
Global configuration
Supported User Rolesnetwork-admin
Command History
1.1
This command was introduced.
1.1.1
The application totalResources command requirement was removed.
Usage Guidelines
The supported license features are mxe-port and mxe-interop. Before enabling a licensed feature, you must accept the EULA.
For Cisco MXE-OS Release 1.1, before you can use any license, you must allocate the number of resources for an application by using the application totalResources command. For more information about allocating resources, see the Configuration Guide for Cisco MXE-OS.
When you install a permanent license, the respective evaluation license is deactivated. If the mxe-port evaluation license is active when you install the permanent license, the port count is transferred to the permanent license. Activation of an evaluation license is not needed if a permanent license is installed.
Examples
This example shows how to activate the mxe-interop evaluation license:
mxe# configure terminalmxe(config)# license eval activate mxe-interopEvaluation licenses are being activated in the device for the following feature(s):Feature Name: mxe-interopPLEASE READ THE FOLLOWING TERMS CAREFULLY. INSTALLING THE LICENSE ORLICENSE KEY PROVIDED FOR ANY CISCO PRODUCT FEATURE OR USING SUCHPRODUCT FEATURE CONSTITUTES YOUR FULL ACCEPTANCE OF THE FOLLOWINGTERMS. YOU MUST NOT PROCEED FURTHER IF YOU ARE NOT WILLING TO BE BOUNDBOUND BY ALL THE TERMS SET FORTH HEREIN.You hereby acknowledge and agree that the product feature licenseis terminable and that the product feature enabled by such licensemay be shut down or terminated by Cisco after expiration of theapplicable term of the license (e.g., 30-day trial period). Ciscoreserves the right to terminate or shut down any such product featureelectronically or by any other means available. While alerts or suchmessages may be provided, it is your sole responsibility to monitoryour terminable usage of any product feature enabled by the licenseand to ensure that your systems and networks are prepared for the shutdown of the product feature. You acknowledge and agree that Cisco willnot have any liability whatsoever for any damages, including, but notlimited to, direct, indirect, special, or consequential damages relatedto any product feature being shutdown or terminated. By clicking the"accept" button or typing "yes" you are indicating you have read andagree to be bound by all the terms provided herein.Do you accept this End User License Agreement? (Yes/[N]o): yes*** 2010-05-12 07:49:08 Eqpt Cleared Chassis Eval License mxe-interop: Inactive ***Related Commands
license install
To install a license, use the license install command.
license install scheme://[user@]host-ip-addr/dir1/.../dirN/filename
Syntax Description
scheme
Supported file system types:
•
host-ip-addr
Use the A.B.C.D format.
dir1/.../dirN
Directory names.
filename
Name of the license file.
Defaults
No license is installed.
Command Modes
Global configuration
Supported User Rolesnetwork-admin
Command History
1.0
This command was introduced.
1.1.1
The application totalResources command requirement was removed.
Usage Guidelines
•
•
–
–
–
–
•
For Cisco MXE-OS Release 1.1, before you can use any license, you must allocate the number of resources for an application by using the application totalResources command. For more information about allocating resources and installing licenses on a Cisco MXE-OS device, see the Configuration Guide for Cisco MXE-OS.
Examples
This example shows how to install a file named license-file that resides in the bootflash: directory:
mxe# configure terminalmxe# license install tftp://infrasun/mxe/mxe_feature.licRelated Commands
Clears a license entry from a permanent license file.
Adds or clears a comment about a feature license.
Saves a copy of a permanent license in a specified license file.
license save credential
Saves license identity information associated with a device to a specified URL.
Displays information about a Cisco MXE-OS software license.
license save
To save a copy of a all Cisco MXE-OS licenses and credentials to a another location for back up purposes, use the license save command.
license save [credential] scheme://[user@]host-ip-addr/dir1/.../dirN/filename
Syntax Description
Command Defaults
Licenses are not saved.
Command Modes
Global configuration
Supported User Rolesnetwork-admin
Command History
Usage Guidelines
Issuing this command stores the license line and comment in Extensible Markup Language (XML) format as required by the command. Issuing this command saves copies of all permanent licenses.
Saved licenses can be restored by using the license install command.
Examples
The following example shows how to saves all Cisco MXE-OS licenses to a file on a remote server called backup.lic:
mxe# configure terminalmxe(config)# license save tftp:/10.194.58.126/backup.licExporting to host/file (10.194.58.126/backup.lic) via TFTPExport success!The following example shows how to save Cisco MXE-OS credential to a file on a remote server named cred-bkup:
mxe# configure terminalmxe(config)# license save feat1.lic credential tftp://10.194.58.126/cred-bkupExporting to host/file (10.194.58.126/cred-bkup) via TFTPExport success!Related CommandsExport success!
Installs a license stored in a license file on a device.
license save credential
Saves the identity information associated with a license to internal storage on a device.
Display license information.
line console
To specify the console port and enter console port configuration mode, use the line console command.
line console
Syntax Description
This command has no arguments or keywords.
Defaults
None
Command Modes
Global configuration
Supported User Rolesnetwork-admin
Command History
Usage Guidelines
You can configure the console line only from a console port session.
Examples
This example shows how to enter console port configuration mode:
mxe# configure terminalmxe(config)# line consolemxe(config-console)#Related Commands
line vty
To specify the virtual terminal and enter line configuration mode, use the line vty command.
line vty
Syntax Description
This command has no arguments or keywords.
Defaults
None
Command Modes
Global configuration
Supported User Rolesnetwork-admin
Command History
Usage Guidelines
You can configure the console line only from a console port session.
Examples
This example shows how to enter console port configuration mode:
mxe# configure terminalmxe(config)# line vtymxe(config-vty)#Related Commands
parity
To configure the parity for the console port, use the parity command. To revert to the default, use the no form of this command.
parity {even | none | odd}
no parity {even | none | odd}
Syntax Description
Defaults
The none keyword is the default.
Command Modes
Console port configuration
Supported User Rolesnetwork-admin
Command History
Usage Guidelines
You can configure the console port only from a session on the console port.
Examples
This example shows how to configure the parity for the console port:
mxe# configure terminalmxe(config)# line consolemxe(config-console)# parity evenThis example shows how to revert to the default parity for the console port:
mxe# configure terminalmxe(config)# line consolemxe(config-console)# no parity evenRelated Commands
ping
To verify the basic network connectivity of the Cisco MXE-OS, use the ping command.
ping [ip-address | host-name] [count repeat-count] [size datagram-size] [timeout timeout]
Syntax Description
Defaults
If no key words or arguments are used, prompts will be issued for address, repeat-count, datagram-size, and time-out settings.
Command Modes
EXEC
Supported User Rolesnetwork-admin
network-operatorCommand History
Usage Guidelines
The ping program sends an echo request packet to an IP address and waits for a reply. The ping output helps with the following:
•
•
To end a ping session press Ctrl-c.
Examples
This example shows how to ping an IP address with various repeat-count, datagram-size, and time-out settings:
mxe# ping 10.194.60.56 count 8 size 676 timeout 10Sending 8 ICMP Echo Packets of size 676-bytes to 10.194.60.56 with timeout 10 Sec....PING 10.194.60.56 (10.194.60.56) 676(704) bytes of data.684 bytes from 10.194.60.56: icmp_seq=1 ttl=64 time=0.052 ms684 bytes from 10.194.60.56: icmp_seq=2 ttl=64 time=0.044 msThe following command shows the prompts that appear when you enter the ping command without an IP address:
mxe# pingTarget IP address: 10.194.58.243Repeat count(1-64) [5]: 6Datagram size(10-1472) [56]: 100Timeout in seconds(1-10) [1]: 2Sending 5 ICMP Echo Packets of size 100-bytes to 10.194.58.243 with timeout 2....PING 10.194.58.243 (10.194.58.243) 100(128) bytes of data.108 bytes from 10.194.58.243: icmp_seq=1 ttl=63 time=0.204 ms108 bytes from 10.194.58.243: icmp_seq=2 ttl=63 time=0.164 ms108 bytes from 10.194.58.243: icmp_seq=3 ttl=63 time=0.239 msRelated Commands
reload
To reload the entire Cisco MXE-OS device, use the reload command.
reload
Syntax Description
This command has no arguments or keywords.
Defaults
Reloads the entire device.
Command Modes
EXEC
Supported User Rolesnetwork-admin
Command History
Usage Guidelines
The reload command uses the system image to reboot the device.
Caution
Note
For information on upgrading images on your Cisco MXE-OS device, see the Software Upgrade Guide for the Cisco MXE-OS.
Examples
This example shows how to reload the Cisco MXE-OS device:
mxe# copy running-config startup-configmxe# reloadThis command will reboot the system. (y/n)? [n] yRelated Commands
Copies the current running configuration to the startup configuration.
Displays information about the software version.
session-limit
To configure the maximum number of the concurrent virtual terminal sessions on a device, use the session-limit command. To revert to the default, use the no form of this command.
session-limit sessions
no session-limit
Syntax Description
Defaults
32 sessions
Command Modes
Line configuration
Supported User Rolesnetwork-admin
Command History
Usage Guidelines
None
Examples
This example shows how to configure the maximum number of concurrent virtual terminal sessions to 30:
mxe# configure terminalmxe(config)# line vtymxe(config-line)# session-limit 30This example shows how to revert to the default maximum number of concurrent virtual terminal sessions to 32:
mxe# configure terminalmxe(config)# line vtymxe(config-line)# no session-limitRelated Commands
setup
To enter the basic device setup dialog, use the setup command.
setup
Syntax Description
This command has no arguments or keywords.
Defaults
Factory settings
Command Modes
EXEC
Supported User Rolesnetwork-admin
Command History
Usage Guidelines
When you use the setup command to change your device configuration, the setup utility uses the factory-default values, not the values that you have configured, when you accept the defaults values in the dialog.
You can exit the setup utility dialog at any point by pressing Ctrl-C.
Examples
This example shows how to enter the basic device setup script:
mxe# setup---- Basic System Configuration ----This setup utility will guide you through the basic configuration ofthe system. Setup configures only enough connectivity for managementof the system.*Note: setup is mainly used for configuring the system initially,when no configuration is present. So setup always assumes systemdefaults and not the current system configuration values.Press Enter at anytime to skip a dialog. Use ctrl-c at anytimeto skip the remaining dialogs.Would you like to enter the basic configuration dialog (yes/no):Related Commands
show banner motd
To display the message-of-the-day (MOTD) banner, use the show banner motd command.
show banner motd
Syntax Description
This command has no arguments or keywords.
Defaults
None
Command Modes
EXEC
Supported User Rolesnetwork-admin
network-operatorCommand History
Usage Guidelines
None
Examples
This example shows how to display the MOTD banner:
mxe# show banner motdUnauthorize access prohibited!Related Commands
show cli history
To display the command history, use the show cli history command.
show cli {history [lines] | history-size}
Syntax Description
history lines
Number of command history lines to display. The range is 2 to 512.
history-size
Show the history-size setting.
Defaults
Displays the entire formatted history.
Command Modes
EXEC
Supported User Rolesnetwork-admin
network-operatorCommand History
Usage Guidelines
When in EXEC mode, the show cli history command displays only commands that have been executed in EXEC mode.
For global configuration mode CLI history, enter global configuration mode, and enter the do show cli history command.
The history-size setting is not retained after a system reload.
Examples
This example shows how to display all of the command history:
mxe# show cli history0 22:59:13 show boot1 23:00:05 show boot sup-12 23:01:23 show boot variables3 23:20:28 config t4 23:22:16 end5 23:22:25 show cli alias6 00:00:10 show cli alias name ethint...This example shows how to display the last 10 lines of the command history:
mxe# show cli history 1042 00:42:54 ip route 0.0.0.0/0 172.28.230.143 00:42:54 interface MGT144 00:42:54 ip address 172.28.231.193/2345 00:42:54 no shutdown46 00:42:54 aaa group server radius aaa-private-sg47 00:42:54 use-vrf management48 00:42:54 telnet server enable49 00:42:54 logging server 172.28.254.25450 00:42:54 power redundancy-mode combined51 00:43:28 show cli history 10This example shows how to configure the history-size setting:
mxe# cli history-size 50This example shows how to display the history-size setting:
mxe# show cli history-sizeHistory size is 50Related Commands
show clock
To display the clock setting, use the show clock command.
show clock
Syntax Description
This command has no arguments or keywords.
Defaults
None
Command Modes
EXEC
Supported User Rolesnetwork-admin
network-operatorCommand History
Usage Guidelines
None
Examples
This example shows how to display the clock setting:
mxe# show clockFri Jun 13 02:19:20 PDT 2008Related Commands
show copyright
To display the Cisco MXE-OS software copyright information, use the show copyright command.
show copyright
Syntax Description
This command has no arguments or keywords.
Defaults
None
Command Modes
EXEC
Supported User Rolesnetwork-admin
network-operatorCommand History
Usage Guidelines
None
Examples
This example shows how to display the Cisco MXE-OS copyright information:
mxe# show copyrightTAC support: http://www.cisco.com/tacCopyright (c) 2007-2010 by Cisco Systems, Inc.All rights reserved.The copyrights to certain works contained in this software are ownedby other third parties and used and distributed under license. Certaincomponents of this software are licensed under the GNU General PublicLicense (GPL) version 2.0 or the GNU Lesser General Public License(LGPL) Version 2.1. A copy of each such license is available athttp://www.opensource.org/licenses/gpl-2.0.php andhttp://www.opensource.org/licenses/lgpl-2.1.phpshow facility-alarm
To display the Cisco MXE 5600 alarm history and status, use the show facility-alarm command.
show facility-alarm {history | status}
Syntax Description
history
Displays current status of facility alarms.
status
Displays status of currently present alarms.
Defaults
None
Command Modes
EXEC
Supported User Rolesnetwork-admin
network-operatorCommand History
Usage Guidelines
None
Examples
These examples show how to display facility alarm history and status reports:
mxe# show facility-alarm historyID Alarm Time Type Severity Description-- ------------------- ---- -------- ------------------------------------------1 2009-05-29 06:53:58 Env Warning MPM 3/1 AMC Side 2 Temp: Threshold crossed2 2009-05-29 06:53:58 Env Warning MPM 3/2 AMC Side 2 Temp: Threshold crossed3 2009-05-29 06:54:38 Env Cleared MPM 3/2 AMC Side 2 Temp: Threshold crossed4 2009-05-29 06:54:38 Env Cleared MPM 3/1 AMC Side 2 Temp: Threshold crossedmxe# show facility-alarm status9 alarms currently activeAlarm time Type Severity Description------------------- ---- -------- ----------------------------------------2009-05-28 21:59:05 Env Warning NPM 1 Payload 1.0V: Threshold crossed2009-05-28 21:59:05 Env Warning MPM 3 Payload 1.2V: Threshold crossed2009-05-28 21:59:05 Env Warning MPM 3 AMC#1 +12V: Threshold crossed2009-05-28 21:59:05 Env Warning MPM 3 1GbE Switch 1.1V: Threshold crossed2009-05-28 21:59:05 Env Warning MPM 3 AMC#2 +12V: Threshold crossed2009-05-28 21:59:05 Env Warning MPM 3 10GbE Switch1.1V: Threshold crossed2009-05-28 21:59:05 Env Warning MPM 3 AMC#3 +12V: Threshold crossed2009-05-28 21:59:05 Env Warning MPM 3 AMC#4 3.3V_MP: Threshold crossed2009-05-28 21:59:05 Env Warning Shelf Manager 1 3V3_local: Threshold crossedRelated Commands
show hardware internal inventory
To display information about the Cisco MXE 5600 hardware's internal inventory, use the show hardware internal inventory command. This command was deprecated in Cisco MXE-OS Release 1.1.
show hardware internal inventory
Syntax Description
This command has no arguments or keywords.
Defaults
None
Command Modes
EXEC
Supported User Rolesnetwork-admin
Command History
Usage Guidelines
None
Examples
This example shows how to display information about the Cisco MXE 5600 physical device hardware:
mxe# show hardware internal inventoryMXE-NPM 1-- Chassis Info ---- Board Info --1. (0x1) MFG datetime: 2001.11.24 20:16:002. (0x2) Manufacturer: Cisco Systems, Inc.3. (0x3) Product name: Product15. (0x5) Serial number: FOC1405810J6. (0x6) Part number: 73-11772-047. (0x7) File ID: Product_P3-v3.0.12-20091216/fru-info.inf9. (0x9) Custom: DEVIATION=0000000000-- Product Info --2. (0x2) Manufacturer: Cisco Systems, Inc.3. (0x3) Product name: MXE-NPM-K94. (0x4) Product version: V015. (0x5) Serial number: FOC14098FG76. (0x6) Part number: 68-3355-047. (0x7) File ID: Product1_P3-v3.0.12-20091216/fru-info.inf8. (0x8) Asset tag: itms000000009. (0x9) Custom: CLEI=FFSSfffRCCMXE-MPM 3-- Chassis Info ---- Board Info --1. (0x1) MFG datetime: 2001.11.24 20:16:002. (0x2) Manufacturer: Cisco Systems, Inc.3. (0x3) Product name: Pruduct25. (0x5) Serial number: FOC1405811U6. (0x6) Part number: 73-11773-047. (0x7) File ID: Pruduct2_P3-v3.0.12-20091216/fru-info.inf9. (0x9) Custom: DEVIATION=0000000000-- Product Info --2. (0x2) Manufacturer: Cisco Systems, Inc.3. (0x3) Product name: MXE-MPM-K94. (0x4) Product version: V015. (0x5) Serial number: FOC141081LR6. (0x6) Part number: 68-3386-047. (0x7) File ID: Pruduct2_P3-v3.0.12-20091216/fru-info.inf8. (0x8) Asset tag: itms000000009. (0x9) Custom: CLEI=FFSSfffRCCMXE-5600-- Chassis Info --0. (0x0) Chassis type: Rack Mount Chassis5. (0x5) Serial number: PGR134403246. (0x6) Part number: 11596-0419. (0x9) Custom: TACH_MASK=00-- Board Info --1. (0x1) MFG datetime: 2010.01.19 14:11:002. (0x2) Manufacturer: Cisco Systems, Inc.3. (0x3) Product name: Windsor Chassis5. (0x5) Serial number: PGR134300366. (0x6) Part number: 23005-3707. (0x7) File ID: 11596041HDBIN.bin9. (0x9) Custom: DEVIATION=-- Product Info --2. (0x2) Manufacturer: Cisco Systems, Inc.3. (0x3) Product name: MXE-5600-K94. (0x4) Product version: V015. (0x5) Serial number: PGR134403246. (0x6) Part number: 74-6366-017. (0x7) File ID: 11596041HDBIN.bin8. (0x8) Asset tag: ITM023049819. (0x9) Custom: CLEI=MXE-5600-SHMGR 1-- Chassis Info ---- Board Info --1. (0x1) MFG datetime: 2010.01.19 14:11:002. (0x2) Manufacturer: Cisco Systems, Inc.3. (0x3) Product name: Windsor Shelf Manager(SMC)5. (0x5) Serial number: PGR134701066. (0x6) Part number: 23098-6517. (0x7) File ID: 21990002HBBIN_P5.bin9. (0x9) Custom: DEVIATION=-- Product Info --2. (0x2) Manufacturer: Cisco Systems, Inc.3. (0x3) Product name: MXE-5600-SHMGR-K94. (0x4) Product version: V015. (0x5) Serial number: PGR134701066. (0x6) Part number: 74-6427-017. (0x7) File ID: 21990002HBBIN_P5.bin8. (0x8) Asset tag: ITM023049829. (0x9) Custom: CLEI=MXE-5600-PWR 1-- Chassis Info ---- Board Info --1. (0x1) MFG datetime: 2010.01.27 07:33:002. (0x2) Manufacturer: Cisco3. (0x3) Product name: Windsor AC/DC Power Supply5. (0x5) Serial number: PGR134402136. (0x6) Part number: 23098-6537. (0x7) File ID: 21990004ABBIN.bin-- Product Info --2. (0x2) Manufacturer: Cisco3. (0x3) Product name: MXE-5600-PWR4. (0x4) Product version: V015. (0x5) Serial number: PGR134402136. (0x6) Part number: 74-6429-017. (0x7) File ID: 21990004ABBIN.bin8. (0x8) Asset tag: ITM023049859. (0x9) Custom: CLEI=MXE-5600-PWR 2-- Chassis Info ---- Board Info --1. (0x1) MFG datetime: 2010.01.26 08:42:002. (0x2) Manufacturer: Cisco3. (0x3) Product name: Windsor AC/DC Power Supply5. (0x5) Serial number: PGR134400596. (0x6) Part number: 23098-6537. (0x7) File ID: 21990004ABBIN.bin-- Product Info --2. (0x2) Manufacturer: Cisco3. (0x3) Product name: MXE-5600-PWR4. (0x4) Product version: V015. (0x5) Serial number: PGR134400596. (0x6) Part number: 74-6429-017. (0x7) File ID: 21990004ABBIN.bin8. (0x8) Asset tag: ITM023049869. (0x9) Custom: CLEI=MXE-5600-PWR 3-- Chassis Info ---- Board Info --1. (0x1) MFG datetime: 2010.01.26 13:23:002. (0x2) Manufacturer: Cisco3. (0x3) Product name: Windsor AC/DC Power Supply5. (0x5) Serial number: PGR134600946. (0x6) Part number: 23098-6537. (0x7) File ID: 21990004ABBIN.bin-- Product Info --2. (0x2) Manufacturer: Cisco3. (0x3) Product name: MXE-5600-PWR4. (0x4) Product version: V015. (0x5) Serial number: PGR134600946. (0x6) Part number: 74-6429-017. (0x7) File ID: 21990004ABBIN.bin8. (0x8) Asset tag: ITM023049879. (0x9) Custom: CLEI=MXE-5600-FAN 1-- Chassis Info ---- Board Info --1. (0x1) MFG datetime: 2010.01.19 14:11:002. (0x2) Manufacturer: Cisco Systems, Inc.3. (0x3) Product name: Windsor Fan Tray5. (0x5) Serial number: PGR134700496. (0x6) Part number: 23098-6507. (0x7) File ID: 21990001AABIN.bin9. (0x9) Custom: DEVIATION=-- Product Info --2. (0x2) Manufacturer: Cisco Systems, Inc.3. (0x3) Product name: MXE-5600-FAN4. (0x4) Product version: V015. (0x5) Serial number: PGR134700496. (0x6) Part number: 74-6428-017. (0x7) File ID: 21990001AABIN.bin8. (0x8) Asset tag: ITM023049839. (0x9) Custom: CLEI=MXE-5600-FAN 2-- Chassis Info ---- Board Info --1. (0x1) MFG datetime: 2010.01.19 14:11:002. (0x2) Manufacturer: Cisco Systems, Inc.3. (0x3) Product name: Windsor Fan Tray5. (0x5) Serial number: PGR134700506. (0x6) Part number: 23098-6507. (0x7) File ID: 21990001AABIN.bin9. (0x9) Custom: DEVIATION=-- Product Info --2. (0x2) Manufacturer: Cisco Systems, Inc.3. (0x3) Product name: MXE-5600-FAN4. (0x4) Product version: V015. (0x5) Serial number: PGR134700506. (0x6) Part number: 74-6428-017. (0x7) File ID: 21990001AABIN.bin8. (0x8) Asset tag: ITM023049849. (0x9) Custom: CLEI=show hostname
To display the hostname for the device, use the show hostname command.
show hostname
Syntax Description
This command has no arguments or keywords.
Defaults
None
Command Modes
EXEC
Supported User Rolesnetwork-admin
network-operatorCommand History
Usage Guidelines
None
Examples
This example shows how to display the hostname for the device:
mxe# show hostnamemxeRelated Commands
show license
To display Cisco MXE-OS license information, use the show license command.
show license [all | brief | detail | feature | file | statistics | status | udi | usage]
Syntax Description
Defaults
None
Command Modes
EXEC
Supported User Rolesnetwork-admin
network-operatorCommand History
Usage Guidelines
Use this command to display license information and to help with troubleshooting issues related to Cisco MXE-OS software licenses. This command displays all the licenses in the system.
This command also displays the features that are available but not licensed to execute. Output is grouped according to how the features are stored in license storage.
If the show license all command displays the license as "Active, Not in Use, EULA not accepted," you can use the license install global configuration command to enable the license and accept the EULA.
Examples
This example shows how to display all licenses installed on a device:
mxe# show licenseLicense Store: Primary License StorageStoreIndex: 0 Feature: mxe-port Version: 1.0License Type: PermanentLicense State: Active, In UseLicense Count: 90 /2License Priority: MediumLicense Store: Evaluation License StorageStoreIndex: 0 Feature: mxe-interop Version: 1.0License Type: EvaluationLicense State: Active, In UseEvaluation total period: 8 weeks 4 daysEvaluation period left: 8 weeks 3 daysExpiry date: Mon Sep 5 18:03:09 2011License Count: Non-CountedLicense Priority: LowLicense Store: Evaluation License StorageStoreIndex: 1 Feature: mxe-port Version: 1.0License Type: EvaluationLicense State: InactiveEvaluation total period: 8 weeks 4 daysEvaluation period left: 8 weeks 4 daysLicense Count: 10 / 0License Priority: None
Note
This example shows how to display a brief list of license files installed on a device:
mxe# show license briefIndex 0 Feature: mxe-interopPeriod left: Life timeLicense Type: PermanentLicense State: Active, Not in UseLicense Count: Non-CountedLicense Priority: MediumIndex 1 Feature: mxe-portPeriod left: Life timeLicense Type: PermanentLicense State: Active, Not in UseLicense Count: 40 / 0This example shows how to display the detailed contents of all license files installed on a device:
mxe# show license detailIndex: 1 Feature: mxe-interop Version: 1.0License Type: PermanentLicense State: Active, Not in UseLicense Count: Non-CountedLicense Priority: MediumStore Index: 1Store Name: Primary License StorageIndex: 2 Feature: mxe-port Version: 1.0License Type: PermanentLicense State: Active, Not in UseLicense Count: 40 / 0License Priority: MediumStore Index: 0Store Name: Primary License StorageThis example shows how to display the licensed features installed on a device:
mxe# show license featureFeature name Enforcement Evaluation Clear Allowed Enabledmxe-interop yes yes yes nomxe-port yes yes yes noThis example shows how to display the contents of the license file installed on a device:
mxe# show license fileLicense Store: Evaluation License StorageStore Index: 0License: 11 mxe-interop 1.0 LONG TRIAL DISABLED 1440 DISABLED STANDALONE ADD INFINITE_KEYS INFINITE_KEYS NEVER NEVER NiL SLM_CODE DEMO NiLNiL Ni NiL NiL 5_MINS NiL R3L67H8hb3Bmn5j,LNcZVzU1YdVDjh6Dr6:Tvd0Ki0L8W7JKGXikjvjHI3vOBUB4Lm$<WLC>AQEBIQAB//9eiycCFokWIjbL4wFSNK/iuNG7qC1jg0/IIzf5nM3MzG2pZY/Hqta7jNuGYXhMEjWRqwInXo3s+nsLU7rOtdOxoIxYZAo3LYmUJ+MFzsqlhKoJVlPyEvQ8H21MNUjVbhoN0gyIWsyiJaM8AQIkVBQFzhr10GYolVzdzfJfEPQIx6tZ++/Vtc/q3SF/5Ko8XCY=</WLC>Comment:Hash: aCo9Ksj+xrw4RQpeyCsNRc0fqJ8=Store Index: 1License: 11 mxe-port 1.0 LONG TRIAL DISABLED 1440 DISABLED STANDALONE ADD10_KEYS INFINITE_KEYS NEVER NEVER NiL SLM_CODE DEMO NiL NiL Ni NiL NiL 5_MINS NiL 7DGW,Ek5tLMQ440rLN5,fU4qK9YJkMKBrny64Sr8D23yBZtcl8p7P,S7xb81n74IVo$<WLC>AQEBIQAB//+2aa0q6+4BNGDOe9fbE01afjfWjX1AeAolUNzZ+FLE87rfGLo3ENJpI9SzgwB31RiRqwInXo3s+nsLU7rOtdOxoIxYZAo3LYmUJ+MFzsqlhKoJVlPyEvQ8H21MNUjVbhoN0gyIWsyiJaM8AQIkVBQFzhr10GYolVzdzfJfEPQIx6tZ++/Vtc/q3SF/5Ko8XCY=</WLC>Comment:Hash: WpLAfs9agyDPmMpkCW/qP436x4w=This example shows how to display license-related statistics of the licence installed on a device:
mxe# show license statisticsAdministrative statisticsInstall success count: 0Install failure count: 3Install duplicate count: 2Comment add count: 0Comment delete count: 0Clear count: 0Save count: 2Save cred count: 2Client statusRequest success count 4Request failure count 0Release count 4Global Notify count 0This example shows how to display information about the device UDI:
mxe# show license udiDevice# PID SN UDI-----------------------------------------------------------------*0 MXE5600 FOC10172T6Z MXE5600:FOC10172T6ZThis example shows how to display information about the current license usage:
mxe# show license usageStoreIndex: 0 Feature: mxe-port Version: 1.0License Type: PermanentLicense State: Active, In UseLicense Count: 40 /2License Priority: MediumRelated Commands
show line
To display console port configuration information, use the show line command.
show line
Syntax Description
This command has no arguments or keywords.
Defaults
None
Command Modes
EXEC
Supported User Rolesnetwork-admin
network-operatorCommand History
Usage Guidelines
None
Examples
This example shows how to display information about the console port configuration:
mxe# show lineLine Console :Speed : 9600 baudsParity : NoneStopbit : 1 bit(s)Related Commands
show module
To display all module information for the chassis or for a single module, use the show module command.
show module [all] [[model] mxe-5600-FAN | mxe-5600-PWR | mxe-5600-SHMGR-K9 | mxe-MPM-K9 | mxe-NPM-K9]] {slot slot-number} [brief]
Syntax Description
Defaults
None.
Command Modes
EXEC
Supported User Rolesnetwork-admin
network-operatorCommand History
Usage Guidelines
This example shows how to display information for all modules in the chassis:
mxe# show module allSlot Module Type Model Status Alarm-----------------------------------------------------------------Chassis MXE-5600-K9 ClearedL Shelf Manager MXE-5600-SHMGR-K9 Standby ClearedR Shelf Manager MXE-5600-SHMGR-K9 Ok ClearedL Fan MXE-5600-FAN Ok ClearedR Fan MXE-5600-FAN Ok ClearedA1 Power MXE-5600-PWR Ok ClearedA2 Power MXE-5600-PWR Ok ClearedA3 Power MXE-5600-PWR Ok ClearedB1 Power MXE-5600-PWR Ok ClearedB2 Power MXE-5600-PWR Ok ClearedB3 Power MXE-5600-PWR Ok Cleared1 Network(Supervisor) MXE-NPM-K9 Ok Cleared2 ---- ---- ---- ----3 Media Processing MXE-MPM-K9 Ok Cleared4 ---- ---- ---- ----5 ---- ---- ---- ----6 ---- ---- ---- ----7 ---- ---- ---- ----8 ---- ---- ---- ----This example shows how to display information about the left Cisco MXE 5600 fan:
mxe# show module mxe-5600-FAN slot LModule Slot: LModule Type: FanModel: MXE-5600-FANAdmin State: UnlockedOperational State: EnabledModule Role: ActiveModule Status: OkModule Alarm: ClearedThis example shows how to display summary table information about the left Cisco MXE 5600 fan:
mxe# show module mxe-5600-FAN slot L briefL Fan MXE-5600-FAN Ok ClearedThis example shows how to display information about the power supply in slot A1:
mxe# show module mxe-5600-PWR slot A1Module Slot: A1Module Type: PowerModel: MXE-5600-PWRAdmin State: UnlockedOperational State: EnabledModule Role: ActiveModule Status: OkModule Alarm: ClearedThis example shows how to display summary table information about the power supply in slot A1:
mxe# show module mxe-5600-pwr slot A1 briefAl brief1 Power MXE-5600-PWR Ok ClearedThis example shows how to display information about the left power supply:
mxe# show module mxe-5600-shmgr slot LModule Slot: LModule Type: Shelf ManagerModel: MXE-5600-SHMGRAdmin State: UnlockedOperational State: EnabledModule Role: ActiveModule Status: OkModule Alarm: ClearedThis example shows how to display summary table information about the left shelf manager:
mxe# show module mxe-5600-shmgr slot L briefL Shelf Manager MXE-5600-SHMGR Ok ClearedThis example shows how to display information about a Cisco MXE MPM in slot 1:
mxe# show module mxe-mpm slot 1Module Slot: 1Module Type: Media ProcessingModel: MXE-MPMAdmin State: UnlockedOperational State: EnabledModule Role: ActiveModule Status: OkModule Alarm: ClearedThis example shows how to display summary table information about a Cisco MXE MPM in slot 1:
mxe# show module mxe-mpm slot 1 brief1 Media Processing MXE-MPM Ok ClearedThis example shows how to display information about a Cisco MXE NPM in slot 1:
mxe# show module mxe-npm slot 1Module Slot: 1Module Type: Network(Supervisor)Model: MXE-NPMAdmin State: UnlockedOperational State: EnabledModule Role: ActiveModule Status: OkModule Alarm: ClearedThis example shows how to display summary table information about a Cisco MXE NPM in slot 1:
mxe# show module mxe-npm slot 1 brief1 Network(Supervisor) MXE-NPM Ok ClearedRelated Commands
show processes
To display the process information for a Cisco MXE 5600, use the show processes command.
show processes [application | cpu | memory]
Syntax Description
application
(Optional) Displays process information for running applications.
cpu
(Optional) Displays CPU usage information for processes.
memory
(Optional) Displays memory allocated to processes.
Defaults
Displays information for all processes in the local device.
Command Modes
EXEC
Supported User Rolesnetwork-admin
network-operatorCommand History
1.0
This command was introduced.
1.1(0)
The cpu and memory keywords were added.
Usage Guidelines
None
Examples
This example shows how to display information about all processing running on the Cisco MXE-OS:
mxe# show processesSlot 1 processes:PROCESS STATE PID COMMANDinit sleeping 1 init [3]udevd sleeping 861 udevdportmap sleeping 3401 /sbin/portmapsyslog-ng sleeping 3439 /sbin/syslog-ngdhcpd sleeping 3448 /usr/sbin/dhcpdxinetd sleeping 3458 /usr/sbin/xinetdcron sleeping 3465 /usr/sbin/cronsrp sleeping 3856 /opt/GoAhead/srk/srpsrkWdog sleeping 3859 /opt/GoAhead/srk/srkWdog...Slot 1/1 processes:PROCESS STATE PID COMMANDinit sleeping 1 init [3]udevd sleeping 804 udevdportmap sleeping 3361 /sbin/portmapsyslog-ng sleeping 3398 supervising syslog-ngsyslog-ng sleeping 3399 /sbin/syslog-nginetd sleeping 3418 /usr/sbin/inetdsshd sleeping 3425 /usr/sbin/sshdntpd sleeping 3429 /usr/sbin/ntpdcron sleeping 3434 /usr/sbin/cronsrp sleeping 3607 /opt/GoAhead/srk/srpsrkWdog sleeping 3610 /opt/GoAhead/srk/srkWdog...This example shows how to display Cisco MXE-OS application processes:
mxe# show processes applicationSlot 1 processes:PROCESS STATE PID COMMANDSecMgr sleeping 3958 /root/ML100/bin/SecMgrcfgmgr sleeping 3959 /root/ML100/bin/cfgmgrifmgr sleeping 3960 /root/ML100/bin/ifmgrsnmpagent sleeping 3961 /root/ML100/bin/snmpagentalarmmgr sleeping 3962 /root/ML100/bin/alarmmgrLicMgr sleeping 3963 /root/ML100/bin/LicMgrLogMgr sleeping 3964 /root/ML100/bin/LogMgrsysmgr sleeping 3965 /root/ML100/bin/sysmgrsysagent sleeping 3966 /root/ML100/bin/sysagentvshd sleeping 3967 /root/ML100/bin/vshdlicensed sleeping 4219 /root/ML100/license/licensedopenhpid sleeping 4252 /root/ML100/hpi/openhpidvsh sleeping 5468 /root/ML100/bin/vshvsh sleeping 7488 /root/ML100/bin/vshvsh sleeping 7489 /root/ML100/bin/vshvsh sleeping 19546 /root/ML100/bin/vshSlot 1/1 processes:PROCESS STATE PID COMMANDACPServ sleeping 3710 /root/ML100/bin/ACPServAppPlane sleeping 3711 /root/ML100/bin/AppPlaneMCPRutherford sleeping 3712 /root/ML100/bin/MCPRutherfordSignalingPlane sleeping 3713 /root/ML100/bin/SignalingPlanencpDproc sleeping 3714 /root/ML100/bin/ncpDprocifagent sleeping 3715 /root/ML100/bin/ifagentsysagent sleeping 3716 /root/ML100/bin/sysagentMPCP sleeping 3717 /root/ML100/bin/MPCPMPDF sleeping 3718 /root/ML100/bin/MPDFNetPlane sleeping 3719 /root/ML100/bin/NetPlaneThis example shows how to display information regarding CPU usage:
mxe# show processes cpuSlot 1 processes:CPU utilization for one-minute: 24% five-minute: 18% fifteen-minute: 24%PROCESS USER KERNEL COMMANDInit 0% 0% init [3]Udevd 0% 0% udevdPortmap 0% 0% /sbin/portmapThis example shows how to display information regarding memory allocation for processes:
mxe# show processes memorySlot 1 processes:PROCESS TEXT/CODE DATA/STACK COMMANDInit 98304 253952 init [3]Udevd 110592 266240 udevdPortmap 86016 270336 /sbin/portmapshow running-config
To display the running configuration, use the show running-config command.
show running-config [access-list | cdp | dns | interface | log | route | snmp | ssh | system | user | vs
h]
Defaults
Displays all the default and configured information.
Command Modes
EXEC
Supported User Rolesnetwork-admin
network-operatorCommand History
Usage Guidelines
None
Examples
This example shows how to display the entire running configuration:
mxe# show running-confighostname mxeuser adminrole network-adminpassword 1 xxxxxuser username1role network-operatoruser username-1role network-operatormedia service media-processingcodec-profile 1codec-type h264payload-number 112codec-profile 2codec-type aacpayload-number 96codec-profile 3codec-type h264payload-number 112codec-profile 4codec-type g711-ulawpayload-number 0codec-profile 5codec-type g722payload-number 9codec-profile 6codec-type g711-alawpayload-number 8stream-profile 1app-muxbandwidth 2250000codec-profile 1 preference-value 10mode sendrecvtransport rtp-avpstream-type videostream-profile 2app-muxbandwidth 128000codec-profile 2 preference-value 9codec-profile 4 preference-value 10mode sendrecvpacket-time 20transport rtp-avpstream-profile 3bandwidth 1984000codec-profile 3 preference-value 10mode sendrecvtransport rtp-avpstream-type videostream-profile 4bandwidth 64000codec-profile 5 preference-value 8codec-profile 4 preference-value 9codec-profile 6 preference-value 10mode sendrecvpacket-time 20transport rtp-avpstream-profile 5bandwidth 1984000codec-profile 3mode sendrecvpacket-time 20transport rtp-avpstream-type presentationstream-profile 6transport rtp-avpstream-type bfcpmedia-profile 1stream-profile 2stream-profile 1media-profile 2stream-profile 4stream-profile 3media-profile 3stream-profile 2stream-profile 1media-profile 4stream-profile 4stream-profile 3stream-profile 5stream-profile 6application-profile mxe-interopaction querydefault-telepresence-media-prof 1default-vc-media-profile 2application-profile mxe-interop-vcsaction querydefault-telepresence-media-prof 3default-vc-media-profile 4dial-peer media-service 1application-profile mxe-interopdescription CTS calling and called dial-peer when VC connected to CUCMmedia-profile 1preference-value 10dial-peer media-service 2application-profile mxe-interopdescription VC calling and called dial-peer when VC connected to CUCMmedia-profile 2preference-value 10dial-peer media-service 3application-profile mxe-interop-vcscalling-party-info id Nonecalling-party-info name Nonedescription CTS calling and called dial-peer when VC connected to VCSdestination-pattern Nonemedia-profile 3preference-value 10dial-peer media-service 4application-profile mxe-interop-vcscalling-party-info id Nonecalling-party-info name Nonedescription VC calling and called dial-peer when VC connected to VCSdestination-pattern Nonemedia-profile 4preference-value 10<output truncated>This example shows how to display the access-list configuration:
mxe# show running-config access-listGenerating configuration.......access-list 1 deny 10.1.1.1 255.255.255.255 MGMTaccess-list 255 deny 10.10.10.10 255.255.255.0This example shows how to display the CDP configuration:
mxe# show running-config cdpGenerating configuration........cdp advertise v1cdp timer 5This example shows how to display the DNS configuration:
mxe# show running-config dnsGenerating configuration.......ip domain-lookupip domain-name company.comip name-server 172.16.0.0 172.59.226.120This example shows how to display the interface configuration:
mxe# show running-config interfaceGenerating configuration........interface Ethernet 1/1ip address 10.194.60.57 255.255.255.0ip default-gateway 10.194.60.1no shutdowndescription "Ethernet Interface"interface MGT1ip address 10.194.60.56 255.255.255.0ip default-gateway 10.194.60.1no shutdowndescription "Management Interface"This example shows how to display the log manager configuration:
mxe# show running-config logGenerating configuration........no logging console 2logging logfile messages 7 size 10485760logging module 5logging server 10.194.59.180 7logging timestamp secondsThis example shows how to display the routing configuration:
mxe# show running-config routeGenerating configuration........ip route 0.0.0.0 0.0.0.0 10.100.101.1ip route 0.0.0.0 0.0.0.0 10.194.59.1This example shows how to display the SNMP configuration:
mxe# show running-config snmpGenerating configuration........snmp-server view all 1 includedsnmp-server view none 1 excludedsnmp-server group network-admin read all write all notify allsnmp-server group network-operator read all notify allsnmp-server community public rwsnmp-server community 1 rosnmp-server community 1exi roThis example shows how to display the Telnet and SSH configuration:
mxe# show running-config sshGenerating configuration........ssh key rsa 1024no ssh key dsassh server enabletelnet server enableThis example shows how to display the system configuration:
mxe# show running-config systemGenerating configuration........hostname mxe-node4clock timezone PST -8 0ntp server 171.68.10.80This example shows how to display the user configuration:
mxe# show running-config userGenerating configuration........user adminrole network-adminpassword 5 $1$DYzvO3zi$CBRmkrsQHs325h4YGHuAG0This example shows how to display the VSH configuration:
mxe# show running-config vshGenerating configuration........banner motd `^|^| MXE Shell -- PRO 5.0 Version^| Copyright (c) 2009by Cisco Systems, Inc.^| All rights reserved.^|^|`line vtyexec-timeout 0session-limit 32line consoleexec-timeout 0speed 9600parity nonestopbits 1Related Commands
Copies the running configuration to the startup configuration.
Displays the startup-configuration.
show startup-config
To display the startup configuration, use the show startup-config command.
show startup-config
Syntax Description
This command has no arguments or keywords.
Defaults
None
Command Modes
EXEC
Supported User Rolesnetwork-admin
network-operatorCommand History
Usage Guidelines
None
Examples
This example shows how to display the startup configuration:
mxe# show startup-configGenerating configuration........interface Ethernet 1/1ip address 10.194.60.57 255.255.255.0no shutdownip default-gateway 10.194.60.1interface Ethernet 1/1no ip addressno shutdowninterface MGT1ip address 10.194.60.56 255.255.255.0no shutdownip default-gateway 10.194.60.1snmp-server community blr-team rwsnmp-server community mxe5k rosnmp-server community sjp3 rwsnmp-server user user2 group network-admin auth md5 root1234snmp-server user user1 group network-admin auth sha a1234567 priv aes-128 b1234567snmp-server host 10.10.10.5 version 2c sjp3 udp-port 162snmp-server host 20.20.10.1 version 3 noauth user1 udp-port 162Related Commands
Copies the running configuration to the startup configuration.
Displays the running configuration.
show system reset-reason
To display the system reset history and the reset reasons, use the show system reset-reason command.
show system reset-reason
Syntax Description
This command has no arguments or keywords.
Defaults
None
Command Modes
EXEC
Supported User Rolesnetwork-admin
network-operatorCommand History
Usage Guidelines
This command displays the history of reset reasons along with the time stamp. The history log stores up to a maximum 20 reset reasons. If there is an unplanned reset, the time stamp shows when system came up.
Examples
This example shows how to display the Cisco MXE 5600 reset-reason history:
mxe# show system reset-reasonReload Time Reason--------------------------------------------------------------Fri Jun 11 14:43:55 PST 2010 Software Upgrade ReloadWed Jun 16 09:31:23 PST 2010 Reload from CLIRelated Commands
show system uptime
To display the amount of time since the last system restart, use the show system uptime command.
show system uptime
Syntax Description
This command has no arguments or keywords.
Defaults
Displays information for all features.
Command Modes
EXEC
Supported User Rolesnetwork-admin
network-operatorCommand History
Usage Guidelines
None
Examples
This example shows how to display the amount of time since the last system restart:
mxe# show system uptime9 hours 14 minutes 12 secondsshow tech-support
To display information for Cisco technical support, use the show tech-support command.
show tech-support
Syntax Description
This command has no arguments or keywords.
Defaults
Displays information for all features.
Command Modes
EXEC
Supported User Rolesnetwork-admin
network-operatorCommand History
Usage Guidelines
The output from this command can be very long.
Examples
This example shows how to display technical support information:
mxe# show tech-supportChecking DSP status...DSP information for 1.31.12.1Task Manager Health stats:dspState: 15[DSP_STATE_INITIALIZED], createCnt: 6, deleteCnt: 0, switchCnt: 1958706, currentTask: 0x8f287ecc, prevTask: 0x8c03504c, flags: 0x0Task Manager Heap Status:heap: 0, heapSize: 50331648, used: 263208, largestFree: 50068224heap: 1, heapSize: 94208, used: 0, largestFree: 94208heap: 2, heapSize: 16384, used: 0, largestFree: 16384heap: 3, heapSize: 0, used: 0, largestFree: 0Task Manager Task status:ThreadID Name Mode Priority StackSize MaxStackUsed CurrStackUsed CpuUsage0x8c03a43c AudioTra 0 11 16384 96 104 0.0%0x8c0376e4 MdpManag 0 7 8192 2036 592 0.0%0x8c03504c TaskMana 2 5 8192 152 160 0.0%0x8c003a64 Main 3 9 4096 1948 88 0.0%0x8c001a04 2 8 8192 772 280 0.0%0x8f287ecc TSK_idle 1 0 8192 376 376 0.0%DSP information for 1.31.13.1Task Manager Health stats:dspState: 15[DSP_STATE_INITIALIZED], createCnt: 8, deleteCnt: 0, switchCnt: 4416216, currentTask: 0x8f287ecc, prevTask: 0x8c0376e4, flags: 0x0Task Manager Heap Status:heap: 0, heapSize: 50331648, used: 314864, largestFree: 50016632heap: 1, heapSize: 94208, used: 0, largestFree: 94208heap: 2, heapSize: 16384, used: 0, largestFree: 16384heap: 3, heapSize: 0, used: 0, largestFree: 0Task Manager Task status:ThreadID Name Mode Priority StackSize MaxStackUsed CurrStackUsed CpuUsage0x8c042dbc H264Itti 0 11 16384 96 104 0.0%0x8c03e9fc H264Itti 2 11 16384 996 488 0.0%0x8c03a594 VideoSca 2 11 16384 996 488 0.0%0x8c0376e4 MdpManag 0 7 8192 2296 1424 0.0%0x8c03504c TaskMana 2 5 8192 152 160 0.0%0x8c003a64 Main 3 9 4096 1948 88 0.0%0x8c001a04 2 8 8192 772 280 0.0%0x8f287ecc TSK_idle 1 0 8192 376 376 0.0%DSP information for 1.31.14.1Task Manager Health stats:dspState: 15[DSP_STATE_INITIALIZED], createCnt: 8, deleteCnt: 0, switchCnt: 4415618, currentTask: 0x8f287ecc, prevTask: 0x8c0376e4, flags: 0x0Task Manager Heap Status:heap: 0, heapSize: 50331648, used: 314864, largestFree: 50016560heap: 1, heapSize: 94208, used: 0, largestFree: 94208heap: 2, heapSize: 16384, used: 0, largestFree: 16384heap: 3, heapSize: 0, used: 0, largestFree: 0Task Manager Task status:ThreadID Name Mode Priority StackSize MaxStackUsed CurrStackUsed CpuUsage0x8c042d8c VideoSca 0 11 16384 96 104 0.0%0x8c03e9f4 H264Itti 2 11 16384 996 488 0.0%0x8c03a5dc H264Itti 2 11 16384 996 488 0.0%0x8c0376e4 MdpManag 0 7 8192 2060 1424 0.0%0x8c03504c TaskMana 2 5 8192 152 160 0.0%...show terminal
To display information about the terminal configuration for a session, use the show terminal command.
show terminal
Syntax Description
This command has no arguments or keywords.
Defaults
None
Command Modes
EXEC
Supported User Rolesnetwork-admin
network-operatorCommand History
Usage Guidelines
None
Examples
This example shows how to display information about the terminal configuration for a session:
mxe# show terminalTTY: /dev/pts/0, Type: "vt100"Length: 24 lines, Width: 80 columnsSession Timeout: NoneRelated Commands
Configures the terminal display length for the session.
Configures the terminal type for a session.
Configures the terminal display width for a session.
show version
To display information about the software version, use the show version command.
show version
Syntax Description
This command has no arguments or keywords.
Defaults
Displays software version information for the kick-start and system images running on the device.
Command Modes
EXEC
Supported User Rolesnetwork-admin
network-operatorCommand History
Usage Guidelines
None
Examples
This example shows how to display the version information for the kick-start and system image running on the device:
mxe# show version------------------------------------------------------------Cisco MXE-5000 Software Versions------------------------------------------------------------MXE-OS 1.0.0-61MXE-MEDIA-OS 1.0.0-61------------------------------------------------------------TAC support: http://www.cisco.com/tacCopyright (c) 2007-2010 by Cisco Systems, Inc.All rights reserved.The copyrights to certain works contained in this software are ownedby other third parties and used and distributed under license. Certaincomponents of this software are licensed under the GNU General PublicLicense (GPL) version 2.0 or the GNU Lesser General Public License(LGPL) Version 2.1. A copy of each such license is available athttp://www.opensource.org/licenses/gpl-2.0.php andhttp://www.opensource.org/licenses/lgpl-2.1.phpRelated Commands
speed
To configure the transmit and receive speed for the console port, use the speed command. To revert to the default, use the no form of this command.
speed speed
no speed speed
Syntax Description
Defaults
The default console port speed is 9600 b/s.
Command Modes
Console configuration
Supported User Rolesnetwork-admin
Command History
Usage Guidelines
You can configure the console port only from a session on the console port.
Examples
This example shows how to configure the speed for the console port:
mxe# configure terminalmxe(config)# line consolemxe(config-console)# speed 57600This example shows how to revert to the default speed for the console port:
mxe# configure terminalmxe(config)# line consolemxe(config-console)# no speed 57600Related Commands
stopbits
To configure the stop bits for the COM1 port or console port, use the stopbits command. To revert to the default, use the no form of this command.
stopbits {1 | 2}
no stopbits {1 | 2}
Syntax Description
Defaults
1 stop bit
Command Modes
Console configuration
Supported User Rolesnetwork-admin
Command History
Usage Guidelines
You can configure the console port only from a session on the console port.
Examples
This example shows how to configure the number of stop bits for the console port:
mxe# configure terminalmxe(config)# line consolemxe(config-console)# stopbits 2This example shows how to revert to the default number of stop bits for the console port:
mxe# configure terminalmxe(config)# line consolemxe(config-console)# no stopbits 2Related Commands
terminal length
To set the number of lines of output to display on the terminal screen for the current session before pausing, use the terminal length command. To revert to the default, use the no form of this command.
terminal length lines
terminal no length
Syntax Description
lines
Number of lines to display. The range is from 0 to 511. Use 0 to not pause while displaying output.
Defaults
The default for the console is 24 lines.
Command Modes
EXEC
Supported User Rolesnetwork-admin
network-operatorCommand History
Usage Guidelines
The session pauses after displaying the number of lines set in the terminal length. Press the space bar to display another screen of lines or press the Enter key to display another line. To return to the command prompt, press Ctrl-C. Use 0 to not pause while displaying output.
The terminal length setting applies only to the current session.
Examples
This example shows how to set the number of lines of command output to display on the terminal before pausing:
mxe# terminal length 28This example shows how to revert to the default number of lines:
mxe# terminal no lengthRelated Commands
terminal terminal-type
To set the terminal type for the current session, use the terminal terminal-type command. To revert to the default, use the no form of this command.
terminal terminal-type type
terminal no terminal-type
Syntax Description
type
Type of terminal. The type string is case sensitive, must be a valid type (for example, vt100 or xterm), and has a maximum of 80 characters.
Defaults
vt100
Command Modes
EXEC
Supported User Rolesnetwork-admin
network-operatorCommand History
Usage Guidelines
For a virtual terminal, the terminal type is set during negotiation with the client software; otherwise, the default applies.
The terminal type setting applies only to the current session.
Examples
This example shows how to set the terminal type:
mxe# terminal terminal-type xtermThis example shows how to revert to the default terminal type:
mxe# terminal no terminal-typeRelated Commands
terminal width
To set the number of character columns on the terminal screen for the current line for a session, use the terminal width command. To revert to the default, use the no form of this command.
terminal width columns
terminal no width
Syntax Description
Defaults
80 columns
Command Modes
EXEC
Supported User Rolesnetwork-admin
network-operatorCommand History
Usage Guidelines
For a virtual terminal, the terminal width is set during negotiation with the client software; otherwise, the default applies.
The terminal width setting applies only to the current session.
Examples
This example shows how to set the number of columns to display on the terminal:
mxe# terminal width 70This example shows how to revert to the default number of columns:
mxe# terminal no widthRelated Commands
upgrade software
To upgrade the Cisco MXE-OS, use the upgrade software command.
upgrade software {sftp | tftp}
Syntax Description
stfp
Specifies Secure File Transfer Protocol (SFTP).
tftp
Specifies Trivial File Transfer Protocol (TFTP).
Command Modes
EXEC
Supported User Rolesnetwork-admin
Command History
Usage Guidelines
None
Examples
This example shows upgrade the Cisco MXE-OS using the TFTP:
mxe# upgrade software tftpYou are using the software upgrade feature.The following information is needed for the upgrade to proceed.Please enter the information requestedTftpserver:10.194.58.126The upgrade requires a file with the updates to be installed.Please specify the filename including the full path relative from the tftp server rootUpgrade File:mxe-interop.tar.gzTrying to download mxe-interop.tar.gzmxe-interop.tar.gz Successfully downloadedUncompressing mxe-interop.tar.gzStarting the software updatechecking for node at 1.11.0.1Updating software on nodeUpdating software on card 1.31.0.1This can take 1-2 hours. Please be patientUpdating software on card 1.32.0.1This can take 1-2 hours. Please be patientUpgrade of 1.31.0.1 successfulUpgrade of 1.32.0.1 successfulUpdating software on node1Restarting Processes.....Upgrade successfulwrite
To erase startup configuration or save a running configuration for use at system startup, use the write command.
write {erase | memory}
Syntax Description
Defaults
Erase all startup configurations.
Command Modes
EXEC
Supported User Rolesnetwork-admin
Command History
Usage Guidelines
You can use this command to erase the startup configuration in the persistent memory when information is corrupted or otherwise unusable. Erasing the startup configuration and returns the device to its initial state after a system reload occurs.
Examples
This example shows how to erase the startup configuration:
mxe# write eraseRelated Commands
