23.07.2014 Views

Lustre 1.6 Operations Manual

Lustre 1.6 Operations Manual

Lustre 1.6 Operations Manual

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

7.3.3 Start clients<br />

For the TCP client, run:<br />

mount -t lustre<br />

192.168.10.101@o2ib0,192.168.10.102@o2ib1:/mds/client /mnt/lustre<br />

7.4 Multi-Rail Configurations with LNET<br />

To aggregate bandwidth across both rails of a dual-rail IB cluster (o2iblnd) 1 using<br />

LNET, consider these points:<br />

■ LNET can work with multiple rails, however, it does not load balance across<br />

them. The actual rail used for any communication is determined by the peer NID.<br />

■<br />

■<br />

Multi-rail LNET configurations do not provide an additional level of network<br />

fault tolerance. The configurations described below are for bandwidth<br />

aggregation only. Network interface failover is planned as an upcoming <strong>Lustre</strong><br />

feature.<br />

A <strong>Lustre</strong> node always uses the same local NID to communicate with a given peer<br />

NID. The criteria used to determine the local NID are:<br />

■ Fewest hops (to minimize routing), and<br />

■ Appears first in the "networks" or "ip2nets" LNET configuration strings<br />

As an example, consider a two-rail IB cluster running the OFA stack (OFED) with<br />

these IPoIB address assignments.<br />

ib0<br />

ib1<br />

Servers 192.168.0.* 192.168.1.*<br />

Clients 192.168.[2-127].* 192.168.[128-253].*<br />

1. Multi-rail configurations are only supported by o2iblnd; other IB LNDs do not support multiple interfaces.<br />

Chapter 7 More Complicated Configurations 7-7

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!