Skip to main content

We've Moved!

Product Documentation has moved to docs.hitachivantara.com
Hitachi Vantara Knowledge

Accessing the server/cluster command line reference

The storage server ships with a comprehensive CLI, documented in the online man pages and the CLI Command Line Reference. You can access the server/cluster CLI through the Server Control (SSC) utility, available for Windows and Linux.

Access the CLI in the following ways:

  • Secure Shell (SSH) connection into the server through the SMU
  • SSH or Telnet connection directly into the server
  • Server Control (SSC) utility, available for Windows and Linux
NoteTo access the file server CLI directly, using SSH or SSC, through the public network, a server administration IP address may be assigned to at least one of the gigabit Ethernet interfaces. The server supports access to its CLI through any administrative IP address. By default, an administrative IP address is available on the private management network.
NoteWhen using the server CLI, the console device should be configured to use UTF-8 (Unicode) encoding. When using the CLI through SSH or SSC, the server sends and expects to receive data using UTF-8 encoding, so the device sending data to or receiving data from the server should be configured to use UTF-8 encoding.
NoteSystem administrators can query the LDAP server for information about hosts configured into netgroups. You may discover whether a host is in a specific netgroup hierarchy or all of the netgroups to which a host belongs. The nis-is-host-in-netgroup and nis-netgroups-for-host commands are used to check whether a host is a member of a specified netgroup or to determine the set of netgroups to which a host belongs.

Using SSH on the SMU

The SMU supports SSH. After logging into the SMU, the SMU can redirect connections directly to the server CLI. This can be useful for two reasons:

  • It eliminates the need to assign a server administration IP address to the gigabit interface of the server.
  • It enhances the security of the server by isolating administrative access to the private management network.

To SSH into the server using the SMU as a proxy:

Procedure

  1. Connect to the SMU through SSH.

  2. Log in to the SMU as manager.

  3. Select the targeted server from the list that is displayed.

    The SMU automatically initiates a connection to the server CLI.
  4. When prompted, enter the user name supervisor and the password for the “supervisor” user account.

Using SSH on the server

When connecting to a NAS server/cluster through SSH through the administrative services EVS IP address, log in using the user name supervisor.

The Administrator must configure the server to accept SSH connections, and the SSH client should be configured to support UTF-8 (Unicode) character encoding.

Use these steps to connect by SSH to the server.

Procedure

  1. Connect to the server's administrative services DNS name or IP address.

    ssh supervisor@server_name_or_IP
  2. When prompted, enter the "supervisor" user's password.

To SSH into the server

Use these steps to connect by SSH to the server.

  1. Connect to the server's administrative services DNS name or IP address.

    ssh supervisor@server_name_or_IP
  2. When prompted, enter the "supervisor" user's password.

Using Telnet

Telnet is not supported on the NAS server.

Using SSC

The administrator can connect to the server from Windows PCs and from Linux/Unix workstations using SSC, which provides a secure connection using a modified version of the Arcfour cipher for encryption and SHA-1 for authentication.

NoteThe NAS module and NAS Platform Series 5000 uses SHA-2 for authentication.

Use the SSC scripting utility to access the server CLI. The server supports SSC access to its CLI through any administrative IP address. By default, the private management network has an administrative IP address available.

The syntax for SSC: ssc -u user_name -p password host[:port][command]

The following table defines the variables:

Syntax Description
user_name User account (typically “supervisor”).
password Password. If none specified, SSC prompts for one.
timeout A timeout (in seconds) for a single-use command.
EVS Specifies a particular EVS (by its numerical EVS ID) as the target for a single-use command.
host The server’s administration IP address or host name.
port If the SSC port number has been changed from its default of 206, the port number configured for SSC must be specified in the command syntax.
command Command to execute. If no command is specified, SSC allows interactive command entry.

 

  • Was this article helpful?