Lustre 1.6 Operations Manual

You could create these configurations:
■
A cluster with more clients than servers. The fact that an individual client cannot
get two rails of bandwith is unimportant because the servers are the actual
bottleneck.
ip2nets="o2ib0(ib0), o2ib1(ib1)192.168.[0-1].* #all servers;\
o2ib0(ib0) 192.168.[2-253].[0-252/2]#even clients;\
o2ib1(ib1) 192.168.[2-253].[1-253/2]#odd clients"
This configuration gives every server two NIDs, one on each network, and statically
load-balances clients between the rails.
■ A single client that must get two rails of bandwidth, and it does not matter if the
maximum aggregate bandwidth is only (# servers) * (1 rail).
ip2nets=" o2ib0(ib0) 192.168.[0-1].[0-252/2] #even servers;\
o2ib1(ib1) 192.168.[0-1].[1-253/2] #odd servers;\
o2ib0(ib0),o2ib1(ib1) 192.168.[2-253].* #clients"
This configuration gives every server a single NID on one rail or the other. Clients
have a NID on both rails.
■ All clients and all servers must get two rails of bandwidth.
ip2nets=” o2ib0(ib0),o2ib2(ib1) 192.168.[0-1].[0-252/2] #even servers;\
o2ib1(ib0),o2ib3(ib1) 192.168.[0-1].[1-253/2] #odd servers;\
o2ib0(ib0),o2ib3(ib1) 192.168.[2-253].[0-252/2)#even clients;\
o2ib1(ib0),o2ib2(ib1) 192.168.[2-253].[1-253/2)#odd clients"
This configuration includes two additional proxy o2ib networks to work around
Lustre's simplistic NID selection algorithm. It connects "even" clients to "even"
servers with o2ib0 on rail0, and "odd" servers with o2ib3 on rail1. Similarly, it
connects "odd" clients to "odd" servers with o2ib1 on rail0, and "even" servers with
o2ib2 on rail1.
7-8 Lustre 1.6 Operations Manual • September 2008