HP StorageWorks Scalable File Share Release Notes - Version 2.3

New and changed features in HP SFS Version 2.31–16
1.8 Documentation updates and corrections
This section provides updates for new features and corrections for errors in the HP SFS Version 2.3
documentation.
1. 8 .1 HP StorageWorks Scalable File Share System Installation and Upgrade
Guide
This section contains the following affected sections:
• Section 2.4.3.1a Configuring multiple InfiniBand interfaces with OFED (Section 1.8.1.1)
• Section 2.4.3.1b Configuring multiple o2ib LNETs per IB interface with OFED (Section 1.8.1.2)
• Section 2.4.3.2 Determining the OFED InfiniBand interconnect information (Section 1.8.1.3)
• Section 5.2.4 Configuring the EVA software using the SSSU utility (Section 1.8.1.4)
• Section 6.4.3 iLO settings — iLO browser tasks (Section 1.8.1.5)
• Section 6.13 Step 13: Scanning MAC addresses (Section 1.8.1.6)
• Section 7.2.3 iLO settings — iLO browser tasks (Section 1.8.1.7)
• Section 7.10 Step 10: Scanning MAC addresses (Section 1.8.1.8)
• Appendix F SSSU script examples (Section 1.8.1.9)
1.8 .1.1 Sect ion 2.4 .3.1a Confi g u ri ng m u l t iple InfiniBand interfaces with OFED
Insert the following section between 2.4.3.1 and 2.4.3.2:
SFS V2.3 allows you to configure two or more IB interfaces on the SFS server nodes. This can be done if the
HCA board has 2 InfiniBand ports, or if the servers are configured with multiple InfiniBand HCAs.
Configuring multiple IB interfaces on the servers allows you to connect the SFS system to multiple IB fabrics.
For instance, two computer clusters that do not share the same IB fabric can be connected to the same SFS
system.
The purpose of using multiple interfaces on the servers is not to increase the per server IO bandwidth, since
the storage is the limiting factor.
Configuring additional IB interfaces requires a unique range of IPoIB addresses for each interface.
At interconnect configuration time, the sfsmgr cli will detect all IB ports connected to an IB fabric. For each
corresponding IPoIB interface it will perform the following tasks:
• Prompt for the required IPoIB address information.
• Automatically create one LNET (o2ib0, o2ib1,...)
1.8 .1.2 Sect ion 2.4 .3.1b Confi g u ri ng m u l ti p le o2ib LNETs per IB interface with OFED
Insert the following section between 2.4.3.1 and 2.4.3.2, after 2.4.3.1a above:
The purpose of configuring multiple o2ib LNETs per server IB interface is to allow SFS client nodes that are
configured with multiple IB interfaces to distribute the Lustre traffic across multiple LNETs to multiple server
nodes.
This is a method of increasing the per client node aggregate bandwidth. This is often desired on large SMP
nodes. At the SFS server side, this requires adding multiple IB interface aliases on the same physical IB
interface. There is no requirement for extra physical IB interfaces on the SFS servers side. But if there are
multiple IB interfaces, each of them can have multiple aliases if desired.
Configuring additional IB interface aliases requires a new unique range of IPoIB addresses for each alias.