Using the Secure Shell server

This topic tells you how to use the management module Secure Shell server.

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 the 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 192.168.70.2, type a command similar to the following example:

ssh -x -l USERID 192.168.70.2

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 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 192.168.70.2 users -T mm[1] -curr

If the CLI command requires special characters such as quotation marks, you must escape them so that they are not consumed by the command shell on your client system. For example, to set a new trespass warning, type a command similar to the following example:

ssh -l USERID 192.168.70.2 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 you must 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 slot 2, the -t SSH client option specifies that a PTY is to be allocated.

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