Remotely accessing the master console

This task describes how to remotely access the master console.

Prerequisites

Before initiating a VPN connection with and IBM® representative, the following requirements must be met:
  • The master console must have a connection to the Internet.
  • A Windows® user account for the support representative must be set up on the master console.
  • If the support representative has a need to access the SAN File System console or the RSA II Web interface remotely, a remote display emulation package, such as Virtual Networking Computer (VNC) server, must be installed and running on the master console.
  • The customer must provide a user ID and password for access.
  • A maintenance agreement must be established between you and IBM or the product must be under software warranty.

Context

The master console is used to set up a VPN connection between you and IBM support representatives. You initiate the connection and have the ability to monitor and control the connection.

Figure 1. VPN connection between the customer and IBM support representativeGraphic illustrates how the VPN connection between the customer and IBM support

Steps

  1. Log into the master console. You can access the master console directly (using the keyboard, monitor, and mouse) or remotely though another computer on the same LAN.
  2. Establish a secure VPN connection from the master console through the VPN gateway to a previously designated VPN server within the IBM intranet. Establish the connection using the IBM connection manager and obtain a connection ID. The IBM connection manager icon is located on the master console desktop.
  3. Provide the connection ID to the service representative. Each time you start a VPN session, a unique connection ID is created.
  4. The service representative connects to the previously designated VPN server within IBM using either a telnet client or a secure shell (SSH) client, such as PuTTY. The service representative uses the connection ID that you provide to access the active VPN tunnel.
  5. The service representative connects to an account on the master console over the VPN connection to access to the master console. The service representative then establishes a second connection to the VPN server. If a remote display emulation package is available, the service representative can use this connection to establish a remote console to the master console.

Result

This connection provides a service representative with the ability to log on to these devices or interfaces:
  • Each of the engines in the SAN File System cluster. The support representative can query and control the engines at the operating system level by initiating an SSH session with the engine. This requires that a UNIX-based user account be set up on each of the engines in the cluster.
  • The administrative command-line interface. The support representative can query and control the SAN File System metadata servers, and access metadata, log, dump, and configuration data. This requires that a SAN File System administrative user account be set up for the support representative.
  • SAN File System clients. The support representative can query and control clients at the operating system level by initiating either an SSH session or a telnet session with the client (if an SSH or telnet application is installed and running on the client). This requires that an operating system user account be set up on each of the clients to which the support representative will need access.
  • SAN File System console and RSA II Web interface (if a remote display emulation package is installed and running).

You can monitor all activity performed by the service representative. You can either run a remote desktop package from another machine to observe the master console desktop, view the master console SSH log file to see the results of all activity, or watch directly from the monitor on the master console. In addition, you can disconnect the VPN session at any time.

Parent topic: Managing metadata servers

Related concepts
Master console

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