HP StorageWorks Scalable File Share - Manual (Page 24)

%{nfs_server} must be replaced by the installation NFS server address or FQDN.
%{nfs_iso_path} must be replaced by the NFS path to the RHEL5U2 ISO directory.
%{post_image_dir} must be replaced by the NFS path to the HP SFS G3.0-0 ISO directory.
%{post_image} must be replaced by the name of the HP SFS G3.0-0 ISO file.
Each server node that is to be installed must be accessible over a network from an installation
server that contains the Kickstart file, the RHEL5U2 ISO image, and the HP SFS G3.0-0 Software
ISO image. This installation server must be configured as a DHCP server to network boot the
file system server nodes to be installed. For this to work, the MAC addresses of the DL380 G5
server eth1 Ethernet interface must be obtained during the BIOS setup. These addresses must
be put into the /etc/dhcpd.conf file on the installation server to assign Ethernet addresses
and network boot the file system servers. See the standard Linux documentation for the proper
procedure to set up your installation server for DHCP and network booting.
The file system server installation starts with a RHEL5U2 Kickstart install. If the installation
server has been set up to network boot the file system servers, the process starts by powering
on the file system server to be installed. When properly configured, the network boot first installs
Linux using the Kickstart parameters. The HP SFS G3.0-0 Software, which must also be available
over the network, installs in the Kickstart post-install phase and the /opt/hp/sfs/scripts/
install1.sh
script is run.
NOTE: The output from Installation Phase 1 is contained in /var/log/postinstall.log.
Proceed to “Installation Phase 2” .
3.4 Installation Phase 2
After the Kickstart and install1.sh have been run, the system reboots and you must log in
and complete the second phase of the HP SFS G3.0-0 Software installation by running the /opt/
hp/sfs/scripts/install2.sh
script provided. The system must be rebooted again, and
you can proceed with system configuration tasks as described in “Configuration Instructions”
(page 24) .
NOTE: You might receive errors when running install2. They can be ignored. See “Errors
from install2” (page 45) for more information.
3.5 Configuration Instructions
After the HP SFS G3.0-0 Software has been installed, some additional configuration steps are
needed. These steps include the following:
• Configuring network interfaces for Ethernet and InfiniBand
• Creating the /etc/hosts file and propagating it to each node
• Configuring the pdsh command for file system cluster-wide operations
• Configuring user access
3.5.1 Configuring Ethernet and InfiniBand Interfaces
Ethernet and InfiniBand IPoIB ib0 interface addresses must be configured, if not already
configured with network statements in the Kickstart file. Use the Red Hat GUI, the
system-config-network
command, or edit /etc/sysconfig/network-scripts/
ifcfg-xxx files.
The IP addresses and netmasks for the InfiniBand interfaces should be chosen carefully to allow
the file system server nodes to communicate with the client nodes.
The system name, if not already set by the Kickstart procedure, must be set by editing the /etc/
sysconfig/network file
as follows:
24 Installing and Configuring HP SFS Software on Server Nodes