Product specifications

D – Multi-Subnet Fabrics
D000006-000 Rev A D-5
Q
❥ (All): Create the allhosts file per the instructions. Next, create additional files
per subnet that list all the hosts in each subnet including the IB management
node.
❥ (All): “Verify Hosts via Ethernet ping” on page 4-4 can be performed per the
instructions.
❥ (All): “Summary of Fabric Components” on page 4-9 is not presently supported
for IB management nodes connected to multiple fabrics. Instead manually run:
iba_report -d 0 -h x -p y
where x and y specify the applicable HCA and port to select the desired subnet.
Repeat for each subnet.
❥ (Host): “Show Status of Host IB Ports” on page 4-9 may be run per the
instructions.
❥ (All): However, instead it is recommended to run:
iba_report -i 10 -o errors -o slowlinks -h x -p y
where x and y specify the applicable HCA and port to select the desired
subnet. Repeat for each subnet.
❥ (Host): “Verify Hosts see each other” on page 4-9 can be run for each subnet
by using the allhosts files specific to each subnet (i.e., those only listing hosts
in a single subnet).
❥ (Host): “Verify Hosts ping via IPoIB” on page 4-9 and (Linux): “Refresh SSH
Known Hosts” on page 4-9 may be run per the instructions.
❥ (Host): “Check MPI Performance” on page 4-10 can be run for each subnet by
using the allhosts files specific to each subnet (i.e., those listing only the hosts
in a single subnet).
“Complete Installation of additional IB Management Nodes” on page 3-18 can be
performed as per the instructions. When copying Fast Fabric configuration files to
the additional IB management nodes, be sure to also copy the additional hosts,
chassis and allhosts files created per subnet.
NOTE: In assymetrical configurations where the IB management nodes are not
all connected to the same set of subnets, the files copied to each
management node may need to be slightly different. For example,
configuration files for fabric_analysis indicating different port
numbers or host files used for Fast Fabric and MPI may need to list
different hosts.
“Configure and Initialize Health Check Tools” on page 3-19 can be performed per
the instructions. In addition, create a /etc/sysconfig/iba/ports file listing the
IB management node local HCAs and ports that are connected to a unique subnet.
When running fabric_analysis or all_analysis, the default is to use the
ports file. If desired, the -p and -t options or the PORTS/PORTS_FILE environment