Using the Secure Shell server

Use the management module Secure Shell server to open a secure connection to a command-line interface.

The following SSH clients are available. Although some SSH clients have been tested, support or nonsupport of any particular SSH client is not implied.

If you are using a Secure Shell client that is based on openSSH, such as the client that is included in Red Hat Linux version 7.3, to start an interactive command-line Secure Shell session to a management module with network address, type a command similar to the following example:

            ssh -x -l USERID

where -x indicates no X Window System forwarding and -l indicates that the session is to use the login ID USERID.

The advanced management module supports non-interactive Secure Shell sessions. This support is most useful when it is combined with public key authentication. Use this capability to issue a single CLI command by adding the command to the end of the ssh command. For example, to get a list of the current users of the advanced management module, type

            ssh -l USERID users -T mm[1] -curr

If the CLI command requires a special character such as a quotation mark, precede the character with an escape sequence so that it is processed correctly by the command shell on your client system. For example, to set a new trespass warning, type a command similar to the following command:

            ssh -l USERID trespass -T mm[1] -tw \"New  WARNING\"

To start a Serial over LAN text redirection session to a blade server the process is similar, but in this case it is important to specify that the Secure Shell server session uses a pseudo-terminal (PTY) to get the correct output formatting and keystroke handling. In the following example, which starts a Serial over LAN session to the blade server in bay 2, the ssh client option -t specifies that a pseudo-terminal should be allocated:

            ssh -t -l USERID console -T blade[2]