CLI Overview

You can access the CLI by using:

• A terminal emulation program running on a computer connected to the serial port on the device (AP, wireless controller, and service platform).
• A Telnet session through SSH (Secure Shell) over a network.

Configuration for connecting to a Controller using a terminal emulator

If connecting through the serial port, use the following settings to configure your terminal emulator:

When a CLI session is established, complete the following (user input is in bold):

login as: <username>
administrator's login password: <password>

User Credentials

Use the following credentials when logging into a device for the first time:

When logging into the CLI for the first time, you are prompted to change the password. Reset the password and use it for subsequent logins.

Examples in this reference guide

Examples used in this reference guide are generic to the each supported wireless controller, service platform, and AP model. Commands that are not common, are identified using the notation "Supported in the following platforms." For an example, see below:

Supported in the following platforms:

• Wireless Controller – NX5500

The above example indicates the command is only available for a NX5500 model wireless controller.

The CLI is used for configuring, monitoring, and maintaining the network. The user interface allows you to execute commands on supported wireless controllers, service platforms, and APs, using either a serial console or a remote access method.

This chapter describes basic CLI features. Topics covered include an introduction to command modes, navigation and editing features, help features and command history.

The CLI is segregated into different command modes. Each mode has its own set of commands for configuration, maintenance, and monitoring. The commands available at any given time depend on the mode you are in, and to a lesser extent, the particular model used. Enter a question mark (?) at the system prompt to view a list of commands available for each command mode/instance.

Use specific commands to navigate from one command mode to another. The standard order is: USER EXEC mode, PRIV EXEC mode and GLOBAL CONFIG mode.

Figure: Hierarchy of User Modes

Command Modes

A session generally begins in the USER EXEC mode (one of the two access levels of the EXEC mode). For security, only a limited subset of EXEC commands are available in the USER EXEC mode. This level is reserved for tasks that do not change the device‘s (wireless controller, service platform, or AP) configuration.

ap505-13403B>

The system prompt signifies the device name and the last three bytes of the device MAC address.

To access commands, enter the PRIV EXEC mode (the second access level for the EXEC mode). Once in the PRIV EXEC mode, enter any EXEC command. The PRIV EXEC mode is a superset of the USER EXEC mode.

ap505-13403B>en
ap505-13403B#

Most of the USER EXEC mode commands are one-time commands and are not saved across device reboots. Save the command by executing ‘commit‘ command. For example, the show command displays the current configuration and the clear command clears the interface.

Access the GLOBAL CONFIG mode from the PRIV EXEC mode. In the GLOBAL CONFIG mode, enter commands that set general system characteristics. Configuration modes, allow you to change the running configuration. If you save the configuration later, these commands are stored across device reboots.

Access a variety of protocol specific (or feature-specific) modes from the global configuration mode. The CLI hierarchy requires you to access specific configuration modes only through the global configuration mode.

ap505-13403B#configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
ap505-13403B(config)#

You can also access sub-modes from the global configuration mode. Configuration sub-modes define specific features within the context of a configuration mode.

ap505-13403B(config)#aaa-policy test
ap505-13403B(config-aaa-policy-test)#

To enter the logged device's configuration, execute the following command:

ap505-13403B(config)#self
ap505-13403B(config-device-94-9B-2C-13-40-38)#

The following table summarizes the available controller commands: