Setting the options lnet settings B–3
B.2 Setting the options lnet settings
The options lnet settings are critical in ensuring both connectivity and performance when client nodes
access the HP SFS system. When you are determining the appropriate settings for the client nodes, take
account of the following rules:
• There can only be one entry for any network type other than Gigabit Ethernet interconnects.
• For Gigabit Ethernet networks, match the numerical identifier for a network and the identifier of the
server, if possible.
If a client node will connect to more than one HP SFS system and it is not possible to match the
numerical identifiers, use the next available identifier instead.
For all interconnect types other than Gigabit Ethernet, the numeric identifier is always 0.
• When a client node connects to a non-bonded, dual Gigabit Ethernet interconnect, there are three
possible lnet options settings. The network chosen is dependant on the network topology and
the client address, as detailed below:
• tcp0(ethX,ethY)
This setting specifies that the client node has dual Gigabit Ethernet links and can communicate
on both links. The ethX and ethY fields must be set to the appropriate client devices.
• tcp1(ethX)
This setting specifies that the client node can communicate only with the first listed Gigabit
Ethernet interconnect on the HP SFS system (as shown by the sfsmgr show network
command on the HP SFS servers). This setting is used where a client node has a single Gigabit
Ethernet link that is on the same network as the first listed interconnect on the server.
• tcp2(ethY)
This setting specifies that the client node can communicate only with the second listed Gigabit
Ethernet interconnect on the HP SFS system (as shown by the sfsmgr show network
command on the HP SFS servers). This setting is used where a client node has a single Gigabit
Ethernet link that is on the same network as the second listed interconnect on the server.
The following are examples of options lnet settings:
• Quadrics interconnect; the client node accesses only HP SFS Version 2.2 servers that are not running
in Portals compatibility mode:
options lnet networks=elan0 portals_compatibility=none
• Bonded Gigabit Ethernet interconnect; the client node accesses only HP SFS Version 2.2 servers that
are not running in Portals compatibility mode:
options lnet networks=tcp0(bond0) portals_compatibility=none
• Gigabit Ethernet interconnect on eth1; the client node accesses HP SFS Version 2.2 servers, some of
which are running in Portals compatibility mode, and others that are not:
options lnet networks=tcp0(eth1) portals_compatibility=weak
• Two (non-bonded) Gigabit Ethernet interconnects (eth1 and eth2), which the client node uses to
access different HP SFS systems, and an InfiniBand interconnect. The client node accesses only
HP SFS Version 2.2 servers that are not running in Portals compatibility mode:
options lnet networks=tcp0(eth1),tcp1(eth2),vib0 portals_compatibility=none
• Two (non-bonded) Gigabit Ethernet interconnects grouped within a single lnet network, which the
client node uses to connect to an HP SFS system that is configured with a dual Gigabit Ethernet
interconnect. The client node accesses only HP SFS Version 2.2 servers that are not running in Portals
compatibility mode:
options lnet networks=tcp0(eth1,eth2) portals_compatibility=none
Komentáře k této Příručce