HP StorageWorks Scalable File Share System Installation and Upgrade Guide Version 2.2

Planning the networks 2–21
2.4.3.1.2 Configuration 2—using the private partitions for the HP SFS traffic
In this configuration, the HP SFS traffic uses all of the private partitions; therefore, the HP SFS servers need
to join all partitions.
Note that in this configuration:
• The nodes in cluster A cannot communicate with the nodes in cluster B.
• The nodes in cluster A and the nodes in cluster B can communicate with the HP SFS servers.
Table 2-4 shows the partition table at the switch.
Table 2-5 shows how the IPoIB interfaces could be configured where one network is configured for each
partition.
As explained in Section 2.4.3, the connection to the HP SFS servers can only be established using the IP
address of the first IPoIB interface of the HP SFS servers (172.32.1.n). This is why there must be a specific
IP mask on the nodes in cluster B to route the 172.32.1 network traffic over the 172.32.2 network interface.
The ipoib1 interface on the server nodes is still required to authorize incoming traffic for messages on the
0x8002 Pkey.
Table 2-6 shows how the IPoIB interfaces could be configured where a single network is shared by multiple
partitions.
Table 2-4 Configuration 2—Partition table at the switch
Host Pkey0 Pkey1 Pkey2
Sfs1 0x7fff 0x8001 0x8002
Sfs2 0x7fff 0x8001 0x8002
HostA1 0x7fff 0x8001 N/A
HostA2 0x7fff 0x8001 N/A
HostB1 0x7fff 0x8002 N/A
HostB2 0x7fff 0x8002 N/A
Table 2-5 Configuration 2—IPoIB interfaces where
one network is configured for each partition
Hosts ipoib0 ipoib1
Pkey IP Mask Pkey IP Address Mask
Sfs1 0x8001 172.32.1.3 Default 0x8002 172.32.2.3 Default
Sfs2 0x8001 172.32.1.4 Default 0x8002 172.32.2.4 Default
HostA1 0x8001 172.32.1.1 Default N/A N/A N/A
HostA2 0x8001 172.32.1.2 Default N/A N/A N/A
HostB1 0x8002 172.32.2.1 255.255.0.0 N/A N/A N/A
HostB2 0x8002 172.32.2.2 255.255.0.0 N/A N/A N/A