Fabric Manager Users Guide, Version 6.1, Revision A - QLogic

4–Virtual Fabrics
Configuration
Each Application, DeviceGroup, and VirtualFabric must be given a unique name
that is used to reference it. Applications, DeviceGroups, and VirtualFabrics may
be defined in the Common or Fm sections. Those defined in the Common section
apply to all Fm Instances. Those defined in an Fm section describe additional
Applications, DeviceGroups, or VirtualFabrics that are specific to the given Fm
instance.
Application Parameters
Applications are defined within the Applications section. This section contains
zero or more Application sections.
The layout is as follows:
Each Application section has zero or more ServiceIDs subsections and/or
MGIDs subsections. These are matched against PathRecord and Multicast SA
queries so that the returned SLID/DLID, PKey, SL, and so on are appropriate for
the vFabric that contains the application(s).
ServiceIDs subsections are 64-bit values that identify applications within a
PathRecord query. In many ways ServiceIDs are InfiniBand’s equivalent of TCP
socket ports. ServiceIDs are typically used within the InfiniBand Communication
Manager protocol to identify the application making a connection request. When
an application issues a PathRecord query to the SA, the ServiceID in the query is
compared against the ServiceID subsections in the various VirtualFabrics
sections.
ServiceIDs are assigned by application writers and standards bodies such as
IBTA and IEEE. Consult with the application supplier to determine the Service IDs
used by the application.
InfiniBand Multicast GIDs (MGIDs) are 128-bit values that identify multicast
groups for Unreliable Datagram applications such as IPoIB. MGIDs are
represented as two 64-bit values separated by a colon (:). For example:
0xabc:0x123567
This way of representing 128-bit values is the same as used in other FastFabric
Toolset commands such as iba_saquery, iba_showmc, and so on.
Applications not used in any vFabric have no effect.
IB0054608-01 B 4-3