User guide
3–InfiniBand
®
Cluster Setup and Administration
QLogic Distributed Subnet Administration
IB0054606-02 A 3-13
Virtual Fabrics and the Distributed SA
The IBTA standard states that applications can be identified by a Service ID (SID).
The QLogic Fabric Manager uses SIDs to identify applications. One or more
applications can be associated with a Virtual Fabric using the SID. The Distributed
SA is designed to be aware of Virtual Fabrics, but to only store records for those
Virtual Fabrics that match the SIDs in the Distributed SA's configuration file. The
Distributed SA recognizes when multiple SIDs match the same Virtual Fabric and
will only store one copy of each path record within a Virtual Fabric. SIDs that
match more than one Virtual Fabric will be associated with a single Virtual Fabric.
The Virtual Fabrics that do not match SIDs in the Distributed SA's database will be
ignored.
Configuring the Distributed SA
In order to absolutely minimize the number of queries made by the Distributed SA,
it is important to configure it correctly, both to match the configuration of the Fabric
Manager and to exclude those portions of the fabric that will not be used by
applications using the Distributed SA. The configuration file for the Distributed SA
is named /etc/sysconfig/iba/qlogic_sa.conf.
Default Configuration
As shipped, the QLogic Fabric Manager creates a single virtual fabric, called
“Default” and maps all nodes and Service IDs to it, and the Distributed SA ships
with a configuration that lists a set of thirty-one SIDs, 0x1000117500000000
through 0x100011750000000f and 0x1 through 0xf. This results in an
arrangement like the one shown in Figure 3-2
Figure 3-2. Distributed SA Default Configuration
9LUWXDO)DEULF³'HIDXOW´
3NH\[IIII
6,'5DQJH[[IIIIIIIIIIIIIIII
,QILQLEDQG)DEULF
9LUWXDO)DEULF³'HIDXOW´
3NH\[IIII
6,'5DQJH[[I
6,'5DQJH[[I
'LVWULEXWHG6$