HP 3PAR OS 3.1.3 CLI Administrator's Manual

NOTE: Help is available to display information about CLI commands. If you started the CLI with
the cli command, you can obtain help by typing either help or clihelp. When you run
individual CLI commands from a system's native shell, use clihelp.
For details about HP 3PAR CLI commands, see also the HP 3PAR Command Line Interface Reference.
SSH
The system is provided with Secure Shell (SSH) protocol version 2 that enables great flexibility in
accessing the HP 3PAR OS CLI and provides an alternative to installing the remote CLI client. SSH
uses strong symmetric encryption to encrypt all traffic between the client and the server. SSH allows
the use of encrypted passwords, or public/private keys for authentication of the user.
SSH client applications are typically provided with the following operating systems:
• AIX
• HP–UX
• Linux
• Oracle® Solaris™
For Microsoft® Windows® users, an SSH client is available at http://www.openssh.org.
Benefits of Using SSH
SSH provides the following benefits:
• No HP 3PAR CLI installation. CLI clients are not required to access and use the CLI (assuming
SSH client is installed).
• No version matching. The HP 3PAR CLI and HP 3PAR OS versions do not need to match
because the CLI does not need to be installed remotely.
• Strong encryption. All information exchanged between client machines and systems are
encrypted.
• Data integrity. Integrity checking is executed to verify that data has not been altered during
transmission from sender to receiver.
• Server authentication. The system can be authenticated using the public key authentication
scheme. The system’s public key can be stored on client machines, allowing the SSH client to
compare the key presented by the system to the key stored on the client machine.
CLI User Name Restrictions Using SSH
There are several CLI user names that are reserved for use by HP. Reserved names are as follows:
• root
• daemon
• bin
• console
• nobody
• sshd
• telnetd
• sys
• sync
• man
SSH 59