Q
(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 listing only 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 that were created per subnet.
NOTE:
"Configure and Initialize Health Check Tools" on page 3-19 can be performed as
per the instructions. Additionally, create a /etc/sysconfig/iba/ports file
listing each of the IB management node local HCAs and ports that are connected
to a unique subnet. When running fabric_analysis or all_analysis, the default will
be to use the ports file. If desired, the -p and -t options or the
PORTS/PORTS_FILE environment variables may be used to specify all the HCAs
and ports on the IB management node such that all subnets are checked. Similarly,
the esm_chasssis and chassis files used should list all relevant SilverStorm IB
chassis in all subnets.
"Running HPL" on page 3-20 can be run for each subnet by creating mpi_hosts
files specific to each subnet (i.e., only listing hosts in a single subnet).
"Upgrading IB software" on page 3-21 can be performed as per the instructions.
D.2
Overlapping Subnets
If multiple IB components are common between subnets (in addition to the IB
management nodes), Fast Fabric may be used to assist in server installation and
D000006-000 Rev A
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 may indicate different port
numbers or host files used for Fast Fabric and MPI may need to list
different hosts.
D – Multi-Subnet Fabrics
D-3
Need help?
Do you have a question about the Fast Fabric and is the answer not in the manual?
Questions and answers