HP StorageWorks Scalable File Share Release Notes - Version 2.3

Documentation updates and corrections 1–25
• The LNET ordering in the LNET module networks option at the server side does not matter.
• A same client node does not necessarily use the same LNET to communicate with all SFS servers
1. 8.2.5.2 S e ction 7.11.1a.2 Single SFS system connected to 2 fabrics
In the previous example, the LNET network option would be configured as in the following table:
1. 8.2.5.3 Se c t io n 7.11.1a.3 Client node using 2 IB rails
Assuming the 6 SFS nodes are configured as follows:
• ib0 address ranges are 172.22.0.[1-6]
• ib0:0 address ranges are 172.23.0.[1-6]
The LNET networks option would be configured as in the following table:
Nodes LNET option Comment
Client node set #1 option lnet networks=o2ib0 Uses default ib0 interface
Client node set #2 option lnet networks=o2ib1(ib0) Uses default ib0 interface
SFS server nodes option lnet networks=o2ib0,o2ib1(ib1) Uses both ib0 and ib1
0
1
0
1
0
1
0
1
0
1
Client node set #1
0
1
0
1
0
1
0
1
0
1
Client node set #2
0
1
0
1
SFS
o2ib0
IB Fabric #1 IB Fabric #2
o2ib0
Nodes LNET option Comment
Client node option lnet networks=o2ib1(ib1),o2ib0(ib0) Uses both ib0 and ib1
SFS nodes option lnet ip2nets="o2ib0 *; o2ib1(ib0:0) 172.23.0.[2-6/2] Uses ib0 and ib0:0 interfaces
0
1
0
1
0
1
Client node set
0
1
0
1
0
1
0
1
0
1
SFS
o2ib0
0
1
0
1
o2ib1
IB Fabric