There are several methods to start the GUI and connect to a node. For more information, see FailSafe Administrator's Guide for SGI InfiniteStorage.
To start the GUI, use one of the following methods:
On an IRIX system where the FailSafe GUI-client software (sysadm_failsafe2.sw.client) and desktop support software (sysadm_failsafe.sw.desktop) are installed, do one of the following:
Note: Do not use this method across a wide-area network (WAN) or virtual private network (VPN), or if the IRIX system has an R5000 or earlier CPU and less than 128-MB memory. Enter the following command line:
# /usr/sbin/fsmgr
(The fsdetail and fstask commands perform the identical function as fsmgr; these command names are kept for historical purposes.)
Choose the following from the Toolchest:
System -> FailSafe Manager
You must restart the Toolchest after installing FailSafe in order to see the FailSafe entry on the Toolchest display. Enter the following commands to restart the Toolchest:
# killall toolchest # /usr/bin/X11/toolchest &
On a PC or if you want to perform administration from a remote location via VPN or WAN, do the following:
Install a web server (such as Apache) and the sysadm_failsafe2.sw.web package on one of the administration nodes with an R5000 or later and at least 128-MB memory.
Install the Java2 v1.4.1 plug-in on your PC.
Close any existing Java windows and restart the Web browser on the PC.
Enter the following URL, where server is the name of a administration node in the pool:
http://server/FailSafeManager/
At the resulting webpage, click the FailSafe Manager icon.
Note: This method can be used on IRIX systems, but it is the preferred method only if you are using WAN or VPN. If you load the GUI using Netscape on IRIX and then switch to another page in Netscape, the FailSafe Manager GUI will not operate correctly. To avoid this problem, leave the FailSafe Manager GUI web page up and open a new Netscape window if you want to view another web page.
The following table describes the platforms where the GUI may be started, connected to, and displayed.
GUI Mode | Where You Start the GUI | Where You Connect the GUI | Where the GUI Displays |
|---|---|---|---|
fsmgr(1) or Toolchest | An IRIX system (such as an SGI 2000 series, SGI O2 workstation, or Silicon Graphics Fuel visual workstation) with sysadm_failsafe2.sw.client and sysadm_failsafe.sw.desktop software installed | The FailSafe administration node in the pool that you want to use for cluster administration | The system where the GUI was invoked |
Web | Any system with a web browser and Java 1.1 plug-in installed and enabled | The FailSafe administration node in the pool that you want to use for cluster administration | The same system with the web browser |
To ensure that the required GUI privileges are available for performing all of the tasks, you should log in to the GUI as root. However, some or all privileges can be granted to any other user using the GUI privilege tasks. (This functionality is also available with the Privilege Manager, part of the IRIX Interactive Desktop System Administration sysadmdesktop product. For more information, see the Personal System Administration Guide.)
A dialog box will appear, prompting you to log in to a FailSafe host. You can choose one of the following connection types:
Local runs the server-side process on the local host instead of going over the network.
Direct creates a direct socket connection using the tcpmux TCP protocol.
Remote Shell connects to the server via a user-specified command shell, such as rsh or ssh.
Note: For a secure connection, choose Remote Shell and type a secure connection command using a utility such as ssh. Otherwise, the FailSafe Manager GUI will not encrypt communication and transferred passwords will be visible to users of the network.
Proxy connects to the server through a firewall via a proxy server.
You should only make changes from one GUI process running at any given time; changes made by a second GUI process (a second invocation of fsmgr) may overwrite changes made by the first instance. However, multiple FailSafe Manager windows accessed via the File menu are all part of the same application process; you can make changes from any of these windows.
The FailSafe administration node to which you connect the GUI affects your view of the cluster. You should wait for a change to appear in the details area before making another change; the change is not guaranteed to be propagated across the cluster until it appears in the view area. The entire cluster status information is sent to every FailSafe administration node each time a change is made to the cluster database.