The application CLI uses an industry-standard hierarchical shell familiar to networking administrators.
Log into the device to access Exec mode. Exec mode supports all clear, show, and debug commands. In addition, some configuration commands that do not make changes to the system configuration are also supported. The following example shows the command prompt in Exec mode:
device#
Use the disable
, exit
, or logout
command to exit
Exec mode.
Config mode supports commands that change the device configuration. All NPB application configurations are auto-persistent. Config mode provides access to sub-configuration modes for individual interfaces and other configuration areas. The following example shows how to access the Config mode:
device# configure terminal device(config)#
All configuration commands require admin privilege.
You can use the do command as a shortcut to save time when you are working in any configuration mode and you want to run a command in Exec mode.
For example, if you are configuring an Ethernet interface and you want to run an Exec mode command, such as the dir command, you first have to exit the Interface configuration mode. By using the do command with the dir command, you can ignore the need to change configuration modes, as shown in the following example:
device(config-if-eth-1/2)# do dir
total 32
drwxrwxr-x 3 21487 1011 4096 Mar 26 17:58 .
drwxrwxr-x 3 21487 1011 4096 Mar 13 06:45 ..
-rw-r--r-- 1 root sys 495 Mar 16 15:41 defaultconfig.cluster
-rw-r--r-- 1 root sys 210 Mar 16 15:41 defaultconfig.standalone
drwxrwxr-x 5 root sys 4096 Mar 26 17:57 flex-cli
-rw-r--r-- 1 root root 11093 Mar 26 18:04 startup-config
16908197888 bytes total (8438681600 bytes free)