You are here: Home > CLI Commands > CLI Access

CLI Access

When you connect to the Mobility Master using the CLICommand-Line Interface. A console interface with a command line shell that allows users to execute text input as commands and convert these commands to appropriate functions., the system displays the login prompt. Log in using the admin user account and the password you entered during the initial setup on the Mobility Master . For example:

login as: admin

admin@192.0.2.1's password:

Last login: Sat Jun 25 01:17:11 2016 from 192.0.2.77

When you are logged in, the enable mode CLICommand-Line Interface. A console interface with a command line shell that allows users to execute text input as commands and convert these commands to appropriate functions. prompt displays. For example:

(host) [mynode] #

All show commands and certain management functions are available in the enable (also called “privileged”) mode.

Configuration commands are available in config mode. Move from enable mode to config mode by entering configure terminal at the # prompt:

(host) [mynode]# configure terminal

Enter Configuration commands, one per line. End with CNTL/Z

When you are in basic config mode, (config) appears before the # prompt:

(host) [mynode] (config) #

 

There are several other sub-command modes that allow users to configure individual interfaces, sub-interfaces, loopback addresses, GREGeneric Routing Encapsulation. GRE is an IP encapsulation protocol that is used to transport packets over a network. tunnels and cellular profiles. For details on the prompts and the available commands for each of these modes, see CLI Commands.

Command Help

You can use the question mark (?) to view various types of command help.

When typed at the beginning of a line, the question mark lists all the commands available in your current mode or sub-mode. A brief explanation follows each command. For example:

(host) [mynode] #aaa ?

authentication Authentication

inservice Bring authentication server into service

ipv6 Internet Protocol Version 6

query-user Query User

test-server Test authentication server

user User commands

When typed at the end of a possible command or abbreviation, the question mark lists the commands that match (if any). For example:

(host) [mynode] #c?

ccm-debug Centralized Configuration Module debug information

cd Change current config node

change-config-node Change current config node

clear Clear configuration

clock Append clock to cli output

cluster-debug Cluster Debug

configure Configuration Commands

copy Copy Files

copy-provisioning-par.. Copy a provisioning-ap-list entry to provisioning-params

crypto Configure IPsec, IKE, and CA

If more than one item is shown, type more of the keyword characters to distinguish your choice. However, if only one item is listed, the keyword or abbreviation is valid and you can press tab or the spacebar to advance to the next keyword.

When typed in place of a parameter, the question mark lists the available options. For example:

(host) [mynode] #write ?

erase Erase and start from scratch

memory Write to memory

terminal Write to terminal

<cr>

The <cr> indicates that the command can be entered without additional parameters. Any other parameters are optional.

Command Completion

To make command input easier, you can usually abbreviate each key word in the command. You need type only enough of each keyword to distinguish it from similar commands. For example:

(host) [mynode] #configure terminal

could also be entered as:

(host) [mynode] #con t

Three characters (con) represent the shortest abbreviation allowed for configure. Typing only c or co would not work because there are other commands (like copy) which also begin with those letters. The configure command is the only one that begins with con.

As you type, you can press the spacebar or tab to move to the next keyword. The system then attempts to expand the abbreviation for you. If there is only one command keyword that matches the abbreviation, it is filled in for you automatically. If the abbreviation is too vague (too few characters), the cursor does not advance and you must type more characters or use the help feature to list the matching commands.

Deleting Configuration Settings

Use the no command to delete or negate previously-entered configurations or parameters.

To view a list of no commands, type no at the enable or config prompt followed by the question mark. For example:

(host) [mynode] (config) # no?

To delete a configuration, use the no form of a configuration command. For example, the following command removes a configured user role:

(host) [mynode] (config) # no user-role <name>

To negate a specific configured parameter, use the no parameter within the command. For example, the following commands delete the DSCPDifferentiated Services Code Point. DSCP is a 6-bit packet header value used for traffic classification and priority assignment. priority map for a priority map configuration:

(host) [mynode] (config) # priority-map <name>

(host) [mynode] (config-priority-map) # no dscp priority high

/*]]>*/