IBM HS40 Setup Guide - Page 45

Starting a command-line Secure Shell (SSH) connection

Get IBM HS40 - BladeCenter - 8839 PDF manuals and user guides
UPC - 000435160188
View all IBM HS40 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 45 highlights

Starting a command-line Secure Shell (SSH) connection To log on to the management module using SSH, complete the following steps: 1. Make sure that the SSH service on the network-management workstation is enabled. See your operating-system documentation for instructions. 2. Make sure that the SSH server on the BladeCenter management module is enabled. See the BladeCenter Management Module User's Guide for instructions. 3. Start a SSH session to the management module using the SSH client of your choice. For example, if you are using the cygwin client, open a command-line window on the network-management workstation, type ssh -x 192.168.70.125, and press Enter. The IP address 192.168.70.125 is the default IP address of the management module; if a new IP address has been assigned to the management module, use that one instead. A command-prompt window opens. 4. Type the management-module user ID when prompted. At the password prompt, type the management-module password. The user ID and password are case sensitive and are the same as those that are used for management-module Web access. The default management-module user name is USERID and the default password is PASSW0RD (note the number zero, not the letter O, in PASSW0RD). A CLI command prompt is displayed. You can now enter commands for the management module. Starting an SOL session from the command-line interface After an SOL session is started, all commands are sent to the operating system on the blade server specified by the console command until the SOL session is ended, regardless of the persistent command target that was in effect before the SOL session. During an SOL session, no BladeCenter command-line interface commands are valid. If a blade server is restarted while an SOL session is in progress, the SOL session remains in progress while the blade server restarts. Restarting the management module will end all SOL sessions that are running. The BladeCenter management module automatically stores the previous 8 KB (kilobytes) of serial data that was transmitted by each blade server even when SOL sessions are not active. When an SOL session is established, all of the previous serial data, up to 8 KB, is automatically displayed. If no previous data is available when the SOL session is started, the cursor will remain on the command line until new serial data is transmitted. If a management module fails, all Telnet and SOL sessions are terminated, and their caches are lost, even if failover to a redundant management module is successful. See the BladeCenter Management Module Command-Line Interface Reference Guide for information about configuring a blade server for SOL using the management module command-line interface. See your operating-system documentation for information about commands that you can enter using an SOL command-line interface. Note: Serial over LAN (SOL) must be enabled for both the BladeCenter unit and the blade server before you can start an SOL session with the blade server. See Chapter 2, "General configuration," on page 7 and Chapter 4, "Special component requirements," on page 25 for information about enabling SOL. Chapter 5. Using SOL 39

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
Starting a command-line Secure Shell (SSH) connection
To log on to the management module using SSH, complete the following steps:
1.
Make sure that the SSH service on the network-management workstation is
enabled. See your operating-system documentation for instructions.
2.
Make sure that the SSH server on the BladeCenter management module is
enabled. See the
BladeCenter Management Module User’s Guide
for instructions.
3.
Start a SSH session to the management module using the SSH client of your
choice. For example, if you are using the cygwin client, open a command-line
window on the network-management workstation, type
ssh -x
192.168.70.125
, and press Enter. The IP address 192.168.70.125 is the default IP
address of the management module; if a new IP address has been assigned to
the management module, use that one instead.
A command-prompt window opens.
4.
Type the management-module user ID when prompted. At the password
prompt, type the management-module password. The user ID and password
are case sensitive and are the same as those that are used for
management-module Web access. The default management-module user name
is USERID and the default password is PASSW0RD (note the number zero, not
the letter O, in PASSW0RD).
A CLI command prompt is displayed. You can now enter commands for the
management module.
Starting an SOL session from the command-line interface
After an SOL session is started, all commands are sent to the operating system on
the blade server specified by the
console
command until the SOL session is ended,
regardless of the persistent command target that was in effect before the SOL
session. During an SOL session, no BladeCenter command-line interface commands
are valid. If a blade server is restarted while an SOL session is in progress, the SOL
session remains in progress while the blade server restarts. Restarting the
management module will end all SOL sessions that are running.
The BladeCenter management module automatically stores the previous 8 KB
(kilobytes) of serial data that was transmitted by each blade server even when SOL
sessions are not active. When an SOL session is established, all of the previous
serial data, up to 8 KB, is automatically displayed. If no previous data is available
when the SOL session is started, the cursor will remain on the command line until
new serial data is transmitted. If a management module fails, all Telnet and SOL
sessions are terminated, and their caches are lost, even if failover to a redundant
management module is successful.
See the
BladeCenter Management Module Command-Line Interface Reference Guide
for
information about configuring a blade server for SOL using the management
module command-line interface. See your operating-system documentation for
information about commands that you can enter using an SOL command-line
interface.
Note:
Serial over LAN (SOL) must be enabled for both the BladeCenter unit and
the blade server before you can start an SOL session with the blade server. See
Chapter 2, “General configuration,” on page 7 and Chapter 4, “Special component
requirements,” on page 25 for information about enabling SOL.
Chapter 5. Using SOL
39