Accessing an engine through SSH

This topic describes how to remotely access an engine using SSH from the master console.

Prerequisites

Before accessing an engine using SSH, the following requirements must be met:
  • A SAN File System administrative user account must be set up for use in signing on to the SAN File System console.
  • A UNIX-based operating system account must be set up on the engine to be accessed for use in signing on to the SSH session.
  • If the service representative is accessing the master console remotely:
    • You must have previously initiated a VPN connection with the service representative.
    • The service representative must have established the VPN connection.

Steps

  1. From the master console, use one of these methods to access the engine:
    1. Open a shell prompt and type putty.exe -ssh engine_IP_address, where engine_IP_address is the IP address of the engine to be accessed.
      Note: If you used SSH to establish a remote session with the master console, type this command from that session to establish an SSH session between the master console and the engine.
    2. Click StartProgramsPuTTYPuTTY.
      1. Type the IP address of the engine to be accessed.
      2. Select SSH as the protocol.
      3. Click Open.
  2. After the session is established, log in using a UNIX-based user ID and password.

Result

After connecting to the engine, you can perform these activities:
  • Access the SAN File System administrative command-line interface (CLI) to run SAN File System commands. These commands provide the ability to manage engines, metadata servers, and administrative servers.
  • Access operating-system commands to enable or disable tracing, obtain dumps, and stop or start applications.

Parent topic: Managing engines

Terms of use | Feedback
(C) Copyright IBM Corporation 2003, 2004. All Rights Reserved.