There are several methods to start the GUI and connect to a node.

Starting the GUI on a PC

To start the GUI 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 following packages on one of the FailSafe nodes:

  sysadm_failsafe2.sw.web sysadm_xvm.sw.web

  
  

• Install the Java2 v1.4.1 or v1.3.2 plug-in on your PC.

• Close any existing Java windows and restart the Web browser on the PC.

• Enter the URL http://server/FailSafeManager/ (where server is the name of a FailSafe node in the pool)

• At the resulting webpage, click the FailSafe Manager icon.

---

Note: This method can be used on IRIX systems, but it is not the preferred method unless you are using WAN or VPN. If you load the GUI using Netscape on IRIX and then switch to another page in Netscape, the GUI will not operate correctly. To avoid this problem, leave the GUI web page up and open a new Netscape window if you want to view another web page.

---

The FailSafe Manager GUI allows you to administer the entire cluster from a single point. It provides access to the tasks that help you set up and administer your FailSafe cluster:

This section discusses the following:

Figure 5-1 shows a sample GUI window.

Figure 5-1. GUI Showing Details for a Resource

Figure 5-2 shows an example of the pop-up menu of applicable tasks that appears when you click the right mouse button on a selected item; in this example, clicking on the resource group name bartest-group displays a list of applicable resource-group tasks.

Figure 5-2. Pop-up Menu that Appears After Clicking the Right Mouse Button

After the command prompt displays, you can enter subcommands. At any time, you can enter ? or help to bring up the cmgr help display.

The cmgr command provides an option which displays detailed prompts for the required inputs that define and modify FailSafe components. You can run in prompt mode in either of the following ways:

For example, if you are not in the prompt mode and you enter the following command to define a node, you will see a single prompt, as indicated:

cmgr> define node cm1a
Enter commands, when finished enter either "done" or "cancel"

cm1a?

At the cm1a? prompt, enter the individual node definition commands in the following format (for full information on defining nodes, see “Define a Node with cmgr” in Chapter 6). For example:

cm1a? set hostname to hostname

A series of commands is required to define a node. If you are running cmgr in prompt mode, however, you are prompted for each required command, as shown in the following example:

cmgr> define node cm1a
Enter commands, you may enter "done" or "cancel" at any time to exit

Node Name [cm1a]? cm1a

Hostname[optional]? cm1a
Is this a FailSafe node <true|false> ? true
Is this a CXFS node <true|false> ? false
Node ID ? 1
Partition ID[optional] ? (0)
Reset type <powerCycle|reset|nmi> ? (powerCycle)
Do you wish to define system controller info[y/n]:y
Sysctrl Type <msc|mmsc|l2|l1>? (msc) msc
Sysctrl Password [optional]? ( )
Sysctrl Status <enabled|disabled>? enabled
Sysctrl Owner? cm2
Sysctrl Device? /dev/ttyd2
Sysctrl Owner Type <tty> [tty]? 
Number of Network interfaces [2]? 2
NIC 1 - IP Address? cm1
NIC 1 - Heartbeat HB (use network for heartbeats) <true|false>? true
NIC 1 - (use network for control messages) <true|false>? true
NIC 1 - Priority <1,2,...>? 1
NIC 2 - IP Address? cm2
NIC 2 Heartbeat HB (use network for heartbeats) <true|false>? true
NIC 2 - (use network for control messages) <true|false>? false
NIC 2 - Priority <1,2,...>? 2

When you are creating or modifying a component of a cluster, you can enter either of the following commands:

The cmgr command supports the following command-line editing commands:

The tasks to define the cluster and to stop HA services are long-running tasks that might take a few minutes to complete. The cmgr command will provide intermediate task status for such tasks. For example:

cmgr> stop ha_services in cluster nfs-cluster
Making resource groups offline
Stopping HA services on node node1
Stopping HA services on node node2

You can set the environment variable CMGR_STARTUP_FILE to point to a startup cmgr script. The startup script that this variable specifies is executed when cmgr is started (with or without the -p option). Only the set and show commands of the cmgr are allowed in the cmgr startup file.

The following is an example of a cmgr startup script file called cmgr_rc:

set cluster test-cluster
show status of resource_group oracle_rg

To specify this file as the startup script, execute the following command:

# setenv CMGR_STARTUP_FILE /cmgr_rc

Whenever cmgr is started, the cmgr_rc script is executed. The default cluster is set to test-cluster and the status of resource group oracle_rg in cluster test-cluster is displayed.

You can enter some cmgr subcommands directly from the command line using the following format:

cmgr -c "subcommand"

where subcommand can be any of the following with the appropriate operands:

For example, to display information about the cluster, enter the following:

# cmgr -c "show clusters"
1 Cluster(s) defined
      eagan

See Chapter 6, “Configuration”, and the cmgr man page for more information.

You can execute a series of cmgr commands by using the -f option and specifying an input file, as follows:

cmgr -f input_file

Or you could include the following as the first line of the file and then execute it as a script:

#!/usr/cluster/bin/cmgr -f

Each line of the file must be a valid cmgr command line, comment line (starting with #), or a blank line. (You must include a done command line to finish a multilevel command and end the file with a quit command line.)

If any line of the input file fails, cmgr will exit. You can choose to ignore the failure and continue the process by using the -i option with the -f option, as follows:

cmgr -if input_file

Or include it in the first line for a script:

#!/usr/cluster/bin/cmgr -if

---

Note: If you include -i when using a cmgr command line as the first line of the script, you must use this exact syntax (that is, -if).

---

For example, suppose the file /tmp/showme contains the following:

fs6# more /tmp/showme
show clusters
show nodes in cluster fs6-8
quit

You can execute the following command, which will yield the indicated output:

fs6# /usr/cluster/bin/cmgr -if /tmp/showme

1 Cluster(s) defined
        fs6-8


Cluster fs6-8 has following 3 machine(s)
        fs6
        fs7
        fs8

Or you could include the cmgr command line as the first line of the script, give it execute permission, and execute showme itself:

fs6# more /tmp/showme
#!/usr/cluster/bin/cmgr -if
#
show clusters
show nodes in cluster fs6-8
quit

fs6# /tmp/showme

1 Cluster(s) defined
        fs6-8


Cluster fs6-8 has following 3 machine(s)
        fs6
        fs7
        fs8

After you have configured the cluster database, you can use the build_cmgr_script command to automatically create a cmgr script based on the contents of the cluster database. The generated script will contain the following:

When you use the -s option, the command also generates create_resource_type scripts for resource types.

As needed, you can then use the generated script to recreate the cluster database after performing a cdbreinit.

By default, the generated script is placed in the following location:

/var/cluster/ha/tmp/cmgr_create_cluster_clustername_processID

You can specify an alternative path name by using the -o option:

build_cmgr_script [-o script_pathname]

For more details, see the build_cmgr_script man page.

For example:

# /var/cluster/cmgr-scripts/build_cmgr_script -o /tmp/newcdb
Building cmgr script for cluster test-cluster ...
build_cmgr_script: Generated cmgr script is /tmp/newcdb

The example script file contents are as follows:

#!/usr/cluster/bin/cmgr -f

# Node node1 definition
define node node1
        set hostname to node1.dept.company.com
        set is_failsafe to true
        set nodeid to 32065
        set hierarchy to Reset,Shutdown
        set reset_type to powerCycle
        set sysctrl_type to msc
        set sysctrl_status to enabled
        set sysctrl_owner to node2
        set sysctrl_device to /dev/ttyd2
        set sysctrl_owner_type to tty
        add nic 192.0.2.58
                set heartbeat to true
                set ctrl_msgs to true
                set priority to 1
        done
        add nic 160.0.2.15
                set heartbeat to true
                set ctrl_msgs to true
                set priority to 2
        done
done

# Node node2 definition
define node node2
        set hostname to node2.dept.company.com
        set is_failsafe to true
        set nodeid to 24140
        set hierarchy to Reset,Shutdown
        set reset_type to powerCycle
        set sysctrl_type to msc
        set sysctrl_status to enabled
        set sysctrl_owner to node1
        set sysctrl_device to /dev/ttyd2
        set sysctrl_owner_type to tty
        add nic 192.0.2.59
                set heartbeat to true
                set ctrl_msgs to true
                set priority to 1
        done
        add nic 160.0.2.16
                set heartbeat to true
                set ctrl_msgs to true
                set priority to 2
        done
done

# Define cluster and add nodes to the cluster
define cluster test-cluster
        set is_failsafe to true
        set ha_mode to normal        
done

modify cluster test-cluster
        add node node1
        add node node2
done


set cluster test-cluster

quit

Template files of scripts that you can modify to configure the different components of your system are located in the /var/cluster/cmgr-templates directory.

Each template file contains a list of cmgr commands to create a particular object, as well as comments describing each field. The template also provides default values for optional fields.

Table 5-2 shows the template scripts for cmgr that are found in the var/cluster/cmgr-templates directory.

To create a FailSafe configuration, you can concatenate multiple templates into one file and execute the resulting script. If you concatenate information from multiple template scripts to prepare your cluster configuration, you must remove the quit at the end of each template script, except for the final quit. A cmgr script must have only one quit line.

For example, for a three-node configuration with an NFS resource group containing one volume, one filesystem , one IP_address, and one NFS resource, you would concatenate the following files, removing the quit at the end of each template script except the last one:

Enter the following command to invoke a shell from within cmgr:

cmgr> sh

To exit the shell and to return to the cmgr prompt, enter exit at the shell prompt.