HP StorageWorks Scalable File Share Release Notes - Version 2.3

Documentation updates and corrections 1–23
Once confirmed and saved, the IB configuration for the above example will be:
CAUTION: In the show network output above, the Name column refers to SFS InfiniBand interconnect names in
the SFS system database. These are always called ibN, for both vib and o2ib interconnect types.
They are not the same as the underlying ibN[:M] IPoIB interfaces used by o2ib interconnects, and listed in the Device
column. Therefore, in a dual-o2ib server rail scenario, it is possible to have an SFS network name ib2 corresponding to
an IPoIB interface ib1.
The LNET parameter is normally set automatically by the sfs server. If the default value is not satisfactory—
for example, in a multiple server environment—then it can be overridden using the SFS lustre.net or
lnet.ip2nets attributes. See section 7.11.2 and 7.11.2a for details.
If there are more than two client rails, repeat the menu choice 3) Add IB Interface as many times as
necessary.
1.8 . 2.5 Section 7.11.1a Configuring multiple LNETS
Insert this section between sections 7.11.1 and 7.11.2.
If your SFS system is configured the standard way, with a single IB fabric and single IB interfaces on the
client node, this section is not necessary.
Starting with version V2.3, SFS allows to configure multiple o2ib LNETs when using OFED. There are two
ways of configuring multiples LNETs, each with a different purpose. Both can be configured at the same time:
Client Server
Interface ib0 ib0
Type Physical Physical
Inet o2ib0 o2ib0
IP address 172.23.184.1 172.23.184.100
NetMask 255.255.255.0 255.255.255.0
Part. key 0xFFFF 0xFFFF
Interface ib1 ib0:0
Type Physical Alias
Inet o2ib1 o2ib1
IP address 172.23.185.1 172.23.185.100
NetMask 255.255.255.0 255.255.255.0
Part. key 0xFFFF 0xFFFF
sfs> show network
Name Device Role Lnet
---- ------ ---- ----
ib0 ib0 interconnect o2ib0
ib0 ib0:0 interconnect o2ib0
mp0 n/a console
nic1 eth0 management
nic2 eth1 interconnect tcp0