Privileged-Level Access; Defining Cli Levels Of Privilege - Juniper SYSTEM BASICS - CONFIGURATION GUIDE V 11.1.X Configuration Manual

NOTE: The vty session factory default is 5. Use the line command to configure up
to a maximum of 30 vtys. The configured vtys are shared among all types of
connections; for example, if you configure 7 vtys, then no more than a total of 7 SSH
plus FTP plus Telnet sessions can simultaneously exist on the router.
To access the system through a local console, attach a terminal to the system console
port. To access the system through Telnet, Telnet client software must be installed
on your host system. To access the system through SSH, SSH version 2.0 client
software must be installed on your host system. To access the system through FTP,
FTP client software must be installed on your host system.
You can configure Telnet to validate login requests. See "Vty Line Authentication and
Authorization" on page 427 in "Managing the System" on page 251 , for more
information. Once Telnet is running on your host system, type in the E Series router
name or its IP address and press Enter. To use a name, your network must have a
name server.
For example, for Microsoft Windows NT enter:
or
You are connected to your E Series router when the following prompt appears:
NOTE: At this point, you have access only to User Exec commands.
To connect through SSH, refer to your SSH client documentation.

Privileged-Level Access

You access the CLI Privileged Exec commands using the enable command.

Defining CLI Levels of Privilege

The CLI has the ability to map any command to one of 16 levels of command privilege
(0 to 15). When you access the Privileged Exec mode, you have access to those
commands that map to your access level or below. In other words, if you access the
Privileged Exec mode at access level 10 (the default), you have access to all commands
with an access level setting of 10 or lower.
In general, command privileges fall within one of the following levels:
telnet 192.168.1.13
telnet westford2
Logging in.
host1>
Chapter 2: Command-Line Interface
Accessing the CLI
49