HP Serviceguard for Linux Version A.11.18 Deployment Guide, August 2008

32
3. Append the public key from the current node to the authorized_keys file on the other node by
executing the following command (as one line):
ssh root@<othernode> ‘cat /root/.ssh/authorized_keys2
>> /root/.ssh/authorized_keys’
4. Set the shell for the ssh authentication agent using the following command:
ssh-agent $BASH
5. Add the rsa identity to the ssh authentication agent
ssh-add
NOTE: To verify that the ssh keys have been set up properly, try to ssh to the other node. If not
prompted for a password, the ssh keys have been set up properly.
To run the script, follow these steps:
1. Change to the directory containing the configuration script, for example:
cd /tmp/sglx_install
2. Make sure the configuration script is executable:
chmod +x sgEasyConfig
3. Run the script:
./sgEasyConfig
4. You will be put into an edit (vi) window to specify the inputs for the script. The content is
shown here. User inputs are shown in bold. For the list servers (including the server where
the script is being executed), make sure the hostname and IP Address are TAB separated.
When done, save and quit (“[Esc]:wq!”). You will be returned to the script for further
processing.
############################################################
# Enter yes or no to indicate whether Virtual Machines are
# participating as nodes in the cluster. Please provide the
# information on same line as the question.
############################################################
Will this cluster have any VM(s) participating as nodes? [yes|no] : no
############################################################
# Enter list of servers that will be part of the current cluster
# and their corresponding IP addresses in the format :
# HOSTNAME.DOMAINNAME<tab>IP-ADDRESS
# Example: xyz.abc.hp.com 111.222.333.444
############################################################
adam.cup.hp.com 16.89.84.245
eve.cup.hp.com 16.89.84.247
############################################################
# Enter the list of non-root users allowed to access this
# cluster and their corresponding roles in the format :
# USER<tab>ROLE
# Example: abcd monitor
# Please note that monitor, full_admin and package_admin are
# the allowed roles for non-root users
############################################################
NOTE: This last section is left blank indicating that only “root” users are enabled to manage the
cluster.
The script comes with its own README. Refer to the README for additional information.