Upgrading HP SFS client software on existing RHEL and SLES 9 SP3 systems 3–19
3.3.4.3 Configuring the NTP server
For the HP SFS diagnostics to work correctly, the date and time on the client nodes must be synchronized
with the date and time on other client nodes, and with the date and time on the servers in the HP SFS system.
In addition, synchronizing the date and time on the systems keeps the logs on the systems synchronized, and
is helpful when diagnosing problems.
As a result, HP strongly recommends that you synchronize the date and time on client nodes with the date
and time on other client nodes, and with the date and time on the servers in the HP SFS system, even though
the systems do not need to be synchronized in order for Lustre to function correctly.
To synchronize the systems, you can enable the NTPD service on the client nodes, and configure the client
nodes to use the same NTP server that the servers in the HP SFS system use (configured on the administration
server).
3.3.4.4 Configuring firewalls
If you intend to run a firewall on your client nodes, you must make sure that it does not block any
communication between the client and the servers in the HP SFS system. If you encounter any problems while
your firewall is running, please disable the firewall and see if the problems can be reproduced. Your
HP Customer Support representative will be able to help you to set up your firewall.
3.3.4.5 Configuring the slocate package on client nodes
The slocate package may be installed on your system. This package is typically set up as a periodic job
to run under the cron daemon. To prevent the possibility of a find command executing on the global file
system of all clients simultaneously, the hpls-lustre-client package searches the
/etc/cron.daily/slocate.cron file and the /etc/updatedb.conf file (if it exists) for references
to lustre or lustre_lite. If no reference is found, lustre and lustre_lite are added to the list
of file systems that the slocate package ignores. This list is in either the /etc/cron.daily/
slocate.cron file or the /etc/updatedb.conf file, depending on the client distribution. When
lustre and lustre_lite are added to this list, all lustre and lustre_lite file systems are ignored
when the slocate package executes a find command.
If you wish to enable the slocate package to search lustre and lustre_lite file systems, remove
the lustre and lustre_lite entries from the /etc/cron.daily/slocate.cron file (or from the
/etc/updatedb.conf file, depending on the distribution) and add a comment containing the text
lustre and lustre_lite at the end of the file.
3.3.5 Step 5: Configuring boot-time mounting of file systems
When you have finished installing and configuring the client node as described in Section 3.3.1 through
Section 3.3.4, configure the client node to mount Lustre file systems at boot time by editing the
/etc/sfstab and /etc/sfstab.proto files. For more information, see Section 4.7.
3.4 Upgrading HP SFS client software on existing RHEL and
SLES 9 SP3 systems
The HP SFS client version must be capable of interoperating with the HP SFS server version on the servers
in the HP SFS system. See Section 1.3.1 for details of which HP SFS server and client software versions can
interoperate successfully.
To upgrade existing RHEL and SLES 9 SP3 client systems, perform the following tasks:
1. Upgrade the HP SFS client software (see Section 3.4.1).
2. Run the sfsconfig command on the client node (see Section 3.4.2).
3. When Portals compatibility is no longer needed, disable Portals compatibility (see Section 3.4.3).
Commenti su questo manuale