Feedback
Table Of Contents
Cisco Nexus 7000 Series NX-OS Fundamentals Commands
clear install all failed-standby
copy running-config startup-config
terminal history no-exec-in-config
Cisco Nexus 7000 Series NX-OS Fundamentals Commands
This chapter describes the Cisco Nexus 7000 Series NX-OS fundamentals commands.
attach module
To start a command session on an I/O module, use the attach module command.
attach module slot-number
Syntax Description
Defaults
None
Command Modes
Any command mode
Supported User Rolesnetwork-admin
Command History
Usage Guidelines
To exit the I/O module session, use the exit command. To abort the session, use the $. character sequence.
You can also use the slot command to send commands to an I/O module from the supervisor module session.
Use the question mark character (?) to obtain context sensitive help.
This command does not require a license.
Examples
This example shows how to start a command session on an I/O module:
switch# attach module 2Attaching to module 2 ...To exit type 'exit', to abort type '$.'module-2#Related Commands
banner motd
To configure the message-of-the-day (MOTD) banner that displays when the 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
User Access Verification
Command Modes
Global configuration
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
To create a multiple-line MOTD banner, press Enter before typing the delimiting character to start a new line. You can enter up to 40 lines of text.
This command does not require a license.
Examples
This example shows how to configure a single-line MOTD banner:
switch# configure terminalswitch(config)# banner motd #Unauthorized access to this device is prohibited!#This example shows how to configure a multiple-line MOTD banner:
switch# configure terminalswitch(config)# banner motd #Welcome to authorized users!> Unauthorized access prohibited.#This example shows how to revert to the default MOTD banner:
switch# configure terminalswitch(config)# no banner motdRelated Commands
boot auto-copy
To enable automatic copying of boot image files to the standby supervisor module, use the boot auto-copy command. To disable automatic copying, use the no form of this command.
boot auto-copy
no boot auto-copy
Syntax Description
This command has no arguments or keywords.
Defaults
Enabled
Command Modes
Global configuration
Supported User Rolesnetwork-admin
Command History
Usage Guidelines
When automatic copying of image files is enabled, the Cisco NX-OS software copies the image files referred to by the boot variable to the standby supervisor module. These image files must be present in local memory on the active supervisor module. For kickstart and system boot variables, only those image files that are configured for the standby supervisor module are copied. For modules images, all modules present in the standby's corresponding locations (bootflash: or slot0:) will be copied.
This command does not require a license.
Examples
This example shows how to enable automatic copying of boot image files to the standby supervisor module:
switch# configure terminalswitch(config)# boot auto-copyAuto-copy administratively enabledRelated Commands
boot kickstart
To configure the boot variable for the Cisco NX-OS software kickstart image, use the boot kickstart command. To clear the kickstart image boot variable, use the no form of this command.
boot kickstart [filesystem:[//directory] | directory]filename [sup-1] [sup-2]
no boot kickstart
Syntax Description
Defaults
Configures for both supervisor modules.
Command Modes
Global configuration
Supported User Rolesnetwork-admin
Command History
Usage Guidelines
The Cisco NX-OS software uses the boot variable for loading images when booting up using the reload or install all command. You must copy the kickstart image to the device before you set the kickstart boot variable. You must also set the system boot variable using the boot system command.
Note
We recommend that you use the install all command to update the system image on your device.
For information on upgrading and downgrading images on your Cisco NX-OS device, see the Cisco Nexus 7000 Series NX-OS Software Upgrade and Downgrade Guide, Release 4.2.
This command does not require a license.
Examples
This example shows how to configure the kickstart boot variable for both supervisor modules:
switch# configure terminalswitch(config)# boot kickstart bootflash:kickstart-imageThis example shows how to configure the kickstart boot variable for the sup-1 supervisor module:
switch# configure terminalswitch(config)# boot kickstart bootflash:kickstart-image sup-1This example shows how to clear the kickstart boot variable:
switch# configure terminalswitch(config)# no boot kickstartRelated Commands
boot system
To configure the boot variable for the Cisco NX-OS software system image, use the boot system command. To clear the system image boot variable, use the no form of this command.
boot system [filesystem:[//directory] | directory]filename [sup-1] [sup-2]
no boot system
Syntax Description
Defaults
Configures for both supervisor modules.
Command Modes
Global configuration
Supported User Rolesnetwork-admin
Command History
Usage Guidelines
The Cisco NX-OS software uses the boot variable for loading images when booting up using the reload or install all command. You must copy the system image to the device before you set the system boot variable. You must also set the kickstart boot variable using the boot kickstart command.
Note
For information on upgrading and downgrading images on your Cisco NX-OS device, see the Cisco Nexus 7000 Series NX-OS Software Upgrade and Downgrade Guide, Release 4.2.
This command does not require a license.
Examples
This example shows how to configure the system boot variable for both supervisor modules:
switch# configure terminalswitch(config)# boot system bootflash:system-imageThis example shows how to configure the system boot variable for the sup-1 supervisor module:
switch# configure terminalswitch(config)# boot system bootflash:system-image sup-1This example shows how to clear the system boot variable:
switch# configure terminalswitch(config)# no boot systemRelated Commands
cd
To change the current working directory in the device file system, use the cd command.
cd [filesystem:[//directory] | directory]
Syntax Description
filesystem:
(Optional) Name of the file system. Valid values are bootflash, slot0, volatile, usb1, or usb2.
//directory
(Optional) Name of the directory. The directory name is case sensitive.
Defaults
bootflash
Command Modes
Any command mode
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
Use the pwd command to verify the current working directory.
You can change only the directories that are on the active supervisor module.
This command does not require a license.
Examples
This example shows how to change the current working directory on the current file system:
switch# cd my-scriptsThis example shows how to change the current working directory to another file system:
switch# cd slot0:This example shows how to revert back to the default working directory (bootflash):
switch# cdRelated 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
Any command mode
Supported User Rolesnetwork-admin
vdc-adminCommand 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).
This command does not require a license.
Examples
This example shows how to clear the command history:
switch# clear cli historyRelated Commands
clear debug-logfile
To clear the contents of the debug logfile, use the clear debug-logfile command.
clear debug-logfile filename
Syntax Description
Defaults
None
Command Modes
Any command mode
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
This command does not require a license.
Examples
This example shows how to clear the debug logfile:
switch# clear debug-logfile syslogd_debugsRelated Commands
debug logfile
Configures a debug logging file.
debug logging
Enable debug logging.
show debug logfile
Displays the contents of the debug logfile.
clear install all failed-standby
To clear the software installation failure log on the standby supervisor module, use the clear install all failed-standby command.
clear install all failed-standby
Syntax Description
This command has no arguments or keywords.
Defaults
None
Command Modes
Any command mode
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
This command does not require a license.
Examples
This example shows how to clear the software installation failure log on the standby supervisor module:
switch# clear install all failed-standbyRelated Commands
clear install failure-reason
To clear the reason for software installation failures, use the clear install failure-reason command.
clear install failure-reason
Syntax Description
This command has no arguments or keywords.
Defaults
None
Command Modes
Any command mode
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
This command does not require a license.
Examples
This example shows how to clear the reason for software installation failures:
switch# clear install failure-reasonRelated Commands
clear license
To uninstall a license, use the clear license command.
clear license filename
Syntax Description
Defaults
None
Command Modes
Any command mode
Supported User Rolesnetwork-admin
Command History
Usage Guidelines
This command does not require a license.
Examples
This example shows how to clear a specific license:
switch# clear license Enterprise.licClearing license Enterprise.lic:SERVER this_host ANYVENDOR ciscoDo you want to continue? (y/n) yClearing license ..doneswitch#Related Commands
cli alias name
To configure a command alias, use the cli alias name command. To delete a command alias, use the no form of this command.
cli alias name alias-name alias-text
no cli alias name
Syntax Description
Defaults
None
Command Modes
Global configuration
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
You can use the command to create aliases for commands that you use frequently.
The Cisco NX-OS software has one predefined command alias called alias. You can use it to display the currently configured command aliases.
This command does not require a license.
Examples
This example shows how to configure a command alias:
switch# configure terminalswitch(config)# cli alias name crun copy running-config startup-configThis example shows how to delete a command alias:
switch# configure terminalswitch(config)# no cli alias name crunRelated Commands
cli var name
To define a command-line interface (CLI) variable for a terminal session, use the cli var name command. To remove the CLI variable, use the no form of this command.
cli var name variable-name variable-text
cli no var name variable-name
Syntax Description
Defaults
None
Command Modes
Any command mode
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
You can reference a CLI variable using the following syntax:
$(variable-name)
Instances where you can use variables in include the following:
•
•
You cannot reference a variable in the definition of another variable.
The Cisco NX-OS software provides a predefined variable, TIMESTAMP, that you can use to insert the time of day. You cannot change or remove the TIMESTAMP CLI variable.
You must remove a CLI variable before you can change its definition.
This command does not require a license.
Examples
This example shows how to define a CLI variable:
switch# cli var name testinterface interface 2/3This example shows how to reference a CLI variable:
switch# cd slot0:This example shows how to reference the TIMESTAMP variable:
switch# copy running-config > bootflash:run-config-$(TIMESTAMP).cnfgThis example shows how to remove a CLI variable:
switch# cli no var name testinterface interface 2/3Related Commands
clock set
To manually set the clock on a Cisco NX-OS device, use the clock set command.
clock set time day month year
Syntax Description
Defaults
None
Command Modes
Any command mode
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
Use this command when you cannot synchronize your device with an outside clock source, such as NTP.
This command does not require a license.
Examples
This example shows how to manually configure the clock:
switch# clock set 9:00:00 1 June 2008Related Commands
clock summer-time
To configure the summer-time (daylight saving time) offset, use the clock summer-time command. To revert to the default, 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
None
Command Modes
Global configuration
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
This command does not require a license.
Examples
This example shows how to configure the offset for summer-time or daylight saving time:
switch# configure terminalswitch(config)# clock summer-time PDT 2 Sunday March 02:00 1 Sunday November 02:00 60This example shows how to remove the summer-time offset:
switch# configure terminalswitch(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 revert to the default, use the no form of this command.
clock timezone zone-name offset-hours offset-minutes
no clock timezone
Syntax Description
Defaults
None
Command Modes
Any command mode
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
Use this command to offset the device clock from UTC.
This command does not require a license.
Examples
This example shows how to configure the time zone offset from UTC:
switch# clock timezone EST 5 0This example shows how to remove the time zone offset:
switch# 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
Any command mode
Supported User Rolesnetwork-admin
vdc-adminCommand 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.
This command does not require a license.
Examples
This example shows how to enter global configuration mode:
switch# configure terminalswitch(config)#Related Commands
copy
To copy any file from a source to a destination, use the copy command.
copy source-url destination-url
Syntax Description
The format of the source and destination URLs varies according to the file or directory location. You may enter either a command-line interface (CLI) variable for a directory or a filename that follows the Cisco NX-OS file system syntax (filesystem:[/directory][/filename]).
The following tables list URL prefix keywords by the file system type. If you do not specify a URL prefix keyword, the router looks for a file in the current directory.
Table 1 lists URL prefix keywords for local writable storage file systems. Table 2 lists the URL prefix keywords for remote file systems. Table 3 lists the URL prefix keywords for nonwritable file systems.
Defaults
The default name for the destination file is the source filename.
Command Modes
Any command mode
Supported User Rolesnetwork-admin
vdc-adminCommand History
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 using a Cisco NX-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.
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 (such as bootflash).
In the URL syntax for ftp:, scp:, sftp:, and tftp:, the server is either an IPv4 address or a hostname.
This command does not require a license.
This section contains usage guidelines for the following topics:
•
•
•
•
Copying Files from a Server to Bootflash Memory
Use the copy source-url bootflash: command (for example, copy tftp:source-url bootflash:) to copy an image from a server to the local bootflash memory.
Copying a Configuration File from a Server to the Running Configuration
Use the copy {ftp: | scp: | 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.
You can copy either a host configuration file or a network configuration file. Accept the default value of host to copy and load a host configuration file containing commands that apply to one network server in particular. Enter network to copy and load a network configuration file that contains commands that apply to all network servers on a network.
Copying a Configuration File from a Server to the Startup Configuration
Use the copy {ftp: | scp: | sftp: | tftp:}source-url startup-config command to copy a configuration file from a network server to the router startup configuration. These commands replace the startup configuration file with the copied configuration file.
Copying the Running or Startup Configuration on a Server
Use the copy running-config {ftp: | scp: | sftp: | tftp:}destination-url command to copy the current configuration file to a network server that uses FTP, scp, SFTP, or TFTP. Use the copy startup-config {ftp: | scp: | stfp: | tftp:}destination-url command to copy the startup configuration file to a network server.
You can use the copied configuration file copy as a backup.
Examples
This example shows how to copy a file within the same directory:
switch# copy file1 file2This example shows how to copy a file to another directory:
switch# copy file1 my_files:file2This example shows how to copy a file to another file system:
switch# copy file1 slot0:This example shows how to copy a file to another supervisor module:
switch# copy file1 bootflash://sup-remote/file1.bakThis example shows how to copy a file from a remote server:
switch# copy scp://10.10.1.1/image-file.bin bootflash:image-file.binRelated 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
Any command mode
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
Use this command to save your configuration changes in the running configuration to the startup configuration in persistent memory. When a device reload or switchover occurs, the saved configuration is applied.
This command does not require a license.
Examples
This example shows how to save the running configuration to the startup configuration:
switch# copy running-config startup-config[########################################] 100%Related Commands
databits
To configure the number of data bits in a character for the COM1 port or console port, use the databits command. To revert to the default, use the no form of this command.
databits bits
no databits bits
Syntax Description
Defaults
8 bits
Command Modes
COM1 port configuration
console port configurationSupported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
You can use this command only in the default virtual device context (VDC).
You can configure the console and COM1 ports only from a session on the console port.
This command does not require a license.
Examples
This example shows how to configure the number of data bits for the COM1 port:
switch# configure terminalswitch(config)# line com1switch(config-com1)# databits 7This example shows how to configure the number of data bits for the console port:
switch# configure terminalswitch(config)# line consoleswitch(config-console)# databits 7This example shows how to revert to the default number of data bits for the COM1 port:
switch# configure terminalswitch(config)# line com1switch(config-com1)# no databits 7This example shows how to revert to the default number of data bits for the console port:
switch# configure terminalswitch(config)# line consoleswitch(config-console)# no databits 7Related Commands
show line
Displays information about the COM1 port and console port configuration.
debug logfile
To direct the output of the debug commands to a specified file, use the debug logfile command. To revert to the default, use the no form of this command.
debug logfile filename [size bytes]
no debug logfile filename [size bytes]
Syntax Description
Defaults
Default filename: syslogd_debugs
Default file size: 4194304 bytes
Command Modes
Any command mode
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
The Cisco NX-OS software creates the logfile in the log: file system root directory. Use the dir log: command to display the log files.
This command does not require a license.
Examples
This example shows how to specify a debug logfile:
switch# debug logfile debug_logThis example shows how to revert to the default debug logfile:
switch# no debug logfile debug_logRelated Commands
dir
Displays the contents of a directory.
show debug
Displays the debug configuration.
show debug logfile
Displays the debug logfile contents.
debug logging
To enable debug command output logging, use the debug logging command. To disable debug logging, use the no form of this command.
debug logging
no debug logging
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Any command mode
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
This command does not require a license.
Examples
This example shows how to enable the output logging for the debug command:
switch# debug loggingThis example shows how to disable the output logging for the debug command:
switch# no debug loggingRelated Commands
delete
To delete a file, use the delete command.
delete [filesystem:[//directory/] | directory/]filename
Syntax Description
Defaults
None
Command Modes
Any command mode
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
Use the dir command to locate the file you that want to delete.
This command does not require a license.
Examples
This example shows how to delete a file:
switch# delete bootflash:old_config.cfgRelated Commands
diff-clean
To remove the temporary files created automatically when you use diff filtering in show commands, use the diff-clean command.
diff-clean [all-sessions | all-users]
Syntax Description
Defaults
Removes the temporary file for the current session of the current user.
Command Modes
All command modes
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
This command does not require a license.
Examples
This example shows how to remove the temporary files for the current session of the current user:
switch# diff-cleanThis example shows how to remove the temporary files for the current session and all past sessions of the current user:
switch# diff-clean all-sessionsThis example shows how to remove the temporary files for the current sessions and all past sessions of all users:
switch# diff-clean all-usersdir
To display the contents of a directory, use the dir command.
dir [filesystem:[//directory/] | directory/]
Syntax Description
Defaults
Displays the contents of the current working directory.
Command Modes
Any command mode
Supported User Rolesnetwork-admin
vdc-admin
network-operator
vdc-operatorCommand History
Usage Guidelines
Use the pwd command to verify the current working directory.
Use the cd command to change the current working directory.
This command does not require a license.
Examples
This example shows how to display the contents of the root directory in bootflash:
switch# dir bootflash:This example shows how to display the contents of the current working directory:
switch# dirRelated Commands
cd
Changes the current working directory.
pwd
Displays the name of the current working directory.
echo
To display a text string on the terminal session, use the echo command.
echo [backslash-interpret] [text]
Syntax Description
Defaults
Displays a blank line
Command Modes
Any command mode
Supported User Rolesnetwork-admin
vdc-adminCommand History
4.0(1)
This command was introduced.
4.0(3)
Replaced the -e keyword with the backslash-interpret keyword.
Usage Guidelines
You can use this command in a command script to display information while the script is running.
Table 4 lists the formatting keywords that you can insert in the text when you include the backslash-interpret keyword.
This command does not require a license.
Examples
This example shows how to display a blank line at the command prompt:
switch# echoswitch#This example shows how to display a line of text at the command prompt:
switch# echo Script run at $(TIMESTAMP).Script run at 2008-08-12-23.29.24.This example shows how to use a formatting option in the text string:
switch# echo backslash-interpret This is line #1. \nThis is line #2.This is line #1.This is line #2.Related 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
Supported User Rolesnetwork-admin
vdc-admin
network-operator
vdc-operatorCommand History
Usage Guidelines
This command does not require a license.
Examples
This example shows how to return to EXEC mode from global configuration mode:
switch(config)# endswitch#This example shows how to return to EXEC mode from interface configuration mode:
switch(config-if)# endswitch#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
vdc-adminCommand History
Usage Guidelines
You can use this command only in the default virtual device context (VDC).
You can configure the console ports only from a session on the console port.
This command does not require a license.
Examples
This example shows how to configure the inactive session timeout for the console port:
switch# configure terminalswitch(config)# line consoleswitch(config-com1)# exec-timeout 30This example shows how to configure the inactive session timeout for the virtual terminal:
switch# configure terminalswitch(config)# line vtyswitch(config-line)# exec-timeout 30This example shows how to revert to the default inactive session timeout for the console port:
switch# configure terminalswitch(config)# line consoleswitch(config-com1)# no exec-timeoutThis example shows how to revert to the default inactive session timeout for the virtual terminal:
switch# configure terminalswitch(config)# line vtyswitch(config-line)# no exec-timeoutRelated Commands
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
vdc-admin
network-operator
vdc-operatorCommand History
Usage Guidelines
This command does not require a license.
Examples
This example shows how to return to EXEC mode from global configuration mode:
switch(config)# exitswitch#This example shows how to return to global configuration mode from interface configuration mode:
switch(config-if)# exitswitch(config)#Related Commands
find
To find filenames beginning with a character string, use the find command.
find filename-prefix
Syntax Description
Defaults
None
Command Modes
Any command mode
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
The find command searches all subdirectories under the current working directory. You can use the cd and pwd commands to navigate to the starting directory.
This command does not require a license.
Examples
This example shows how to display filenames beginning with ospf:
switch# find ospf/usr/bin/find: ./lost+found: Permission denied./ospf-gr.cfg./ospfgrconfig./ospf-gr.confRelated Commands
cd
Changes the current working directory.
pwd
Displays the name of the current working directory.
flowcontrol hardware
To enable flow control on the COM1 port, use the flowcontrol hardware command. To disable flow control, use the no form of this command.
flowcontrol hardware
no flowcontrol hardware
Syntax Description
This command has no arguments or keywords.
Defaults
Enabled
Command Modes
COM1 port configuration
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
You can use this command only in the default virtual device context (VDC).
You can configure the COM1 ports only from a session on the console port or COM1 port.
This command does not require a license.
Examples
This example shows how to enable flow control for the COM1 port:
switch# configure terminalswitch(config)# line com1switch(config-com1)# flowcontrol hardwareThis example shows how to disable flow control for the COM1 port:
switch# configure terminalswitch(config)# line com1switch(config-com1)# no flowcontrol hardwareRelated Commands
show line
Displays information about the COM1 port and console port configuration.
format
To format an external Flash device to erase the contents and restore it to its factory-shipped state, use the format command.
format filesystem:
Syntax Description
Defaults
None
Command Modes
Any command mode
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
You can use this command only in the default virtual device context (VDC).
Note
This command does not require a license.
Examples
This example shows how to format an external Flash device:
switch# format slot0:Related Commands
cd
Changes the current working directory.
dir
Displays the directory contents.
pwd
Displays the name of the current working directory.
gunzip
To uncompress a compressed file, use the gunzip command.
gunzip filename
Syntax Description
Defaults
None
Command Modes
Any command mode
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
The compressed filename must have the .gz extension. You do not have to enter the .gz extension as part of the filename.
The Cisco NX-OS software uses Lempel-Ziv 1977 (LZ77) coding for compression.
This command does not require a license.
Examples
This example shows how to uncompress a compressed file:
switch# gunzip run_cnfg.cfgRelated Commands
gzip
To compress a file, use the gzip command.
gzip filename
Syntax Description
Defaults
None
Command Modes
Any command mode
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
After you use this command, the file is replaced with the compressed filename that has the .gz extension.
The Cisco NX-OS software uses Lempel-Ziv 1977 (LZ77) coding for compression.
This command does not require a license.
Examples
This example shows how to compress a file:
switch# gzip run_cnfg.cfgRelated Commands
hostname
To configure the hostname 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.
Defaults
switch
Command Modes
Global configuration
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
The Cisco NX-OS software uses the hostname in command-line interface (CLI) prompts and in default configuration filenames.
The hostname command performs the same function as the switchname command.
This command does not require a license.
Examples
This example shows how to configure the device hostname:
switch# configure terminalswitch(config)# hostname Engineering2Engineering2(config)#This example shows how to revert to the default device hostname:
Engineering2# configure terminalEngineering2(config)# no hostnameswitch(config)#Related Commands
switchname
Configures the device hostname.
show hostname
Displays the device hostname.
install all
To install the kickstart and system images on your Cisco NX-OS device, use the install all command.
install all
[kickstart {bootflash: | ftp:[//server][/path] | scp:[//[username@]server][/path] | sftp:[//[username@]server][/path] | slot0: | tftp:[//server[:port]][/path] | volatile:}kickstart-filename]
[system {bootflash: | ftp:[//server][/path] | scp:[//[username@]server][/path] | sftp:[//[username@]server][/path] | slot0: | tftp:[//server[:port]][/path] | volatile:}system-filename]Syntax Description
Defaults
If you do not enter any parameters, the boot variable values are used.
The path is the default for the user on the remote server.
Command Modes
Any command mode
Supported User Rolesnetwork-admin
Command History
Usage Guidelines
If you do not enter the information about the server or username when downloading and installing the image files from a remote server, you are prompted for the information.
This command sets the kickstart and system boot variables and copies the image files to the redundant supervisor module.
You can use install all command to downgrade the Cisco NX-OS software on the device. To determine the incompatibility of the downgrade Cisco NX-OS software with the current Cisco NX-OS configuration on the device, use the show incompatibility system command and resolve any configuration incompatibilities.
This command only installs Cisco NX-OS software on devices with dual supervisor modules. To install new Cisco NX-OS software on a device with a single supervisor, you must use the reload command to boot the system after you use the install all command. For information on upgrading and downgrading images on your Cisco NX-OS device, see the Cisco Nexus 7000 Series NX-OS Software Upgrade and Downgrade Guide, Release 4.2.
The install all command does not install EPLD images.
This command does not require a license.
Examples
This example shows how to install the Cisco NX-OS software from the bootflash: directory:
switch# install all kickstart bootflash:nx-os_kick.bin system bootflash:nx-os_sys.binThis example shows how to install the Cisco NX-OS software using the values configured in the kickstart and system boot variables:
switch# configure terminalswitch(config)# boot kickstart bootflash:nx-os_kick.binswitch(config)# boot system bootflash:nx-os_sys.binswitch(config)# exitswitch# copy running-config startup-configswitch# install allThis example shows how to install the Cisco NX-OS software from an SCP server:
switch# install all kickstart scp://adminuser@10.10.1.1/nx-os_kick.bin system bootflash:scp://adminuser@10.10.1.1/nx-os_sys.binRelated Commands
install all epld
To upgrade the electronic programmable logical device (EPLD) image, use the install all epld command.
install all epld [bootflash: epld-image-name | slot0: epld-image-name | volatile: epld-image-name]
Syntax Description
Defaults
None
Command Modes
Any command mode
Supported User Rolesnetwork-admin
Command History
Usage Guidelines
Follow these guidelines when you upgrade or downgrade the EPLD:
•
•
–
–
•
•
•
•
This command does not require a license.
Examples
This example shows how to upgrade a Cisco NX-OS EPLD image:
switch# install all epld bootflash:n7000-s1-epld.4.2.1.imgCompatibility check:Module Type Upgradable Impact Reason------ ---- ---------- ---------- ------3 LC Yes disruptive Module Upgradable5 SUP Yes disruptive Module Upgradable7 LC Yes disruptive Module Upgradable9 LC Yes disruptive Module Upgradable1 Xbar Yes disruptive Module Upgradable2 Xbar Yes disruptive Module Upgradable3 Xbar Yes disruptive Module Upgradable1 FAN Yes disruptive Module Upgradable2 FAN Yes disruptive Module Upgradable3 FAN Yes disruptive Module Upgradable4 FAN Yes disruptive Module UpgradableRetrieving EPLD versions... Please wait.Images will be upgraded according to following table:Module Type EPLD Running-Version New-Version Upg-Required------ ---- ------------- --------------- ----------- ------------3 LC Power Manager 5.4 5.6 Yes3 LC IO 2.11 2.13 Yes3 LC Forwarding Engine 1.6 1.6 No5 SUP Power Manager 3.7 3.9 Yes5 SUP IO 3.26 3.28 Yes5 SUP Inband 1.7 1.8 Yes5 SUP Local Bus CPLD 3.0 3.0 No5 SUP CMP CPLD 6.0 6.0 No7 LC Power Manager 4.6 4.8 Yes7 LC IO 1.14 1.15 Yes7 LC Forwarding Engine 1.6 1.6 No7 LC FE Bridge(1) 186.3 186.3 No7 LC FE Bridge(2) 186.3 186.3 No7 LC Linksec Engine(1) 1.8 2.2 Yes7 LC Linksec Engine(2) 1.8 2.2 Yes7 LC Linksec Engine(3) 1.8 2.2 Yes7 LC Linksec Engine(4) 1.8 2.2 Yes7 LC Linksec Engine(5) 1.8 2.2 Yes7 LC Linksec Engine(6) 1.8 2.2 Yes7 LC Linksec Engine(7) 1.8 2.2 Yes7 LC Linksec Engine(8) 1.8 2.2 Yes9 LC Power Manager 5.4 5.6 Yes9 LC IO 2.11 2.13 Yes9 LC Forwarding Engine 1.6 1.6 No1 Xbar Power Manager 2.9 2.10 Yes2 Xbar Power Manager 2.9 2.10 Yes3 Xbar Power Manager 2.9 2.10 Yes1 FAN Fan Controller (1) 0.5 0.7 Yes1 FAN Fan Controller (2) 0.5 0.7 Yes2 FAN Fan Controller (1) 0.5 0.7 Yes2 FAN Fan Controller (2) 0.5 0.7 Yes3 FAN Fan Controller (1) 0.5 0.7 Yes3 FAN Fan Controller (2) 0.5 0.7 Yes4 FAN Fan Controller (1) 0.4 0.7 Yes4 FAN Fan Controller (2) 0.4 0.7 YesThe above modules require upgrade.Do you want to continue (y/n) ? [n]Related Commands
install fan-module epld
To install an electronically programmable logical device (EPLD) image on a fan module, use the install fan-module epld command.
install fan-module slot epld {bootflash: | slot0: | volatile:}filename
Syntax Description
slot
Slot number in chassis.
bootflash:
Specifies the internal Flash memory.
slot0:
Specifies the external Flash memory.
volatile:
Specifies the volatile memory.
filename
Name of the EPLD image file.
Defaults
None
Command Modes
Any command mode
Supported User Rolesnetwork-admin
Command History
Usage Guidelines
You must copy the EPLD image file to local storage before you can install it.
Enter this command from the active supervisor module to update any other module.
Use the show version fan slot epld command to display the EPLD version for a fan module.
Caution
This command does not require a license.
Examples
This example shows how to install an EPLD image on a module:
switch# install fan-module 1 epld bootflash:n7000-s1-epld.4.0.2.binRelated Commands
copy
Copies files.
show version
Displays information about the software version.
install license
To install a license, use the install license command.
install license {bootflash: | slot0: | usb0: | usb1:}src-filename [target-filename]
Syntax Description
Defaults
No license is installed.
Command Modes
Any command mode
Supported User Rolesnetwork-admin
Command History
Usage Guidelines
If a target filename is provided after the source location, the license file is installed with that name. Otherwise, the filename in the source URL is used. This command also verifies the license file before installing it.
For information on installing licenses on your Cisco NX-OS device, see the Cisco Nexus 7000 Series NX-OS Licensing Guide, Release 4.2.
This command does not require a license.
Examples
This example shows how to install a file named license-file that resides in the bootflash: directory:
switch# install license bootflash:license-fileRelated Commands
install module epld
To install an electronically programmable logical device (EPLD) image on an I/O module, use the install module epld command.
install module slot epld {bootflash: | slot0: | volatile:}filename
Syntax Description
slot
Slot number in chassis.
bootflash:
Specifies the internal Flash memory.
slot0:
Specifies the external Flash memory.
volatile:
Specifies the volatile memory.
filename
Name of the EPLD image file.
Defaults
None
Command Modes
Any command mode
Supported User Rolesnetwork-admin
Command History
Usage Guidelines
You must copy the EPLD image file to local storage before you can install it.
Enter this command from the active supervisor module to update any other module.
Use the show version module slot epld command to display the EPLD version for a fabric module.
Caution
This command does not require a license.
Examples
This example shows how to install an EPLD image on a fabric module:
switch# install module 2 epld bootflash:n7000-s1-epld.4.0.2.binRelated Commands
copy
Copies files.
show version
Displays information about the software version.
install xbar-module epld
To install an electronically programmable logical device (EPLD) image on a fabric module, use the install xbar-module epld command.
install xbar-module slot epld {bootflash: | slot0: | volatile:}filename
Syntax Description
slot
Slot number in chassis.
bootflash:
Specifies the internal Flash memory.
slot0:
Specifies the external Flash memory.
volatile:
Specifies the volatile memory.
filename
Name of the EPLD image file.
Defaults
None
Command Modes
Any command mode
Supported User Rolesnetwork-admin
Command History
Usage Guidelines
You must copy the EPLD image file to local storage before you can install it.
Enter this command from the active supervisor module to update any other module.
Use the show version xbar slot epld command to display the EPLD version for an I/O module.
Caution
This command does not require a license.
Examples
This example shows how to install an EPLD image on an I/O module:
switch# install xbar-module 2 epld bootflash:n7000-s1-epld.4.0.2.binRelated Commands
copy
Copies files.
show version
Displays information about the software version.
line com1
To specify the COM1 port and enter COM1 port configuration mode, use the line com1 command.
line com1
Syntax Description
This command has no arguments or keywords.
Defaults
None
Command Modes
Global configuration
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
You can configure the COM1 line from a console port session or a COM1 port session.
This command does not require a license.
Examples
This example shows how to enter COM1 port configuration mode:
switch# configure terminalswitch(config)# line com1switch(config-com1)#Related Commands
show line
Displays information about the COM1 port and console port configuration.
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
vdc-adminCommand History
Usage Guidelines
You can use this command only in the default virtual device context (VDC).
You can configure the console line only from a console port session.
This command does not require a license.
Examples
This example shows how to enter console port configuration mode:
switch# configure terminalswitch(config)# line consoleswitch(config-console)#Related Commands
show line
Displays information about the COM1 port and console port configuration.
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
vdc-adminCommand History
Usage Guidelines
This command does not require a license.
Examples
This example shows how to enter console port configuration mode:
switch# configure terminalswitch(config)# line vtyswitch(config-line)#Related Commands
show line
Displays information about the COM1 port and console port configuration.
modem connect line
To notify the Cisco NX-OS that you connected a modem, use the modem connect line command.
modem connect line {com1 | console}
Syntax Description
com1
Specifies that you have connected the modem to the COM1 port.
console
Specifies that you have connected the modem to the console port.
Defaults
None
Command Modes
Any command mode
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
You can use this command only in the default virtual device context (VDC).
This command does not require a license.
Examples
This example shows how to notify the device that you have connected a modem to the COM1 port:
switch# modem connect line com1This example shows how to notify the device that you have connected a modem to the console port:
switch# modem connect line consoleRelated Commands
modem in
Enables the modem connection on the COM1 port or console port.
show line
Displays information about the COM1 and console port configuration.
modem in
To enable the modem connection on the COM1 or console port, use the modem in command. To disable the modem connection, use the no form of this command.
modem in
no modem in
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
COM1 port configuration
console port configurationSupported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
You can use this command only in the default virtual device context (VDC).
You can configure the console and COM1 ports only from a session on the console port.
This command does not require a license.
Examples
This example shows how to enable a modem connection on the COM1 port:
switch# configure terminalswitch(config)# line com1switch(config-com1)# modem inThis example shows how to enable a modem connection on the console port:
switch# configure terminalswitch(config)# line consoleswitch(config-console)# modem inThis example shows how to disable a modem connection on the console port:
switch# configure terminalswitch(config)# line consoleswitch(config-console)# no modem inRelated Commands
line console
Enters console port configuration mode.
line com1
Enters COM1 port configuration mode.
show line
Displays information about the COM1 and console port configuration.
modem init-string
To download the initialization string to a modem connected to the COM1 or console port, use the modem init-string command. To revert to the default, use the no form of this command.
modem init-string {default | user-input}
no modem init-string
Syntax Description
default
Downloads the default initialization string.
user-input
Downloads the user-input initialization string.
Defaults
The default initialization string is ATE0Q1&D2&C1S0=1\015.
Command Modes
COM1 port configuration
console port configurationSupported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
You can use this command only in the default virtual device context (VDC).
You can configure the console and COM1 ports only from a session on the console port.
The default initialization string ATE0Q1&D2&C1S0=1\015 is defined as follows:
•
•
•
•
•
•
•
Use the modem set-string command to configure the user-input initialization string.
This command does not require a license.
Examples
This example shows how to download the default initialization string to the modem connected to the COM1 port:
switch# configure terminalswitch(config)# line com1switch(config-com1)# modem init-string defaultThis example shows how to download the default initialization string to the modem connected to the console port:
switch# configure terminalswitch(config)# line consoleswitch(config-console)# modem init-string defaultThis example shows how to download the user-input initialization string to the modem connected to the COM1 port:
switch# configure terminalswitch(config)# line com1switch(config-com1)# modem init-string user-inputThis example shows how to download the user-input initialization string to the modem connected to the console port:
switch# configure terminalswitch(config)# line consoleswitch(config-console)# modem init-string user-inputThis example shows how to revert to the default initialization string for the modem connected to the COM1 port:
switch# configure terminalswitch(config)# line com1switch(config-com1)# no modem init-stringThis example shows how to revert to the default initialization string for the modem connected to the console port:
switch# configure terminalswitch(config)# line consoleswitch(config-console)# no modem init-stringRelated Commands
modem restart line
To restart a modem connection on the COM1 port or console port, use the modem restart line command.
modem restart line {com1 | console}
Syntax Description
Defaults
None
Command Modes
Any command mode
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
You can use this command only in the default virtual device context (VDC).
This command does not require a license.
Examples
This example shows how to restart a modem connected to the COM1 port:
switch# modem restart line com1This example shows how to restart a modem connected to the console port:
switch# modem restart line consoleRelated Commands
modem in
Enables the modem connection on the COM1 port or console port.
show line
Displays information about the COM1 and console port configuration.
modem set-string user-input
To configure the user-input initialization string to download to a modem connected to the COM1 or console port, use the modem set-string user-input command. To revert to the default, use the no form of this command.
modem set-string user-input string
no modem set-string
Syntax Description
string
User-input string. This string is alphanumeric and case sensitive, can contain special characters, and has a maximum of 100 characters.
Defaults
None
Command Modes
COM1 port configuration
console port configurationSupported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
You can use this command only in the default virtual device context (VDC).
You can configure the console and COM1 ports only from a session on the console port.
This command does not require a license.
Examples
This example shows how to configure the user-input initialization string for the modem connected to the COM1 port:
switch# configure terminalswitch(config)# line com1switch(config-com1)# modem set-string user-input ATE0Q1&D2&C1S0=3\015This example shows how to configure the user-input initialization string for the modem connected to the console port:
switch# configure terminalswitch(config)# line consoleswitch(config-console)# modem set-string user-input ATE0Q1&D2&C1S0=3\015This example shows how to revert to the default user-input initialization string for the modem connected to the COM1 port:
switch# configure terminalswitch(config)# line com1switch(config-com1)# no modem set-stringThis example shows how to revert to the default user-input initialization string for the modem connected to the console port:
switch# configure terminalswitch(config)# line consoleswitch(config-console)# no modem set-stringRelated Commands
move
To move a file from one directory to another, use the move command.
move [filesystem:[//module/][directory/] | directory/]source-filename {{filesystem:[//module/][directory/] | directory/}[destination-filename] | target-filename}
Syntax Description
Defaults
The default name for the destination file is the same as the source filename.
Command Modes
Any command mode
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
You can make a copy of a file by using the copy command.
Tip
This command does not require a license.
Examples
This example shows how to move a file to another directory:
switch# move file1 my_files:file2This example shows how to move a file to another file system:
switch# move file1 slot0:This example shows how to move a file to another supervisor module:
switch# move file1 bootflash://sup-remote/file1.bakRelated Commands
cd
Changes the current working directory.
copy
Makes a copy of a file.
dir
Displays the directory contents.
pwd
Displays the name of the current working directory.
parity
To configure the parity for the COM1 port or 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
COM1 port configuration
console port configurationSupported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
You can use this command only in the default virtual device context (VDC).
You can configure the console and COM1 ports only from a session on the console port.
This command does not require a license.
Examples
This example shows how to configure the parity for the COM1 port:
switch# configure terminalswitch(config)# line com1switch(config-com1)# parity evenThis example shows how to configure the parity for the console port:
switch# configure terminalswitch(config)# line consoleswitch(config-console)# parity evenThis example shows how to revert to the default parity for the COM1 port:
switch# configure terminalswitch(config)# line com1switch(config-com1)# no parity evenThis example shows how to revert to the default parity for the console port:
switch# configure terminalswitch(config)# line consoleswitch(config-console)# no parity evenRelated Commands
show line
Displays information about the COM1 port and console port configuration.
ping
To determine the network connectivity to another device using IPv4 addressing, use the ping command.
ping {dest-ipv4-address | hostname} [count {number | unlimited}] [df-bit] [interval seconds] [packet-size bytes] [source src-ipv4-address] [timeout seconds] [vrf vrf-name]
Syntax Description
Defaults
For the default values, see the "Syntax Description" section for this command.
Command Modes
Any command mode
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
To determine the network connectivity to another device using IPv6 addressing, use the ping6 command.
This command does not require a license.
Examples
This example shows how to determine connectivity to another device using IPv4 addressing:
switch# ping 172.28.231.246 vrf managementPING 172.28.231.246 (172.28.231.246): 56 data bytesRequest 0 timed out64 bytes from 172.28.231.246: icmp_seq=1 ttl=63 time=0.799 ms64 bytes from 172.28.231.246: icmp_seq=2 ttl=63 time=0.597 ms64 bytes from 172.28.231.246: icmp_seq=3 ttl=63 time=0.711 ms64 bytes from 172.28.231.246: icmp_seq=4 ttl=63 time=0.67 ms--- 172.28.231.246 ping statistics ---5 packets transmitted, 4 packets received, 20.00% packet lossround-trip min/avg/max = 0.597/0.694/0.799 msRelated Commands
ping6
To determine the network connectivity to another device using IPv6 addressing, use the ping6 command.
ping6 {dest-ipv6-address | hostname} [count {number | unlimited}] [interface intf-id] [interval seconds] [packet-size bytes] [source ipv6-address] [timeout seconds] [vrf vrf-name]
Syntax Description
Defaults
For the default values, see the "Syntax Description" section for this command.
Command Modes
Any command mode
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
To determine the network connectivity to another device using IPv4 addressing, use the ping command.
This command does not require a license.
Examples
This example shows how to determine connectivity to another device using IPv6 addressing:
switch# ping6 2001:0DB8::200C:417A vrf managementRelated Commands
pop
To restore a saved command mode context, use the pop command.
pop [name]
Syntax Description
Defaults
The mode recent save context
Command Modes
Any command mode
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
You can save a command mode context using the push command.
This command does not require a license.
Examples
This example shows how to restore an unnamed command mode context:
switch# configure terminalswitch(config)# role name testswitch(config-role)# pushswitch(config-role)# endswitch# popswitch(config-role)#This example shows how to restore a named command mode context:
switch# configure terminalswitch(config)# line com1switch(config-com1)# push com1switch(config-com1)# endswitch# pop com1switch(config-com1)#Related Commands
power redundancy-mode
To configure the power supply redundancy mode, use the power redundancy-mode command. To revert to the default, use the no form of this command.
power redundancy-mode {combined | insrc-redundant | ps-redundant | redundant}
no power redundancy-mode {combined | insrc-redundant | ps-redundant | redundant}
Syntax Description
Defaults
ps-redundant
Command Modes
Global configuration
Supported User Rolesnetwork-admin
Command History
Usage Guidelines
You can use this command only in the default virtual device context (VDC).
You can configure the power supplies with the following modes:
•
•
•
•
This command does not require a license.
Examples
This example shows how to configure the power supply redundancy mode:
switch# configure terminalswitch(config)# power redundancy-mode redundantThis example shows how to revert to the default power supply redundancy mode:
switch# configure terminalswitch(config)# no power redundancy-mode redundantRelated Commands
purge module running-config
To remove the configuration for a missing module from the running configuration, use the purge module running-config command.
purge module slot running-config
Syntax Description
Defaults
None
Command Modes
Any command mode
Supported User Rolesnetwork-admin
Command History
Usage Guidelines
You can use this command only in the default virtual device context (VDC).
Use the show hardware command to verify which modules are missing.
This command does not require a license.
Examples
This example shows how to remove the configuration for a missing module from the running configuration:
switch# purge module 1 running-configRelated Commands
push
To save a command mode context, use the push command.
push [name]
Syntax Description
Defaults
None
Command Modes
Any command mode
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
You can save only one command mode context. You can use the pop command to restore a saved command mode context.
This command does not require a license.
Examples
This example shows how to save an unnamed command mode context:
switch# configure terminalswitch(config)# role name testswitch(config-role)# pushThis example shows how to save a named command mode context:
switch# configure terminalswitch(config)# line com1switch(config-com1)# push com1Related Commands
reload
To reload the entire Cisco NX-OS device, use the reload command.
reload [soft]
Syntax Description
soft
(Optional) Specifies to not reload the Connectivity Management Processor (CMP) on the active supervisor module.
Defaults
Reloads the entire device.
Command Modes
Any command mode
Supported User Rolesnetwork-admin
Command History
Usage Guidelines
You can use this command only in the default virtual device context (VDC).
The reload command uses the kickstart and system images referenced in the boot variables to reboot on the device. Use the show boot command to verify the contents of the kickstart and system boot variables. To set the boot variables to reference the correct images, use the boot kickstart and boot system commands.
If the boot variables do not reference images on the device, after you enter the reload command the device comes up at the loader> prompt. For information about recovering from the loader> prompt, see the Cisco Nexus 7000 Series NX-OS Troubleshooting Guide, Release 4.x.
Caution
Note
For information on upgrading and downgrading images on your Cisco NX-OS device, see the Cisco Nexus 7000 Series NX-OS Software Upgrade and Downgrade Guide, Release 4.2.
This command does not require a license.
Examples
This example shows how to reload the Cisco NX-OS device:
switch# copy running-config startup-config[########################################] 100%switch# reloadThis command will reboot the system. (y/n)? [n] yRelated Commands
reload cmp module
To reload the Connectivity Management Processor (CMP), use the reload cmp module command.
reload cmp module slot
Syntax Description
Defaults
None
Command Modes
Any command mode
Supported User Rolesnetwork-admin
Command History
Usage Guidelines
You can use this command only in the default virtual device context (VDC).
Use the show hardware command to determine the location of the CMPs on your device.
This command does not require a license.
Examples
This example shows how to reload the CMP on the supervisor module in slot 5:
switch# reload cmp module 5Related Commands
reload module
To reload a module in the device, use the reload module command.
reload module slot [force-dnld]
Syntax Description
Defaults
None
Command Modes
Any command mode
Supported User Rolesnetwork-admin
Command History
Usage Guidelines
You can use this command only in the default virtual device context (VDC).
Use the show hardware command to display information about the hardware on your device.
This command does not require a license.
Examples
This example shows how to reload a module:
switch# reload module 2Related Commands
rmdir
To remove a directory, use the rmdir command.
rmdir [filesystem:[//module/]]directory
Syntax Description
Defaults
Removes the directory from the current working directory.
Command Modes
Any command mode
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
This command does not require a license.
Examples
This example shows how to remove a directory:
switch# rmdir my_filesRelated Commands
cd
Changes the current working directory.
dir
Displays the directory contents.
pwd
Displays the name of the current working directory.
run-script
To run a command script file at the command-line interface (CLI), use the run-script command.
run-script [filesystem:[//module/]][directory/]filename
Syntax Description
Defaults
None
Command Modes
Any command mode
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
You must create the command file on a remote device and download it to the Cisco NX-OS device using the copy command.
This command does not require a license.
Examples
This example shows how to run a command script file:
switch# run-script script-fileRelated Commands
cd
Changes the current working directory.
copy
Copies files.
dir
Displays the directory contents.
pwd
Displays the name of the current working directory.
send
To send a message to the active user sessions, use the send command.
send [session line] text
Syntax Description
session line
(Optional) Specifies a user session.
text
Text string. The text string can be up to 80 alphanumeric characters and is case sensitive.
Defaults
Sends a message to all active user sessions.
Command Modes
Any command mode
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
You can use the show users command to display information about the active user sessions.
This command does not require a license.
Examples
This example shows how to send a message to all active user sessions on the device:
switch# send The system will reload in 15 minutes!The system will reload in 15 minutes!This example shows how to send a message to a specific user session:
switch# send session pts/39 You must log off the device.Related 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
Any command mode
Supported User Rolesnetwork-admin
vdc-adminCommand 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.
This command does not require a license.
Examples
This example shows how to enter the basic device setup script:
switch# setup---- Basic System Configuration Dialog VDC: 1 ----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
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 sessions
Syntax Description
Defaults
32 sessions
Command Modes
Line configuration
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
This command does not require a license.
Examples
This example shows how to configure the maximum number of concurrent virtual terminal sessions:
switch# configure terminalswitch(config)# line vtyswitch(config-line)# session-limit 48This example shows how to revert to the default maximum number of concurrent virtual terminal sessions:
switch# configure terminalswitch(config)# line vtyswitch(config-line)# no session-limit 48Related 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
Any command mode
Supported User Rolesnetwork-admin
vdc-admin
network-operator
vdc-operatorCommand History
Usage Guidelines
This command does not require a license.
Examples
This example shows how to display the MOTD banner:
switch# show banner motdUnauthorize access prohibited!Related Commands
show boot
To display the boot variable configuration, use the show boot command.
show boot [auto-copy | module [slot] | sup-1 | sup-2 | variables]
Syntax Description
Defaults
Displays all configured boot variables.
Command Modes
Any command mode
Supported User Rolesnetwork-admin
vdc-admin
network-operator
vdc-operatorCommand History
Usage Guidelines
Sup-1 refers to the top supervisor module in a chassis with two supervisor modules and sup-2 refers to the bottom supervisor module. For example, in the Cisco NX-OS 7010 device, sup-1 is in slot 5 and sup-2 is in slot 6.
This command does not require a license.
Examples
This example shows how to display all configured boot variables:
switch# show bootsup-1kickstart variable = bootflash:/n7000-s1-kickstart.4.0.2.binsystem variable = bootflash:/n7000-s1-dk9.4.0.2.binsup-2kickstart variable = bootflash:/n7000-s1-kickstart.4.0.2.binsystem variable = bootflash:/n7000-s1-dk9.4.0.2.binNo module boot variable setThis example shows how to display the boot variables for supervisor module 1:
switch# show boot sup-1sup-1kickstart variable = bootflash:/n7000-s1-kickstart.4.0.2.binsystem variable = bootflash:/n7000-s1-dk9.4.0.2.binThis example shows how to display the list of boot variable names (see Table 5 for field descriptions):
switch# show boot variablesssisystemasm-sfnkickstart
Related Commands
show cli alias
To display the command alias configuration, use the show cli alias command.
show cli alias [name alias-name]
Syntax Description
name alias-name
(Optional) Specifies the name of a command alias. The alias name is not case sensitive.
Defaults
Displays all configured command aliases variables.
Command Modes
Any command mode
Supported User Rolesnetwork-admin
vdc-admin
network-operator
vdc-operatorCommand History
Usage Guidelines
This command does not require a license.
Examples
This example shows how to display all configured command aliases:
switch# show cli aliasCLI alias commands==================ethint :interface ethernetshintbr :show interface brshintupbr :shintbr | include up | include ethernetalias :show cli aliascrun :copy running-config startup-configThis example shows how to display a specific command alias:
switch# show cli alias name ethintethint :interface ethernetRelated Commands
show cli history
To display the command history, use the show cli history command.
show cli history [lines] [unformatted]
Syntax Description
lines
(Optional) Number of line at the end of the command history lines to display.
unformatted
(Optional) Displays the commands without line numbers or time stamps.
Defaults
Displays the entire formatted history.
Command Modes
Any command mode
Supported User Rolesnetwork-admin
vdc-admin
network-operator
vdc-operatorCommand History
Usage Guidelines
This command does not require a license.
Examples
This example shows how to display all of the command history:
switch# 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:
switch# show cli history 1042 00:42:54 ip route 0.0.0.0/0 172.28.230.143 00:42:54 interface mgmt044 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 display unformatted command history:
switch# show cli history unformattedconfig tvrf context managementip route 0.0.0.0/0 172.28.230.1interface mgmt0ip address 172.28.231.193/23no shutdownaaa group server radius aaa-private-sguse-vrf managementtelnet server enablelogging server 172.28.254.254power redundancy-mode combinedshow cli history unformatedshow cli list
To list the Cisco NX-OS commands available in a command mode, use the show cli list command.
show cli list [combinations] [component-name] [recurse]
Syntax Description
Defaults
Displays the commands for the command mode in a single-line format.
Command Modes
Any command mode
Supported User Rolesnetwork-admin
vdc-admin
network-operator
vdc-operatorCommand History
Usage Guidelines
To exit a long listing generated by this command, type Ctrl-C.
This command does not require a license.
Examples
This example shows how to display all commands available in EXEC mode:
switch# show cli listMODE execshow system internal modlock-infoshow system internal usd errorsshow system internal usd isrshow system internal usd mtsshow system internal usd timesliceshow system internal usd wdshow system internal aaa event-history errorsshow system internal aaa event-history msgs...^CThis example shows how to display all commands related to the address resolution protocol (ARP) available in configuration command mode:
switch(config)# show cli list arpMODE configureno ip arp timeoutno logging level arp <uint:0-7>no ip arp event-history packet size <small|medium|large|disabled>no ip arp event-history event size <small|medium|large|disabled>no ip arp event-history ha size <small|medium|large|disabled>no ip arp event-history errors size <small|medium|large|disabled>no ip arp event-history lcache size <small|medium|large|disabled>no ip arp event-history lcache-errors size <small|medium|large|disabled>no ip arp event-history client-event size <small|medium|large|disabled>no ip arp event-history client-errors size <small|medium|large|disabled>no ip arp event-history snmp size <small|medium|large|disabled>no ip arp event-history cli size <small|medium|large|disabled>logging level arp <uint:0-7>ip arp event-history packet size <small|medium|large|disabled>ip arp event-history event size <small|medium|large|disabled>ip arp event-history ha size <small|medium|large|disabled>ip arp event-history errors size <small|medium|large|disabled>ip arp event-history lcache size <small|medium|large|disabled>ip arp event-history lcache-errors size <small|medium|large|disabled>ip arp event-history client-event size <small|medium|large|disabled>ip arp event-history client-errors size <small|medium|large|disabled>ip arp event-history snmp size <small|medium|large|disabled>ip arp event-history cli size <small|medium|large|disabled>ip arp timeout <int:60-28800>This example shows how to display commands related to Open Shortest Path First (OSPF) available in the loopback interface command mode:
switch(config)# interface loopback 0switch(config-if)# show cli list ospfMODE if-loopbackno ip ospf network point-to-pointno ip ospf networkRelated Commands
show cli syntax
Displays the Cisco NX-OS command syntax available in a command mode.
show cli syntax
To display the Cisco NX-OS command syntax available in a command mode, use the show cli syntax command.
show cli syntax [component-name] [long] [mode mode-name] [recurse]
Syntax Description
Defaults
Displays the command syntax for the command mode in a single-line format.
Command Modes
Any command mode
Supported User Rolesnetwork-admin
vdc-admin
network-operator
vdc-operatorCommand History
Usage Guidelines
This command does not require a license.
Examples
This example shows how to display the command syntax for commands available in the role configuration command mode in the default format:
switch(config-role)# show cli syntaxMODE role(0) description <line> | no description(1) description <line> | no description(2) rule <number> { <action> } { { <permission> [ <featuretype> <name> ] } | { command <cmd_line> } } | no rule <number>(3) rule <number> { <action> } { { <permission> [ <featuretype> <name> ] } | { command <cmd_line> } } | no rule <number>(4) [ no ] vlan policy deny(5) [ no ] interface policy deny(6) [ no ] vrf policy denyThis example shows how to display the command syntax for commands available in the role configuration command mode in long format:
switch(config-role)# show cli syntax longMODE role***(0) description <line>| no description***(1) description <line>| no description***(2) rule <number> { <action> }{ { <permission> [ <featuretype> <name> ]}| { command <cmd_line> }}| no rule <number>***(3) rule <number> { <action> }{ { <permission> [ <featuretype> <name> ]}| { command <cmd_line> }}| no rule <number>***(4) [no] vlan policy deny***(5) [no] interface policy deny***(6) [no] vrf policy denyThis example shows how to display the command syntax for commands and subcommands available in the role configuration command mode in the default format:
switch(config-role)# show cli syntax long recurseMODE role***(0) description <line>| no description***(1) description <line>| no description***(2) rule <number> { <action> }{ { <permission> [ <featuretype> <name> ]}| { command <cmd_line> }}| no rule <number>***(3) rule <number> { <action> }{ { <permission> [ <featuretype> <name> ]}| { command <cmd_line> }}| no rule <number>***(4) [no] vlan policy deny***(5) [no] interface policy deny***(6) [no] vrf policy denyMODE vlan***(7) [no] permit vlan <vlan-mrange>MODE interface***(8) [no] permit interface <if0>MODE vrf***(9) [no] permit vrf <vrf-name>show cli variables
To display the configuration of the CLI variables, use the show cli variables command.
show cli variables
Syntax Description
This command has no arguments or keywords.
Defaults
None
Command Modes
Any command mode
Supported User Rolesnetwork-admin
vdc-admin
network-operator
vdc-operatorCommand History
Usage Guidelines
This command does not require a license.
Examples
This example shows how to display the CLI variables:
switch# show cli variablesVSH Variable List-----------------TIMESTAMP="2008-06-13-01.14.09"testinterface="ethernet 2/3"Related Commands
show clock
To display the clock configuration, use the show clock command.
show clock [detail]
Syntax Description
Defaults
Displays all configured command aliases variables.
Command Modes
Any command mode
Supported User Rolesnetwork-admin
vdc-admin
network-operator
vdc-operatorCommand History
Usage Guidelines
This command does not require a license.
Examples
This example shows how to display the clock setting:
switch# show clockFri Jun 13 02:19:20 PDT 2008This example shows how to display the clock setting and the summer-time (daylight saving time) configuration:
switch# show clock detailFri Jun 13 02:19:02 PDT 2008summer-time configuration:--------------------------timezone name: PDTstarts : 1 Sunday March at 02:00 hoursEnds : 1 Sunday November at 02:00 hoursMinute offset: 60Related Commands
clock set
Sets the clock time.
clock summer-time
Configures the summer-time (daylight saving time) offset.
show copyright
To display the Cisco NX-OS software copyright information, use the show copyright command.
show copyright
Syntax Description
This command has no arguments or keywords.
Defaults
None
Command Modes
Any command mode
Supported User Rolesnetwork-admin
vdc-admin
network-operator
vdc-operatorCommand History
Usage Guidelines
This command does not require a license.
Examples
This example shows how to display the Cisco NX-OS copyright information:
switch# show copyrightCisco Nexus Operating System (NX-OS) SoftwareTAC support: http://www.cisco.com/tacCopyright (c) 2002-2008, Cisco Systems, Inc. All rights reserved.The copyrights to certain works contained in this software areowned by other third parties and used and distributed underlicense. Certain components of this software are licensed underthe GNU General Public License (GPL) version 2.0 or the GNULesser General Public License (LGPL) Version 2.1. A copy of eachsuch license is available athttp://www.opensource.org/licenses/gpl-2.0.php andhttp://www.opensource.org/licenses/lgpl-2.1.phpshow debug logfile
To display the contents of the debug logfile, use the show debug logfile command.
show debug logfile filename
Syntax Description
Defaults
None
Command Modes
Any command mode
Supported User Rolesnetwork-admin
vdc-admin
network-operator
vdc-operatorCommand History
Usage Guidelines
The log files are located in the log: file system.
This command does not require a license.
Examples
This example shows how to display the contents of the debug log file:
switch# show debug logfile syslogd_debugsDropping the mts messageDropping MTS notif(not a reject) reference, from: 0x00000601/22000, To: 0x00000601/32, Opcode: 8888, MsgID: 38388549, rr_token: 0Jun 9 23:49:58 2008select_and_process_log_messages :: Successful select, count = 1, Activity on: 9Jun 9 23:49:58 2008 Message from UNIX socket: #9Jun 9 23:49:58 2008 printchopped :: Message - <15>Jun 9 23:49:58 aaad: Semaphore lock success, Length - 52, FD - 9Jun 9 23:49:58 2008 printchopped :: Calling copy_message(do loop), message - <15>Jun 9 23:49:58 aaad: Semaphore lock success...Related Commands...
show file
To display the contents of a file on the local memory, use the show file command.
show file [filesystem:][//directory/]filename
Syntax Description
Defaults
None
Command Modes
Any command mode
network-admin
vdc-admin
network-operator
vdc-operatorCommand History
Usage Guidelines
This command does not require a license.
Examples
This example shows how to display the contents of a file:
switch# show file scriptfileconfigure terminalinterface $(testinterface)no shutdownendshow interface $(testinterface)Related Commands
cd
Changes the current working directory.
dir
Displays the directory contents.
pwd
Displays the name of the current working directory.
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
Any command mode
Supported User Rolesnetwork-admin
vdc-admin
network-operator
vdc-operatorCommand History
Usage Guidelines
The show switchname command also displays the device hostname.
This command does not require a license.
Examples
This example shows how to display the hostname for the device:
switch# show hostnameswitchRelated Commands
hostname
Configures the hostname for the device.
show switchname
Displays the hostname.
show incompatibility system
To display the configuration incompatibilities between the running system image and an earlier system image prior to downgrading the Cisco NX-OS software, use the show incompatibility system command.
show incompatibility system {bootflash: | slot0: | volatile:}filename
Syntax Description
Defaults
None
Command Modes
Any command mode
Supported User Rolesnetwork-admin
vdc-admin
network-operator
vdc-operatorCommand History
Usage Guidelines
You can use this command only in the default virtual device context (VDC).
This command does not require a license.
Examples
This example shows how to display the configuration incompatibilities:
switch# show incompatibility system bootflash:old_image.binThe following configurations on active are incompatible with the system image1) Service : eth_port_channel , Capability : CAP_FEATURE_AUTO_CREATED_PORT_CHANNELDescription : active mode port channels, auto create enabled ports or auto created port-channels are presentCapability requirement : STRICTDisable command : 1.Convert Active mode port channels to On mode port channels (no channelmode active).2.Disable autocreate on interfaces (no channel-group auto).3.Convert autocreated port channels to be persistent (port-channel 1 persistent).show install all
To display information related to the operation of the install all command, use the show install all command.
show install all {failed-standby | failure-reason | impact [kickstart | system] | status}
Syntax Description
Defaults
None
Command Modes
Any command mode
Supported User Rolesnetwork-admin
Command History
Usage Guidelines
You can use this command only in the default virtual device context (VDC).
This command does not require a license.
Examples
This example shows how to display the installation failure reason:
switch# show install all failure-reasonNo install all failure-reasonThis example shows how to display the impact of installing new images:
switch# show install all impactVerifying image bootflash:/n7000-s1-kickstart.4.0.2.bin for boot variable "kickstart".[####################] 100% -- SUCCESSVerifying image bootflash:/n7000-s1-dk9.4.0.2.bin for boot variable "system".[####################] 100% -- SUCCESSVerifying image type.[####################] 100% -- SUCCESSExtracting "lc1n7k" version from image bootflash:/n7000-s1-dk9.4.0.2.bin.[####################] 100% -- SUCCESSExtracting "bios" version from image bootflash:/n7000-s1-dk9.4.0.2.bin.[####################] 100% -- SUCCESSExtracting "system" version from image bootflash:/n7000-s1-dk9.4.0.2.bin.[####################] 100% -- SUCCESSExtracting "kickstart" version from image bootflash:/n7000-s1-kickstart.4.0.2.gbin.S22.[####################] 100% -- SUCCESSCompatibility check is done:Module bootable Impact Install-type Reason------ -------- -------------- ------------ ------2 yes non-disruptive none6 yes non-disruptive noneImages will be upgraded according to following table:Module Image Running-Version(pri:alt) New-Version Upg-Required------ ---------- ---------------------------------------- -------------------- ------------2 lc1n7k 4.0(2) 4.0(2) no2 bios v1.10.5(02/27/08): v1.10.5(02/27/08) v1.10.5(02/27/08) no6 system 4.0(2) 4.0(2) no6 kickstart 4.0(2) 4.0(2) no6 bios v3.17.0(03/23/08): v3.17.0(03/23/08) v3.17.0(03/23/08) noThis example shows how to display the status of a software installation:
switch# show install all impactThere is an on-going installation...Enter Ctrl-C to go back to the prompt.Verifying image bootflash:/n7000-s1-kickstart.4.0.2.bin-- SUCCESSVerifying image bootflash:/n7000-s1-dk9.4.0.2.bin-- SUCCESSExtracting "system" version from image bootflash:/n7000-s1-dk9.4.0.2.bin.-- SUCCESSExtracting "kickstart" version from image bootflash:/n7000-s1-kickstart.4.0.2.bin.-- SUCCESSExtracting "loader" version from image bootflash:/n7000-s1-kickstart.4.0.2.bin.-- SUCCESSRelated Commands
show license
To display license information, use the show license command.
show license [brief | file filename]
Syntax Description
brief
(Optional) Displays a list of license files installed on a device.
file filename
(Optional) Displays information for a specific license file.
Defaults
Displays information about the installed licenses.
Command Modes
Any command mode
Supported User Rolesnetwork-admin
vdc-admin
network-operator
vdc-operatorCommand History
Usage Guidelines
This command does not require a license.
Examples
This example shows how to display a specific license installed on a device:
switch# show license file Enterprise.licEnterprise.lic:SERVER this_host ANYVENDOR ciscoINCREMENT LAN_ENTERPRISE_SERVICES_PKG cisco 1.0 permanent uncounted \VENDOR_STRING=<LIC_SOURCE>MDS_SWIFT</LIC_SOURCE><SKU>N7K-LAN1K9=</SKU> \HOSTID=VDH=TBC10412106 \NOTICE="<LicFileID>20071025133322456</LicFileID><LicLineID>1</LicLineID>\<PAK></PAK>" SIGN=0CC6E2245FBEThis example shows how to display a list of license files installed on a device:
switch# show license briefEnterprise.lic:This example shows how to display all licenses installed on a device:
switch# show licenseEnterprise.lic:SERVER this_host ANYVENDOR ciscoINCREMENT LAN_ENTERPRISE_SERVICES_PKG cisco 1.0 permanent uncounted \VENDOR_STRING=<LIC_SOURCE>MDS_SWIFT</LIC_SOURCE><SKU>N7K-LAN1K9=</SKU> \HOSTID=VDH=TBC10412106 \NOTICE="<LicFileID>20071025133322456</LicFileID><LicLineID>1</LicLineID>\<PAK></PAK>" SIGN=0CC6E2245FBEshow license host-id
To display the serial number for the chassis to use for licensing, use the show license host-id command.
show license host-id
Syntax Description
This command has no arguments or keywords.
Defaults
None
Command Modes
Any command mode
Supported User Rolesnetwork-admin
vdc-admin
network-operator
vdc-operatorCommand History
Usage Guidelines
The serial number is the entire string that appears after the colon (:).
This command does not require a license.
Examples
This example shows how to display the host ID, required to request node-locked licenses:
switch# show license host-idLicense hostid:VDH=4C0AF664show license usage
To display license usage information, use the show license usage command.
show license usage [vdc-all] [LAN_ADVANCED_SERVICES_PKG | LAN_ENTERPRISE_SERVICES_PKG]
Syntax Description
Defaults
Displays license usage for the local VDC.
Command Modes
Any command mode
Supported User Rolesnetwork-admin
vdc-admin
network-operator
vdc-operatorCommand History
Usage Guidelines
This command does not require a license.
Examples
This example shows how to display information about the current license usage for the local VDC:
switch# show license usageFeature Ins Lic Status Expiry Date CommentsCount--------------------------------------------------------------------------------LAN_ADVANCED_SERVICES_PKG No - In use Grace 116D 20HLAN_ENTERPRISE_SERVICES_PKG No - In use Grace 116D 20H--------------------------------------------------------------------------------Table 6 describes the significant fields shown in the display.
This example shows how to display a list of features in use for a specific license:
switch# show license usage LAN_ENTERPRISE_SERVICES_PKGApplication-----------bgpospf-----------This example shows how to display a list of features in use for a specific license for all VDCs:
switch# show license usage vdc-all LAN_ENTERPRISE_SERVICES_PKGApplication-----------bgpospfbgp@2ospf@2-----------
Note
show line
To display COM1 and console port configuration information, use the show line command.
show line [com1 | console]
Syntax Description
com1
(Optional) Displays only information about the COM1 port configuration.
console
(Optional) Displays only information about the console port configuration.
Defaults
Displays information about the COM1 port and the console port configuration.
Command Modes
Any command mode
Supported User Rolesnetwork-admin
vdc-admin
network-operator
vdc-operatorCommand History
Usage Guidelines
This command does not require a license.
Examples
This example shows how to display information about the COM1 port and the console port configuration information:
switch# show lineline Console:Speed: 115200 baudDatabits: 8 bits per byteStopbits: 1 bit(s)Parity: noneModem In: DisableModem Init-String -default : ATE0Q1&D2&C1S0=1\015Statistics: tx:26197 rx:805 Register Bits:RTS|CTS|DTR|DSR|CD|RIline Aux:Speed: 9600 baudDatabits: 8 bits per byteStopbits: 1 bit(s)Parity: noneModem In: EnableModem Init-String -default : ATE0Q1&D2&C1S0=1\015Hardware Flowcontrol: ONStatistics: +ò Çêe+ Register Bits:RTS|CTS|DTR|DSR|CD|RIThis example shows how to display only the information about the console port configuration:
switch# show line consoleline Console:Speed: 115200 baudDatabits: 8 bits per byteStopbits: 1 bit(s)Parity: noneModem In: DisableModem Init-String -default : ATE0Q1&D2&C1S0=1\015Statistics: tx:26197 rx:805 Register Bits:RTS|CTS|DTR|DSR|CD|RIRelated Commands
line com1
Enters the COM1 port configuration mode.
line console
Enters the console port configuration mode.
show running-config
To display the running configuration, use the show running-config command.
show running-config [all | exclude component-list]
Syntax Description
Defaults
Displays only the configured information.
Command Modes
Any command mode
Supported User Rolesnetwork-admin
vdc-admin
network-operator
vdc-operatorCommand History
Usage Guidelines
This command does not require a license.
Examples
This example shows how to display the changes that you have made to the running configuration:
switch# show running-configThis example shows how to display the entire running configuration, including the default values:
switch# show running-config allThis example shows how to exclude the ACL manager and control plane policing (CoPP) components from the command output:
switch# show running-config exclude aclmgr coppRelated Commands
show running-config diff
To display the differences between the running configuration and the startup configuration, use the show running-config diff command.
show running-config diff
Syntax Description
This command has no arguments or keywords.
Defaults
None
Command Modes
Any command mode
Supported User Rolesnetwork-admin
vdc-admin
network-operator
vdc-operatorCommand History
Usage Guidelines
Table 7 describes the notations used in the command output.
This command does not require a license.
Examples
This example shows how to display the difference between the running configuration and the startup configuration:
switch# show running-config diff*** Startup-config--- Running-config****************** 48,76 ****--- 48,83 ----username foo role network-adminusername x password 5 ! role network-operatorusername user-op password 5 $1$ykZCz5Y2$npXjKVQhpa4U7EtwMauQG1 role network-operatortelnet server enablessh key rsa 768 force+ ssh key dsa forceip domain-lookupip host 172.28.231.193 172.28.231.193kernel core target 0.0.0.0...Related Commands
show startup-config
To display the startup configuration, use the show startup-config command.
show startup-config [exclude component-list]
Syntax Description
Defaults
None
Command Modes
Any command mode
Supported User Rolesnetwork-admin
vdc-admin
network-operator
vdc-operatorCommand History
Usage Guidelines
This command does not require a license.
Examples
This example shows how to display the startup configuration:
switch# show startup-configThis example shows how to exclude the ACL manager and control place policing (CoPP) components from the command output:
switch# show startupt-config exclude aclmgr coppRelated Commands
show switchname
To display the hostname for the device, use the show switchname command.
show switchname
Syntax Description
This command has no arguments or keywords.
Defaults
None
Command Modes
Any command mode
Supported User Rolesnetwork-admin
vdc-admin
network-operator
vdc-operatorCommand History
Usage Guidelines
The show hostname command also displays the device hostname.
This command does not require a license.
Examples
This example shows how to display the hostname for the device:
switch# show switchnameswitchRelated Commands
switchname
Configures the hostname for the device.
show hostname
Displays the hostname.
show tech-support
To display information for Cisco technical support, use the show tech-support command.
show tech-support [brief | commands | feature]
Syntax Description
Defaults
Displays information for all features.
Command Modes
Any command mode
Supported User Rolesnetwork-admin
vdc-admin
network-operator
vdc-operatorCommand History
Usage Guidelines
The output from the show tech-support command is very long. To better manage this output, you can redirect the output to a file (for example show tech-support > bootflash:filename).
This command does not require a license.
Examples
This example shows how to display technical support information and redirect it to a file:
switch# show tech-support > bootflash:tsupport_fileThis example shows how to display the brief technical support information for the device:
switch# show tech-support briefThis example shows how to display the technical support information for a feature:
switch# show tech-support aaaThis example shows how to display the commands to generate the technical support information:
switch# show tech-support commandsshow 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
Any command mode
Supported User Rolesnetwork-admin
vdc-admin
network-operator
vdc-operatorCommand History
Usage Guidelines
This command does not require a license.
Examples
This example shows how to display information about the terminal configuration for a session:
switch# show terminalTTY: /dev/pts/41 Type: "ansi"Length: 31 lines, Width: 80 columnsSession Timeout: NoneRelated Commands
show version
To display information about the software version, use the show version command.
show version [build-info [all] | epld filename | fan fan-number epld | image filename | module slot [epld] | xbar xbar-number epld]
Syntax Description
Defaults
Displays software version information for the running kickstart and system images.
Command Modes
Any command mode
Supported User Rolesnetwork-admin
vdc-admin
network-operator
vdc-operatorCommand History
Usage Guidelines
This command does not require a license.
Examples
This example shows how to display the version information for the kickstart and system image running on the device:
switch# show versionCisco Nexus Operating System (NX-OS) SoftwareTAC support: http://www.cisco.com/tacCopyright (c) 2002-2008, Cisco Systems, Inc. All rights reserved.The copyrights to certain works contained in this software areowned by other third parties and used and distributed underlicense. Certain components of this software are licensed underthe GNU General Public License (GPL) version 2.0 or the GNULesser General Public License (LGPL) Version 2.1. A copy of eachsuch license is available athttp://www.opensource.org/licenses/gpl-2.0.php andhttp://www.opensource.org/licenses/lgpl-2.1.phpSoftwareBIOS: version 3.17.0loader: version N/Akickstart: version 4.0(1a) [gdb]system: version 4.0(1a) [gdb]BIOS compile time: 03/23/08kickstart image file is: bootflash:/n7000-s1-kickstart.4.0.1a.binkickstart compile time: 5/8/2008 13:00:00 [05/20/2008 07:52:26]system image file is: bootflash:/n7000-s1-dk9.4.0.1a.binsystem compile time: 5/8/2008 13:00:00 [05/20/2008 08:35:00]Hardwarecisco Nexus7000 C7010 (10 Slot) Chassis ("Supervisor module-1X")Intel(R) Xeon(R) CPU with 2063436 kB of memory.Processor Board ID JAB10380101Device name: switchbootflash: 1023120 kBslot0: 0 kB (expansion flash)Kernel uptime is 1 day(s), 3 hour(s), 48 minute(s), 20 second(s)Last reset at 761445 usecs after Wed May 21 11:46:23 2008Reason: Reset Requested by CLI command reloadSystem version: 4.0(1.51)Service:pluginCore Plugin, Ethernet PluginCMP (Module 6) no responseCMP (Module 5) no responseThis example shows how to display the version information for an image file:
switch# show version image bootflash:old_imageimage name: old_imagebios: v3.15.0(03/04/08)system: version 4.0(1a)compiled: 4/3/2008 8:00:00 [04/18/2008 08:26:29]This example shows how to display the version information for an I/O module:
switch# show version module 2ModNo Image Type SW Version SW Interim Version BIOS Version2 SLC 4.0(1a) 4.0(1a) 1.10.5This example shows how to display the version information for the EPLD images on an I/O module:
switch# show version module 2 epldEPLD Device Version---------------------------------------Power Manager 2.9IO 1.17Forwarding Engine 1.4This example shows how to display the version information for the EPLD images on a fabric module:
switch# show version xbar 1 epldEPLD Device Version---------------------------------------Power Manager 2.4sleep
To cause the command-line interface (CLI) to pause before displaying the prompt, use the sleep command.
sleep seconds
Syntax Description
Defaults
None
Command Modes
Any command mode
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
You can use this command in command scripts to delay the execution of the script.
This command does not require a license.
Examples
This example shows how to cause the CLI to pause before displaying the prompt:
switch# sleep 5slot
To issue commands to an I/O module from the supervisor module session, use the slot command.
slot slot-number {command-string | quoted "command-string"}
Syntax Description
Defaults
None
Command Modes
Any command mode.
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
You can use the slot command instead of starting a session on the I/O module with the attach command.
By default, the keyword and arguments in the command-string argument are space-separated. To send more than one command to a module, separate the commands with a space character, a semicolon character (;), and a space character.
The quoted keyword indicates that the command string begins and ends with double quotation marks (" "). Use this keyword when you want to redirect the module command output to a filtering utility, such as diff, that is only supported on the supervisor module session.
This command does not require a license.
Examples
This example shows how to send commands to an I/O module from the supervisor module session:
switch# slot 1 show system uptime ; show versionSystem start time: Tue Aug 4 15:09:49 2009System uptime: 6 days, 17 hours, 50 minutes, 55 secondsKernel uptime: 6 days, 17 hours, 53 minutes, 7 secondsRAM 516692 kBlc1SoftwareBIOS: version 1.10.6system: version 4.2(1) [build 4.2(1)]BIOS compile time: 11/04/08system compile time: 7/3/2009 2:00:00 [08/02/2009 07:15:39]Hardwarebootflash: 0 blocks (block size 512b)uptime is 6 days 17 hours 53 minute(s) 7 second(s)This example shows how to send a quoted command to an I/O module from the supervisor module session:
switch# slot 1 quoted "show system uptime" | diffswitch# slot 1 quoted "show system uptime" | diff -c*** /volatile/vsh_diff_1_admin_4849_slot__quoted_show_system_uptime.old Tue Aug 11 09:16:14 2009--- - Tue Aug 11 09:16:14 2009****************** 1,3 ****System start time: Tue Aug 4 15:09:49 2009! System uptime: 6 days, 18 hours, 6 minutes, 13 seconds! Kernel uptime: 6 days, 18 hours, 8 minutes, 25 seconds--- 1,3 ----System start time: Tue Aug 4 15:09:49 2009! System uptime: 6 days, 18 hours, 6 minutes, 36 seconds! Kernel uptime: 6 days, 18 hours, 8 minutes, 48 secondsRelated 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
COM1 port configuration
console port configurationSupported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
You can use this command only in the default virtual device context (VDC).
You can configure the console and COM1 ports only from a session on the console port.
This command does not require a license.
Examples
This example shows how to configure the number of stop bits for the COM1 port:
switch# configure terminalswitch(config)# line com1switch(config-com1)# stopbits 2This example shows how to configure the number of stop bits for the console port:
switch# configure terminalswitch(config)# line consoleswitch(config-console)# stopbits 2This example shows how to revert to the default number of stop bits for the COM1 port:
switch# configure terminalswitch(config)# line com1switch(config-com1)# no stopbits 2This example shows how to revert to the default number of stop bits for the console port:
switch# configure terminalswitch(config)# line consoleswitch(config-console)# no stopbits 2Related Commands
show line
Displays information about the COM1 port and console port configuration.
switchname
To configure the hostname for the device, use the switchname command. To revert to the default, use the no form of this command.
switchname name
no switchname
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.
Defaults
switch
Command Modes
Global configuration
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
The Cisco NX-OS software uses the hostname in command-line interface (CLI) prompts and in default configuration filenames.
The switchname command performs the same function as the hostname command.
This command does not require a license.
Examples
This example shows how to configure the device hostname:
switch# configure terminalswitch(config)# switchname Engineering2Engineering2(config)#This example shows how to revert to the default device hostname:
Engineering2# configure terminalEngineering2(config)# no switchnameswitch(config)#Related Commands
hostname
Configures the device hostname.
show switchname
Displays the device hostname.
tail
To display the last lines of a file, use the tail command.
tail [filesystem:[//module/]][directory/]filename lines]
Syntax Description
Defaults
10 lines
Command Modes
Any command mode
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
This command does not require a license.
Examples
This example shows how to display the last 10 lines of a file:
switch# tail bootflash:startup.cfgip arp inspection filter marp vlan 9ip dhcp snooping vlan 13ip arp inspection vlan 13ip dhcp snoopingip arp inspection validate src-mac dst-mac ipip source binding 10.3.2.2 0f00.60b3.2333 vlan 13 interface Ethernet2/46ip source binding 10.2.2.2 0060.3454.4555 vlan 100 interface Ethernet2/10logging level dhcp_snoop 6logging level eth_port_channel 6This example shows how to display the last 20 lines of a file:
switch# tail bootflash:startup.cfg 20area 99 virtual-link 1.2.3.4router rip Enterpriserouter rip fooaddress-family ipv4 unicastrouter bgp 33.33event manager applet sdtestmonitor session 1monitor session 2ip dhcp snooping vlan 1ip arp inspection vlan 1ip arp inspection filter marp vlan 9ip dhcp snooping vlan 13ip arp inspection vlan 13ip dhcp snoopingip arp inspection validate src-mac dst-mac ipip source binding 10.3.2.2 0f00.60b3.2333 vlan 13 interface Ethernet2/46ip source binding 10.2.2.2 0060.3454.4555 vlan 100 interface Ethernet2/10logging level dhcp_snoop 6logging level eth_port_channel 6Related Commands
cd
Changes the current working directory.
copy
Copies files.
dir
Displays the directory contents.
pwd
Displays the name of the current working directory.
tar append
To append files to a tar archive file, use the tar append command.
tar append {bootflash: | volatile:}archive-filename [absolute] [remove] [verbose] filename-list
Syntax Description
Defaults
Adds the tar.gz extension to the archive filename if you do not enter an extension.
Command Modes
Any command mode
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
You must create an archive file using the tar create command before you can append files to it.
This command does not require a license.
Examples
This example shows how to append two files to the end of an archive file:
switch# tar append bootflash:testarchive.tar.gz newfile1 newfile2This example shows how to append two files to the end of an archive file and display the filenames as they are appended:
switch# tar append bootflash:testarchive.tar.gz verbose newfile1 newfile2/bootflash/newfile1/bootflash/newfile2This example shows how to append two files to the end of an archive file and remove those files from the device:
switch# tar append bootflash:testarchive.tar.gz remove newfile1 newfile2Related Commands
tar create
Creates an archive file.
tar extract
Extracts the files from an archive file.
tar list
Displays the contents of an archive file.
tar create
To create a tar archive file, use the tar create command.
tar create {bootflash: | volatile:}archive-filename [absolute] [bz2-compress] [gz-compress] [remove] [uncompressed] [verbose] filename-list
Syntax Description
Defaults
gz-compress
Command Modes
Any command mode
Supported User Rolesnetwork-admin
vdc-adminCommand History
4.1(2)
This command was introduced.
4.2(1)
Added the absolute, bz2-compress, and uncompressed optional keywords.
Changed the compress keyword to gz-compress.
Usage Guidelines
This command does not require a license.
Examples
This example shows how to create a tar archive file and add two files:
switch# tar create bootflash:testarchive.tar.gz newfile1 newfile2This example shows how to create a tar archive file, two files to the end of an archive file, and display the filenames as they are appended:
switch# tar create bootflash:testarchive.tar.gz verbose newfile1 newfile2/bootflash/newfile1/bootflash/newfile2This example shows how to create a tar archive file, add two files, and remove those files from the device:
switch# tar create bootflash:testarchive.tar.gz remove newfile1 newfile2Related Commands
tar append
Appends files to the end of an archive file.
tar extract
Extracts the files from an archive file.
tar list
Displays the contents of an archive file.
tar extract
To extract files from a tar archive file, use the tar extract command.
tar extract {bootflash: | volatile:}archive-filename [keep-old] [screen] [to {bootflash: | volatile:}filename] [verbose]
Syntax Description
Defaults
Adds the tar.gz extension to the archive filename if you do not enter an extension.
Command Modes
Any command mode
Supported User Rolesnetwork-admin
vdc-adminCommand History
4.1(2)
This command was introduced.
4.2(1)
Added the keep-old and to optional keywords.
Usage Guidelines
You must create an archive file using the tar create command before you can append files to it.
This command does not require a license.
Examples
This example shows how to extract files from an archive file:
switch# tar extract bootflash:testarchive.tar.gzThis example shows how to extract files from an archive file and display the filenames as they are extracted:
switch# tar append bootflash:testarchive.tar.gz verbose newfile1 newfile2/bootflash/newfile1/bootflash/newfile2Related Commands
tar append
Appends files to the end of an archive file.
tar create
Creates an archive file.
tar list
Displays the contents of an archive file.
tar list
To list the files in a tar archive file, use the tar list command.
tar list {bootflash: | volatile:}archive-filename
Syntax Description
Defaults
Adds the tar.gz extension to the archive filename if you do not enter an extension.
Command Modes
Any command mode
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
You must create an archive file using the tar create command before you can list files.
This command does not require a license.
Examples
This example shows how to list files in an archive file:
switch# tar list bootflash:testfile.tar.gzbootflash/newfile2bootflash/newfile1Related Commands
tar append
Appends files to the end of an archive file.
tar create
Creates an archive file.
tar extract
Extracts the files from an archive file.
terminal alias
To display and define command aliases for the user session, use the terminal alias command. To remove the alias definition, use the no form of this command.
terminal alias [persist] [alias-name alias-definition]
no terminal alias [persist] [alias-name alias-definition]
Syntax Description
persist
(Optional) Makes the setting persistent for the current and future sessions for the current user.
alias-name
(Optional) Name of the alias.
alias-definition
Alias definition.
Defaults
Displays the command aliases available to the user session.
Command Modes
Any command mode
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
Aliases that you define with the terminal alias command are only available to the current user. Other user cannot use these command aliases. To create aliases that other users can access, use the cli alias name command.
This command does not require a license.
Examples
This example shows how to define a command alias only for the current user session:
switch# terminal alias shint show interface briefThis example shows how to define a command alias to persist across session for the current user:
switch# terminal alias persist shver show versionThis example shows how to display the command aliases available to the current user session:
switch# terminal aliasCLI alias commands==================shint :show interface brief------------------alias :show cli aliasThis example shows how to remove a temporary command alias for the user session:
switch# no terminal alias shintRelated Commands
terminal color
To change the colors used when displaying the commands and output on the command-line interface (CLI) for the user session, use the terminal color command. To revert to the default, use the no form of this command.
terminal color [evening] [persist]
no terminal color [evening] [persist]
Syntax Description
evening
(Optional) Not supported.
persist
(Optional) Makes the setting persistent for the current and future sessions for the current user.
Defaults
All CLI prompts, commands, and command output display in colors defined by the terminal emulator.
Command Modes
Any command mode
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
The terminal color command changes the CLI colors as follows:
•
•
•
•
The terminal colors setting applies only to the current user session. Use the persist keyword to change the setting for the current and future session for the current user.
This command does not require a license.
Examples
This example shows how to change the terminal display colors for the current user session:
switch# terminal colorThis example shows how to change the terminal display colors for the current and future sessions for the current user:
switch# terminal color persistThis example shows how to revert to the default for the current user session:
switch# no terminal colorThis example shows how to revert to the default for the current and future sessions for the current user:
switch# no terminal color persistterminal dont-ask
To disable confirmation prompts on the command-line interface (CLI), use the terminal dont-ask command. To revert to the default, use the no form of this command.
terminal dont-ask [persist]
no terminal dont-ask [persist]
Syntax Description
persist
(Optional) Makes the setting persistent for the current and future sessions for the current user.
Defaults
Confirmation prompts enabled.
Command Modes
Any command mode
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
The terminal confirmation prompt setting applies only to the current user session. Use the persist keyword to change the setting for the current and future session for the current user.
This command does not require a license.
Examples
This example shows how to disable the CLI confirmation prompts for the current user session:
switch# terminal dont-askThis example shows how to disable the CLI confirmation prompts for the current and future sessions for the current user:
switch# terminal dont-ask persistThis example shows how to enable the CLI confirmation prompts for the current user session:
switch# no terminal dont-askThis example shows how to enable the CLI confirmation prompts for the current and future sessions for the current user:
switch# no terminal dont-ask persistterminal edit-mode vi
To enable vi editing of recalled commands, use the terminal edit-mode command. To revert to the default, use the no form of this command.
terminal edit-mode vi [persist]
no terminal edit-mode vi [persist]
Syntax Description
persist
(Optional) Makes the setting persistent for the current and future sessions for the current user.
Defaults
emacs
Command Modes
Any command mode
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
The edit mode setting applies only to the current user session. Use the persist keyword to change the setting for the current and future session for the current user.
This command does not require a license.
Examples
This example shows how to change the edit mode for recalled commands to vi for the current user session:
switch# terminal edit-mode viThis example shows how to change the edit mode for recalled commands to vi for the current and future session for the current user:
switch# terminal edit-mode vi persistThis example shows how to revert the edit mode for recalled command to emacs for the current user session:
switch# no terminal edit-mode viThis example shows how to revert the edit mode for recalled command to emacs for the current and future sessions for the current user:
switch# no terminal edit-mode vi persistRelated Commands
terminal history no-exec-in-config
To remove the EXEC commands from the show history command output, use the terminal length command. To revert to the default, use the no form of this command.
terminal history no-exec-in-config
no terminal history no-exec-in-config
Syntax Description
This command has no arguments or keywords.
Defaults
The show history command always displays EXEC commands.
Command Modes
Any command mode
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
The terminal history setting applies only to the current session.
This command does not require a license.
Examples
This example shows how to remove the EXEC commands when recalling the command history from a configuration command mode:
switch# terminal history no-exec-in-configThis example shows how to revert to the default:
switch# no terminal history no-exec-in-configterminal 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 initial default for the console is 0.
The initial default for virtual terminal sessions is 31.
The default for the no form is 24 lines.Command Modes
Any command mode
Supported User Rolesnetwork-admin
vdc-adminCommand 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.
The terminal length setting applies only to the current session.
This command does not require a license.
Examples
This example shows how to set the number of lines of command output to display on the terminal before pausing:
switch# terminal length 28This example shows how to revert to the default number of lines:
switch# terminal no lengthRelated Commands
terminal log-all
To enable logging of all commands, including the show commands, to the accounting log, use the terminal log-all command. To revert to the default, use the no form of this command.
terminal log-all
terminal no log-all
Syntax Description
This command has no arguments or keywords.
Defaults
Does not log the show commands.
Command Modes
Any command mode
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
The terminal log setting applies only to the current session.
This command does not require a license.
Examples
This example shows how to enable logging of all commands in the accounting log:
switch# terminal log-allThis example shows how to disable logging of all commands in the accounting log:
switch# terminal no log-allRelated Commands
terminal redirection-mode
To configure the format of the output from show commands, use the terminal redirection-mode command.
terminal redirection-mode {ascii | zipped}
Syntax Description
ascii
Specifies standard character format when redirecting show command output.
zipped
Specifies zipped format when redirecting show command output.
Defaults
ascii
Command Modes
Any command mode
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
Some of the show commands have lengthy outputs, especially debugging show commands such as the show tech-support command. You can use the terminal redirection-mode command to reduce the size of the file when you redirect the output from the command.
The terminal redirection mode setting applies only to the current session.
This command does not require a license.
Examples
This example shows how to configure zipped format for the terminal redirection mode:
switch# terminal redirection-mode zippedThis example shows how to configure ASCII format for the terminal redirection mode:
switch# terminal redirection-mode asciiRelated Commands
terminal session-timeout
To set the terminal inactivity timeout for the current session, use the terminal session-timeout command. To revert to the default, use the no form of this command.
terminal session-timeout minutes
terminal no session-timeout
Syntax Description
Defaults
0 minutes
Command Modes
Any command mode
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
A value of 0 minutes disables the session timeout.
The terminal session inactivity timeout setting applies only to the current session.
This command does not require a license.
Examples
This example shows how to set the terminal inactivity timeout for the session:
switch# terminal session-timeout 10This example shows how to revert to the default terminal inactivity timeout for the session:
switch# terminal no session-timeoutRelated Commands
terminal type
To set the terminal type for the current session, use the terminal type command. To revert to the default, use the no form of this command.
terminal type type
terminal no 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
ansi
Command Modes
Any command mode
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
The terminal type setting applies only to the current session.
This command does not require a license.
Examples
This example shows how to set the terminal type:
switch# terminal type xtermThis example shows how to revert to the default terminal type:
switch# terminal no 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
Any command mode
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
The terminal width setting applies only to the current session.
This command does not require a license.
Examples
This example shows how to set the number of columns to display on the terminal:
switch# terminal width 70This example shows how to revert to the default number of columns:
switch# terminal no widthRelated Commands
traceroute
To discover the routes that packets take when traveling to an IPv4 address, use the traceroute command.
traceroute {dest-ipv4-addr | hostname} [vrf vrf-name] [show-mpls-hops] [source src-ipv4-addr]
Syntax Description
Defaults
Uses the default VRF.
Does not show the MPLS hops.
Uses the management IPv4 address for the source address.Command Modes
Any command mode
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
To use IPv6 addressing for discovering the route to a device, use the traceroute6 command.
This command does not require a license.
Examples
This example shows how to discover a route to a device:
switch# traceroute 172.28.255.18 vrf managementtraceroute to 172.28.255.18 (172.28.255.18), 30 hops max, 40 byte packets1 172.28.230.1 (172.28.230.1) 0.746 ms 0.595 ms 0.479 ms2 172.24.114.213 (172.24.114.213) 0.592 ms 0.51 ms 0.486 ms3 172.20.147.50 (172.20.147.50) 0.701 ms 0.58 ms 0.486 ms4 172.28.255.18 (172.28.255.18) 0.495 ms 0.43 ms 0.482 msRelated Commands
traceroute6
To discover the routes that packets take when traveling to an IPv6 address, use the traceroute6 command.
traceroute6 {dest-ipv6-addr | hostname} [vrf vrf-name] [source src-ipv6-addr]
Syntax Description
Defaults
Uses the default VRF.
Uses the management IPv6 address for the source address.Command Modes
Any command mode
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
To use IPv4 addressing for discovering the route to a device, use the traceroute command.
This command does not require a license.
Examples
This example shows how to discover a route to a device:
switch# traceroute6 2001:0DB8::200C:417A vrf managementRelated Commands
update license
To update an existing license, use the update license command.
update license {bootflash: | slot0: | usb0: | usb1:}filename license-filename
Syntax Description
Command Modes
Any command mode
Supported User Rolesnetwork-admin
Command History
Usage Guidelines
You can use this command only in the default virtual device context (VDC).
This command does not require a license.
Examples
This example shows how to update a specific license:
switch# update license bootflash:Advanced2.lic Advanced1.licUpdating Advanced1.lic:SERVER this_host ANYVENDOR ciscoAdvanced1.lic:FEATURE LAN_ADVANCED_SERVICES cisco 1.000 permanent 30 HOSTID=VDH=4C0AF664 \SIGN=24B2B68AA676with bootflash:/Advance2.lic:SERVER this_host ANYVENDOR ciscoAdvanced2.lic:FEATURE LAN_ADVANCED_SERVICES cisco 1.000 permanent uncounted HOSTID=VDH=4C0AF664 \SIGN=CB7872B23700Do you want to continue? (y/n) yUpdating license ..donewhere
To display your current context in the command-line interface (CLI), use the where command.
where [detail]
Syntax Description
Defaults
Displays summary context information.
Command Modes
Any command mode
Supported User Rolesnetwork-admin
vdc-adminCommand History
Usage Guidelines
This command helps you to keep track where you are in the CLI and how you got to that place.
This command does not require a license.
Examples
This example shows how to display summary context information:
switch(config-if)# where?conf; interface Ethernet2/3 admin@switch%defaultThis example shows how to display detailed context information:
switch(config-if)# where detail?conf; interface Ethernet2/3 admin@switch%defaultmode: confinterface Ethernet2/3username: adminvdc: switchrouting-context vrf: defaultwrite erase
To erase configurations in persistent memory areas, use the write erase command.
write erase [boot | debug]
Syntax Description
boot
(Optional) Erases only the boot variable and mgmt0 interface configuration.
debug
(Optional) Erases only the debug configuration.
Defaults
Erases all configuration in persistent memory except for the boot variable, mgmt0 interface, and debug configuration.
Command Modes
Any command mode
Supported User Rolesnetwork-admin
vdc-adminCommand 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 returns the device to its initial state, except for the boot variable, mgmt0 interface, and debug configurations. You have to explicitly erase those configurations with the boot and debug options.
This command does not require a license.
Examples
This example shows how to erase the startup configuration:
switch(config-if)# write eraseWarning: This command will erase the startup-configuration.Do you wish to proceed anyway? (y/n) [n] yThis example shows how to erase the boot variable and mgmt0 interface configuration in the persistent memory:
switch(config-if)# write erase bootThis example shows how to erase the debug configuration in the persistent memory:
switch(config-if)# write erase debugRelated Commands
copy running-config startup-config
Copies the running configuration to the startup configuration.
show running-config
Displays the startup configuration.
