HP StorageWorks Scalable File Share - Manual (Page 35)

3.5.2 Creating the /etc/hosts file
Create an /etc/hosts file with the names and IP addresses of all the Ethernet interfaces on
each system in the file system cluster, including the following:
• Internal interfaces
• External interface
• iLO interfaces
• InfiniBand or 10 GigE interfaces
• Interfaces to the Fibre Channel switches
• MSA2000 controllers
• InfiniBand switches
• Client nodes (optional)
Propagate this file should be to all nodes in the file system cluster.
3.5.3 Configuring pdsh
The pdsh command enables parallel shell commands to be run across the file system cluster.
The pdsh RPMs are installed by the HP SFS G3.2-0 software installation process, but some
additional steps are needed to enable passwordless pdsh and ssh access across the file system
cluster.
1. Put all host names in /opt/hptc/pdsh/nodes.
2. Verify the host names are also defined with their IP addresses in/etc/hosts.
3. Append /root/.ssh/id_rsa.pub from the node where pdsh is run to
/root/.ssh/authorized_keys
on each node.
4. Enter the following command:
# echo "StrictHostKeyChecking no" >> /root/.ssh/config
This completes the process to run pdsh from one node. Repeat the procedure for each additional
node you want to use for pdsh.
3.5.4 Configuring ntp
The Network Time Protocol (ntp) should be configured to synchronize the time among all the
Lustre file system servers and the client nodes. This is primarily to facilitate the coordination of
time stamps in system log files to easily trace problems. This should have been performed with
appropriate editing to the initial Kickstart configuration file. But if it is incorrect, manually edit
the /etc/ntp.conf file and restart the ntpd service.
3.5.5 Configuring User Credentials
For proper operation, the Lustre file system requires the same User IDs (UIDs) and Group IDs
(GIDs) on all file system clients. The simplest way to accomplish this is with identical
/etc/passwd
and /etc/group files across all the client nodes, but there are other user
authentication methods like Network Information Services (NIS) or LDAP.
By default, Lustre file systems are created with the capability to support Linux file system group
access semantics for secondary user groups. This behavior requires that UIDs and GIDs are
known to the file system server node providing the MDS service, and also the backup MDS node
in a failover configuration. When using standard Linux user authorization, you can do this by
adding the lines with UID information from the client /etc/passwd file and lines with GID
information from the client /etc/group file to the /etc/passwd and /etc/group files on
the MDS and backup MDS nodes. This allows the MDS to access the GID and UID information,
but does not provide direct user login access to the file system server nodes. If other user
authentication methods like NIS or LDAP are used, follow the procedures specific to those
methods to provide the user and group information to the MDS and backup MDS nodes without
3.5 Configuration Instructions 35