Red Hat GLOBAL FILE SYSTEM 4.7 Podręcznik Użytkownika Pobierz pdf (Strona 51)

Installing the HP SFS client software on RHEL and SLES 9 SP3 systems (new installations) 3–17

When the script has completed, examine the /etc/modprobe.conf.lustre or /

etc/modules.conf.lustre file and the /etc/modprobe.conf or /etc/modules.conf file to

ensure that the options lnet settings and the lquota settings have been added (see Appendix B for

more information on the settings).

Note that the sfsconfig command uses the http: protocol to get configuration information from the

HP SFS servers. If the client node does not have access to the HP SFS servers over a TCP/IP network, or if

the servers are offline, the sfsconfig command will not be able to configure the client node correctly, and

you will have to modify the configuration file manually. For instructions on how to do this, see Appendix B.

When you have finished configuring the options lnet and lquota settings, proceed to Section 3.3.4

to complete the remaining additional configuration tasks.

3.3.4 Step 4: Completing other configuration tasks

To complete the configuration of the client node, perform the following tasks:

1. Configure interconnect interfaces (see Section 3.3.4.1).

2. Check that the python2 package is loaded (see Section 3.3.4.2).

3. Configure the NTP server (see Section 3.3.4.3).

4. Configure firewalls (see Section 3.3.4.4).

5. Configure the slocate package (see Section 3.3.4.5).

3.3.4.1 Configuring interconnect interfaces

This section describes specific configuration steps that you may need to perform depending on the

interconnect type and configuration that is used in the HP SFS system.

The section is organized as follows:

• Configuring Gigabit Ethernet interfaces (Section 3.3.4.1.1)

• Configuring Voltaire InfiniBand interfaces (Section 3.3.4.1.2)

No specific configuration steps are required for Quadrics or Myrinet interconnects.

3.3.4.1.1 Configuring Gigabit Ethernet interfaces

If a client node uses more than one Gigabit Ethernet interface to connect to an HP SFS system, the

arp_ignore parameter must be set to 1 for all client node interfaces that are expected to be used for

interaction with Lustre file systems. This setting ensures that a client node only replies to an ARP request if

the requested address is a local address configured on the interface receiving the request.

You can set the arp_ignore value for an interface after a client node has been booted; you can also

configure a node so that the arp_ignore value is set automatically when the node is booted, by adding

the arp_ignore definition to the /etc/sysctl.conf file.

For example, if a client node uses interfaces eth1 and eth2 for interaction with an HP SFS system, both of

these interfaces must have the arp_ignore parameter set to 1. To set this value on a running client node,

enter the following commands:

# echo "1" > /proc/sys/net/ipv4/conf/eth1/arp_ignore

# echo "1" > /proc/sys/net/ipv4/conf/eth2/arp_ignore

To configure the client node so that the values are automatically set when the client node is booted, add the

following lines to the /etc/sysctl.conf file:

net.ipv4.conf.eth1.arp_ignore = 1

net.ipv4.conf.eth2.arp_ignore = 1

1 2 ... 46 47 48 49 50 51 52 53 54 55 56 ... 133 134

Brak uwag

Red Hat GLOBAL FILE SYSTEM 4.7 Podręcznik Użytkownika Strona 51