Command Line Interface Overview
The ASR 5000 hardware platform has reached end of life and is not supported in this release. Any references to the ASR 5000 (specific or implied) or its components in this document are coincidental. Full details on the ASR 5000 hardware platform end of life are available at: https://www.cisco.com/c/en/us/products/collateral/wireless/asr-5000-series/eos-eol-notice-c51-735573.html.
This chapter describes the numerous features in the command line
interface (CLI). It includes information about the architecture of the CLI, its
command modes and user privileges, how to obtain help within the CLI, and other
The operating system (StarOS™) controls the overall system logic,
control processes, and the CLI. The CLI is a multi-threaded user interface that
allows you to manipulate, configure, control and query the hardware and
software components that make up the system and its hosted services. In
addition, the CLI can host multiple instances of management and service
configuration sessions. This allows multiple users to simultaneously access and
manage multiple hosted services.
This section provides the following information about the CLI:
CLI commands are strings
of commands or keywords and user-specified arguments that
set or modify specific parameters of the system. Commands
are grouped by function and the various command modes with which
they are associated.
The structure of the
CLI is hierarchical. All users begin at a specific entry
point into the system, called the Exec (Execute) Mode, and
then navigate through the CLI according to their defined user privileges (access
level) by using other command modes.
CLI Command Modes
There are two primary CLI command modes:
Exec (Execute) Mode: The Exec Mode is the lowest level in the
CLI. The Exec Mode is where you execute basic commands such as
ping. When you log into the CLI, you are placed in this mode
Config (Configuration) Mode: The Config mode is accessible
only by users with administrator and security administrator privileges. If you
are an administrative user, in this mode you can add and configure contexts and
access the configuration sub-modes to configure protocols, interfaces, ports,
services, subscribers and other service-related items.
The entry point into the CLI is called Exec Mode. In the initial CLI
login, all users are placed into the default local context, which is the CLI's
default management context. From this context, administrative users can access
the Config Mode and define multiple service contexts.
Refer to the mode entry-path diagrams at the beginning of each mode
chapter in the
Command Line Interface Reference.
The commands or keywords/variables that are available to the user vary
based on platform type, StarOS version and installed license(s).
This section contains
information on the administrative user types and privileges supported
by the system.
There are two types of
administrative users supported by the system:
users: This user type is configured at the context-level and relies on the
AAA subsystems for validating user names and passwords during login. This is
true for both administrative user accounts configured locally through a
configuration file or on an external RADIUS or TACACS+ server. Passwords for
these user types are assigned once and are accessible in the configuration
Local-users: This user
type supports ANSI T1.276-2003 password security protection. Local-user account
information, such as passwords, password history, and lockout states, is
maintained in /flash. This information is maintained in a separate local user
database subject to AAA based authentication and is not used by the rest of the
system. As such, configured local-user accounts are not visible with the rest
of the system configuration.
In release 20.0 and
higher Trusted StarOS builds, the local user database is disabled. The Global
commands, and Exec mode
local-user commands are unavailable. For additional information on Trusted
builds, see the
context-level administrative accounts can be used in parallel. However, a
mechanism is provided to de-activate context-level administrative user
accounts, thereby providing access only to local-user accounts.
Authenticating Administrative Users with RADIUS
To authorize users via RADIUS, you must include two RADIUS attributes in
the RADIUS Access-Accept message:
RADIUS SN-Admin-Permission / SN1-Admin-Permission AVP
The possible values for SN-Admin-Permission / SN1-Admin-Permission AVP
are as follows:
The default value is 1 (CLI).
RADIUS Mapping System
RADIUS server configuration
depends on the type of server used and the instructions distributed
by the server manufacturer. The following table shows the
supported attribute/value mapping system that is constant, regardless
of server manufacturer or model:
Table 1 RADIUS Attribute/Value
There are four RADIUS
privilege roles. The following table shows the relationship between
the privilege roles in the CLI configuration and RADIUS Service-Type.
Table 2 CLI Privilege Roles
and RADIUS Service Types
Users with TACACS+
The ASR 5x00 or StarOS virtual machine is identified
as a Network Access Server (NAS) and remotely
accesses the Terminal Access Controller Access Control System+ (TACACS+) server
for information about users who can perform administrative operations
on the system.
The NAS is defined
as a client-side requesting component associated with a
specific IP address. StarOS only supports one NAS with
one IP address. This NAS processes TACACS+ protocol
packets within the local context. Several management services
may be associated with a login.
StarOS only supports
multiple-connection mode with a TACACS+ server. In
a multiple-connection mode, each TACACS+ session
opens and maintains a separate and private TCP connection to the
server. When the session ends, this connection
is always closed.
and their passwords are defined and stored on the TACACS+ server. They are
stored in a persistent space and are always known to the server
while the server is running. The users are not directly
known to the NAS.
Regardless of the
administrative user type, the system supports four user privilege levels:
Inspector: Inspectors are
limited to a small number of read-only Exec Mode commands. The bulk of these
are show commands for viewing a variety of statistics and conditions. The
Inspector cannot execute show configuration commands and does not have the
privilege to enter the Config Mode.
Operator: Operators have
read-only privileges to a larger subset of the Exec Mode commands. They can
execute all commands that are part of the inspector mode, plus some system
monitoring, statistic, and fault management functions. Operators do not have
the ability to enter the Config Mode.
Administrators have read-write privileges and can execute any command in the
CLI except for a few security-related commands that can only be configured by
Security Administrators. Administrators can configure or modify system settings
and can execute all system commands, including those available to the Operators
Security Administrators have read-write privileges and can execute all CLI
commands, including those available to Administrators, Operators, and
The following figure
represents how user privileges are defined in the CLI configuration modes.
Figure 1. User Privileges
Though the privilege
levels are the same regardless of user type, the corresponding user type names
differ slightly. The following table displays the privilege level to
administrative user type mappings:
Table 3 User Privilege to
User Type Mapping
|User Type as Defined by T1.276-2003
||Local-User Level User
|System Security Administrator
|Application Security Administrator
administrative users in the Context Configuration Mode with the
administrative users at the Global Configuration Mode with the
In release 20.0 and
higher Trusted StarOS builds, the Global Configuration mode
commands are unavaible.
You can further refine
administrative levels to include access to certain features with the following
feature-use administrative user options:
This privilege is
available only for context-level administrative users. In addition, to ensure
security in accordance with the standards, LI administrative users must access
the system through the Secure Shell Protocol (SSH).
All system users can be
configured within any context. However, it is recommended that you configure
users in the system's management context called local. Refer to sections later
in this chapter for additional information about contexts.
per User Type
With the exception
of security administrators, all other management users
are limited to a subset of the entire command list. This
section defines the commands allowed for each management user type.
In the Exec Mode,
system inspectors can access the following commands:
no logging active
no logging trace
no reveal disabled
reveal disabled commands
Operator Mode Commands
In the Exec Mode, system operators can access all inspector mode
commands plus the following commands:
Administrator Mode Commands
Administrators can access all system commands except:
Administrator Mode Commands
administrators can access all system commands.
A security administrator cannot access the shell or monitor debug port
output in Debug Mode through non-local context login.
A context is a group of configuration parameters that apply to the
ports, interfaces, and protocols supported by the system. You can configure
multiple contexts on the system, each of which resides as a separate, logically
independent instance on the same physical device. The CLI can host multiple
contexts within a single physical device.
This allows wireless service providers to use the same system to
Different levels of service
Multiple wholesale or enterprise customers or customer groups
Different classes of customers based on defined Class of Service
IP address pools across multiple contexts, thus saving IP address
Each defined context operates independently from any other context(s) in
the system. Each context contains its own CLI instance, IP routing tables,
access filters, compression methods, and other configured data.
By default, a single system-wide context called "local", is used
exclusively for the management of the system. Think of the local context as the
root directory of the system, since you can define and access all other
contexts from this point. You cannot delete the local context.
From this location in the CLI, you can:
Create and configure other service contexts that contain different
Configure system-wide services such as CORBA and SNMP management
interfaces, physical management ports, system messages, and others
The system requires that you define at least one context in addition
to the local context. This isolates system management functions from
application or service functions.
Administrative users add contexts through the Global Configuration Mode.
A substantial advantage of configuring numerous service contexts is that it
allows operators to broadly distribute different subscribers across the system.
This greatly enhances the performance of the system and minimizes the loss of
sessions should a failure occur.
CLI Command Prompt
The CLI provides an
intuitive command prompt that informs you of:
Exactly where you
are located within the CLI
The command mode
you are using
The following figure
shows the various components of the command prompt.
Figure 2. CLI Command Prompt
CLI Command Syntax
This section describes the components of the CLI command syntax that you
should be familiar with prior to using the CLI. These include:
In the following example,
slot_number are the command variables for the
Commands: Specific words that precede, or initiate, a
Keywords: Specific words that follow a command to more
clearly dictate the command's function.
Variables: Alphanumeric values that are user-supplied as part
of the command syntax. Sometimes referred to as arguments, these terms further
specify the command function.
Repetitive keywords (+): Specific keyword, that when
followed by a plus (+) sign, indicates that more than one of the keywords can
be entered within a single command.
show port info slot_number/
port_number/slot_number is a variable
representing a particular Ethernet slot/port on an ASR 5x00 or vitualized platfrom. See the
System Administration Guide specific to the platform type
for actual slot/port ranges.
A keyword that was supported in a previous
release may be concealed in subsequent releases. StarOS continues to parse
concealed keywords in existing scripts and configuration files created in a
previous release. But the concealed keyword no longer appears in the command
syntax for use in new scripts or configuration files. Entering a question mark
(?) will not display a concealed keyword as part of the Help text.
Entering and Viewing
This section describes
various methods for entering commands into the CLI.
Typing each command
keyword, argument, and variable can be time-consuming
and increase your chance of making mistakes. The CLI therefore, supports
the following features to assist you in entering commands quickly
and more accurately. Other features allow you to view the
display and review previously entered commands.
In all of the modes, the
CLI recognizes partially-typed commands and keywords, as
long as you enter enough characters for the command to be unambiguously
recognized by the system. If you do not enter enough characters
for the system to recognize a unique command or keyword, it
returns a message listing all possible matches for the partial entry.
If you enter the partial
command conf and press Enter, you
enter the Global Configuration Mode. If you were to enter
only c, the system would respond with the message:
CLI Command Auto-completion
Use the command auto-completion
feature to automatically complete unique CLI commands. Press
the Tab key after
entering enough characters to enable this feature.
If you do not enter
enough characters to allow the CLI to determine the appropriate command
to use, the CLI displays all commands that match the characters
you entered with auto-completion:Important:
If you enter a partial
keyword for a keyword that is concealed in this release, pressing Tab will
not complete the concealed keyword. You must type in the
complete keyword to display/execute a concealed keyword.
Enter a question mark (?) after
a partial command to display all of the possible matching commands, and
their related help text.
shutdown - Terminates execution of all tasks within the entire chassis
show - Displays information based on a specified argument
not display keywords that have been concealed in this release.
Using CLI Auto-Pagination
When you enter commands
whose expected results exceed the terminal window's vertical
display, the auto-pagination function pauses the
display each time the terminal window reaches its display limit. Press
any key to display the next screen of results.
By default, auto-pagination
functionality is disabled. To enable auto-pagination, type
the pipe command: | more.
[local]host_name# show configuration | more
is enabled, if a command's output exceeds the
terminal window's vertical display parameters, you
can exit by entering "q". This
returns you to the CLI prompt.
Using CLI Autoconfirmation
By default, the system is configured to prompt all administrative users
with a confirmation prior to executing certain commands. This functionality
serves two purposes:
For example, to save a configuration:
[local]host_name# save configuration
Are you sure ? [Yes | No]:
You create a context named
Indicates potential misspellings of names during configuration. The
first time you configure an element name (context, subscribers, services,
etc.), the prompt is displayed. The prompt is not displayed for subsequent
entries of the name. Therefore, if you see the confirmation prompt after
entering the name of a previously configured element, it is likely that you
misspelled the name.
[local]host_name(config)# context newcontext
Are you sure ? [Yes | No]: yes
You revisit the context named
[local]host_name(config)# context newcontext
On another occasion, you misspell the context named
[local]host_name(config)# context mewcontext
Are you sure ? [Yes | No]:n
After aborting the above action, you can again revisit
[local]host_name(config)# context newcontext
You can control CLI autoconfirmation at the following levels:
Specific administrative user sessions: To enable or disable
autoconfirmation, use the
[no] autoconfirm commands while in the Exec Mode.
All Future Sessions: To disable or re-enable autoconfirmation
for all future sessions, use the
[no] autoconfirm commands while in the Global Configuration
For specific commands: Disable autoconfirmation for various
commands that support the
-noconfirm keyword, such as the save configuration or card
Regulating the Command
For many CLI commands, you
can use | grep and/or | more keywords
to regulate or control the command's output.
grep for Regular Expressions
| grep keyword to filter through a command's output for certain
expressions or patterns. Only those portions of the output that contain or
exclude the pattern are displayed. The
| grep has the following syntax:
| grep [ -E | -i | -n |-v | --extended-regexp | --ignore-case | --invert-match | --line-number ] expression
Table 4 grep Options
||Match using extended regular expressions (EREs).
Treat each pattern specified as an ERE ("IEEE Std 1003.1-2001, Section 9.4,
Extended Regular Expressions"). If any entire ERE pattern matches some part of
an input line excluding the terminating <newline>, the line shall be
matched. A null ERE shall match every line.
||Perform pattern matching in searches without
regard to case. Lower case matches the same as upper case.
||Precede each output line by its relative line
number in the file, each file starting at line 1. The line number counter is
reset for each file processed.
||Select lines not matching any of the specified
patterns. If the -v option is not specified, selected lines shall be those that
match any of the specified patterns.
||The long form of the
||The long form of the
||The long form of the
||Specifies the character pattern to find in the
command's output as an alphanumeric string of 1 to 256 characters.
A regular expression is a pattern that describes a set of strings.
Regular expressions are constructed analogously to arithmetic expressions, by
using various operators to combine smaller expressions. For additional
information, refer to
ISO/IEC/IEEE 9945:2009 Information technology – Portable
Operating System Interface (POSIX®) Base Specifications, Issue 7.
Use the | more keyword
to pause the terminal each time the terminal window reaches its
display limit. Press any key to display the next screen. The function
of this keyword is identical to the autoless command, except
that you must manually enter it on a command-by-command basis.
To view a history of
all commands line by line, simply scroll up or down with
the <up arrow>
and <down arrow>
cursor keys on the keyboard.
The operating system
supports EMACS-style text editing commands. This
standard UNIX text editor format allows you to use keyboard-based
shortcut keys for maneuvering around the CLI. The following
table lists these available shortcut keys.
Table 5 EMACS Shortcut Keystrokes
|<Ctrl + p>
and <up arrow>
previous command in the command history
|<Ctrl + n>
and <down arrow>
next command in the command history
|<Ctrl + f>
and <right arrow>
cursor forward by one character in command line
|<Ctrl + b>
and <left arrow>
cursor backward by one character in command line
|<Esc> + <f>
cursor forward by one word in command line
|<Esc> + <b>
cursor backward by one word in command line
|<Ctrl> + <a>
cursor to the beginning of the command line
|<Ctrl> + <e>
cursor to the end of the command line
|<Ctrl> + <k>
the current command line from the insertion point to the end of
|<Ctrl> + <u>
the current command line from the insertion point to the beginning
of the line
|<Ctrl> + <d>
a single character in the current command line
|<Esc> + <d>
a word in the current command line
|<Ctrl> + <c>
editing the current line
|<Ctrl> + <l>
|<Ctrl> + <t>
switches) the two characters surrounding the insertion
Obtaining CLI Help
The CLI provides context-sensitive help for every command token and
keyword available to you. To obtain, use one of these methods:
Command Help: Command help provides assistance for a specific
command. Type a question mark (?) at the end of the specific command to
test - Performs test on followed mechanism
Keyword Help: Keyword help provides assistance in determining
the next keyword, argument, or option to use in the command syntax. Enter the
command keyword, enter a space, and then type a question mark (?).
[local]host_name# test alarm ?
audible - Tests internal audible alarm buzzer on SPC
central-office - Tests specified central office alarm relays
<cr> - newline
Variable Help: Variable help provides the correct format,
value, or information type for each variable that is part of the command
syntax. For commands with variables, enter the command keyword, enter a space,
and then type a question mark (?).
[local]host_name# show card info ?
<Enter card number as an integer ranging 1 to n>
| - Pipeline
<cr> - Carriage Return or <Enter> key
Exiting the CLI and CLI Command Modes
A CLI session is defined as the successful login into the CLI. When you
establish a CLI session, you are placed into the system's Exec Mode. Depending
upon your user privilege level, you can:
local context to perform system management functions.
Move to an assigned context and work in Exec Mode.
Move to an assigned context as an administrative user and work in
Global Configuration Mode or other configuration sub-mode.
This section addresses how to properly exit the various modes and the
To exit a configuration
sub-mode and return to the next highest configuration sub-mode
or Global Configuration Mode, type the exit command at
the system prompt.
The CLI supports implicit
mode-exits when using configuration files. Therefore, configuration
files do not have to contain all of the required exit commands
for you to leave various sub-config modes.
To exit a sub-mode
and return to the Exec Mode, enter the end command.
Exiting Global Configuration
To exit Global Configuration
Mode, and return to the Exec Mode prompt, type
the exit command at the prompt.
Ending a CLI Session
To end a CLI session
and exit the CLI, type the exit command at the Exec
Accessing the CLI
Access the CLI through the following methods:
Local login through an ASR 5x00
Console port via a serial connection with a management card
Local login through a vConsole port
via the hypervisor that initiated the StarOS virtual machine
Remote login using Telnet and Secure Shell (SSH) access to the CLI
through any IP interface on the system. You can use remote login methods only
after the system has been configured to support the various access methods.
Even though you can access the CLI remotely through any available IP
interface, management traffic should be isolated from network traffic by using
one of the dedicated management interfaces supported on the ASR 5x00
platform or StarOS virtual machine.
Multiple CLI sessions are supported, but the number of sessions varies
based on the amount of available memory. The Resource Manager reserves enough
resources so that as a minimum up to 15 CLI sessions are assured. One of the
CLI sessions is always reserved for use exclusively by a CLI session on a
Console or vConsole interface. Additional CLI
sessions beyond the pre-reserved set are permitted if sufficient CPU
resources are available. If the Resource Manager is unable to
reserve additional resources, you are prompted whether to allow the system to
create the new CLI session, even without the reserved resources.
Accessing the CLI Locally Using an ASR 5x00 Console Port
This section provides instructions for accessing the CLI locally through
a Console port on the ASR 5x00 platform.
Establish a connection between the serial Console port on an ASR 5x00
and a workstation that has a communications application that accesses the
workstation's serial port, such as Minicom for Linux or HyperTerminal® for
MicroSoft Windows®. Refer to the ASR 5x00
Installation Guide for detailed information on connecting to
a serial Console port.
Configure the communications application to support the following:
To change the configuration defined in the table above, modify the
terminal command located in the Global Configuration Mode.
- At the terminal window,
- If no configuration file is present (that is, this is the first time
the system is powered), the CLI prompts you as to whether or not you want to
use the Quick Setup Wizard. If the system was configured previously, you are
prompted to enter a username and password.
Accessing the CLI Locally Using a vConsole Port
You connect to a vConsole port via a hypervisor that initiates
a virtual machine running StarOS. Refer to the hypervisor
user documentation and the VPC Administration Guide for additional
To remotely access
the CLI through a defined management interface, you must first
configure the remote access method (such as Telnet or SSH).
You can find examples
of how to configure this in the Getting Started chapter
in the System Administration
on ASR 5x00 and virtualized platforms. Howerver, all
CLI features and functions are not supported by all platforms.
This guide includes
descriptions for all commands that have been qualified to run under
StarOS. There may be specific instances where a command
cannot be run and an error message is generated.
As features become
fully qualified on specific or all platforms, this guide
will be revised to reflect supported commands. For additional
information, refer to the Release Notes provided
with each StarOS version
A Trusted build is a starfile image from which non-secure or low
security features have been deleted or disabled. However, the binaries in the
Trusted starfile image are are identical to those found in other starfiles for
a particular StarOS release-build number. In general, a Trusted build is more
restrictive than a Normal build image.
You can identify whether your platform is running a Trusted build via
the Exec mode
show version command. The output of the command displays the
word "Trusted" as part of the image description text.
The following non-secure programs and features are disabled/removed
from a Trusted build:
- FTP (File Transfer
- Local user database access
- tcpdump utility
- rlogin (Remote Login) utility and
rlogind (Remote Login daemon)
- rsh (Remote Shell) and
rcp (Remote Copy) utilities
IP Address Notation
When configuring a port
interface via the CLI you may be required to enter an IP address. The
CLI always accepts an IPv4 address, and in some cases accepts
an IPv6 address as an alternative.
For some configuration
commands, the CLI also accepts CIDR notation when entering
an IP address. Always view the online Help for the CLI
command to verify acceptable forms of IP address notation.
An Internet Protocol
Version 4 (IPv4) address consists of 32 bits divided
into four octets. These four octets are written in decimal numbers, ranging
from 0 to 255, and are concatenated as a character string
with full stop delimiters (dots) between each
For example, the
address of the loopback interface, usually assigned the
host name localhost, is 127.0.0.1. It
consists of the four binary octets 01111111, 00000000, 00000000, and 00000001, forming
the full 32-bit address.
IPv4 allows 32 bits
for an Internet Protocol address and can, therefore, support
2^32 (4,294,967,296) addresses
IPv6 Colon-Separated-Hexadecimal Notation
An Internet Protocol Version 6 (IPv6) address has two logical parts: a
64-bit network prefix, and a 64-bit host address part. An IPv6 address is
represented by eight groups of 16-bit
hexadecimal values separated by colons (:).
A typical example of a full IPv6 address is
The hexadecimal digits are case-insensitive.
The 128-bit IPv6 address can be abbreviated with the following rules:
- Leading zeroes within a
16-bit value may be omitted. For example, the address
fe80:0000:0000:0000:0202:b3ff:fe1e:8329 may be written as
- One group of consecutive
zeroes within an address may be replaced by a double colon. For example,
fe80:0:0:0:202:b3ff:fe1e:8329 becomes fe80::202:b3ff:fe1e:8329
IPv6 allows 128 bits for an Internet Protocol address and can support
2^128 (340,282,366,920,938,000,000,000,000,000,000,000,000) internet addresses.
Classless Inter-Domain Routing (CIDR) notation is a compact
specification of an Internet Protocol address and its associated routing
prefix. It is used for both IPv4 and IPv6 addressing in networking
CIDR is a bitwise, prefix-based standard for the interpretation of IP
addresses. It facilitates routing by allowing blocks of addresses to be grouped
into single routing table entries. These groups (CIDR blocks) share an initial
sequence of bits in the binary representation of their IP addresses.
CIDR notation is constructed from the IP address and the prefix size,
the latter being the number of leading 1 bits of the routing prefix. The IP
address is expressed according to the standards of IPv4 or IPv6. It is followed
by a separator character, the slash (/) character, and the prefix size
expressed as a decimal number.
On the ASR 5000, routes with IPv6 prefix lengths less than /12 and
between the range of /64 and /128 are not supported.
The address may denote a single, distinct, interface address or the
beginning address of an entire network. In the latter case the CIDR notation
specifies the address block allocation of the network. The maximum size of the
network is given by the number of addresses that are possible with the
remaining, least-significant bits below the prefix. This is often called the
The number of addresses of a subnet defined by the mask or prefix can be
calculated as 2address size - mask, in which the address size for
IPv4 is 32 and for IPv6 is 128. For example, in IPv4, a mask of /29 gives 8
Some CLI commands
require the entry of a string of characters that can contain a contiguous collection
of alphabetic, numeric, or alphanumeric characters
with a defined minimum and maximum length (number of characters)
The alphanumeric character set is a combination of alphabetic characters
(Latin letters) and numeric characters (Arabic numerals). The set consists of
the letters A to Z (uppercase) and a to z (lowercase) and the numbers 0 to 9.
The underscore character ( _ ) and dash/hyphen character ( - ) can also be
Blank spaces (whitespaces or SPACE characters) should mostly be avoided
in alphabetic, numeric, and alphanumeric strings, except in certain ruledef
formats, such as time/date stamps.
The following special characters can be used in ruledefs, APNs, license
keys and other configuration/display parameters:
The following special characters can be used to delimit the domain from
the user name for global AAA functions:
- < > (arrow brackets)
[less than or greater than]
- * (asterisk) [wildcard]
- : (colon)
- $ (dollar sign) [wildcard]
- . (dot)
- = (equals sign)
- ! (exclamation point)
- % (percent)
- / (slash - forward)
- | (vertical bar)
- @ (at sign)
- - (dash or hyphen)
- # (hash or pound sign)
- % (percent)
- \ (slash - backward) [must be entered as double slash \\]
- / (slash - forward)
If descriptive text
requires the use of spaces between words, the string must
be entered within double quotation marks (" ").
interface "Rack 3 Chassis 1 port 5/2"