HBA_BIND_TYPE

The HBA_BIND_TYPE WMI class qualifier indicates the ability of an HBA and its miniport driver to provide a specific set of features related to persistent binding.

The following table lists the qualifier names and the meaning of each name:

Types	Meaning
HBA_CAN_BIND_TO_D_ID	Indicates the ability of an HBA and its miniport driver to accept a persistent binding that identifies the Fibre Channel target port by its address identifier.
HBA_CAN_BIND_TO_WWPN	Indicates the ability of an HBA and its miniport driver to accept a persistent binding that identifies the Fibre Channel target port by its worldwide port name (WWPN).
HBA_CAN_BIND_TO_WWNN	Indicates the ability of an HBA and its miniport driver to accept a persistent binding that identifies a Fibre Channel target device (not a target port) by its worldwide node name (WWNN). The implicit ambiguity in this means of identifying devices on multiport devices is intentional. It allows the HBA and/or the fabric to resolve the ambiguity in a vendor-specific manner.
HBA_CAN_BIND_TO_LUID	Indicates the ability of an HBA and its miniport driver to accept a persistent binding that identifies a Fibre Channel logical unit by the identification descriptor derived from SCSI inquiry data for the logical unit.
HBA_CAN_BIND_ANY_LUNS	Indicates the ability of an HBA and its miniport driver to accept persistent binding settings that specify both the operating system and Fibre Channel logical unit number.
HBA_CAN_BIND_TARGETS	Indicates the ability of an HBA and its miniport driver to generate persistent bindings between Fibre Channel protocol (FCP) identifiers for logical units and the information that the operating system uses to identify logical units, such as the bus and target numbers that are stored in the HBAScsiID.
HBA_CAN_BIND_AUTOMAP	Indicates the ability of an HBA and its miniport driver to automatically generate target mappings and persistent bindings for all discovered storage resources. If this capability is not indicated or is disabled, the only bindings allowed are those that are explicitly configured in the operating system. Explicit configuration of bindings facilitates logical unit number (LUN) masking.
HBA_CAN_BIND_CONFIGURED	Indicates the ability of an HBA and its miniport driver to accept dynamic configuration of persistent bindings.

By including Hbaapi.h your software will have access to a series of symbolic constants that correspond to the type names in the previous table. The definitions for these symbolic constants is not included in Hbapiwmi.h (the file that the WMI tool suite generates when it compiles).