scope:

A standard application programming interface (API) defines a scope within which, and a grammar by which it is possible to write application software without attention to vendor-specific infrastructure behavior. This standard specifies a standard API the scope of which is management of Fibre Channel (FC) and Serial Access SCSI (SAS) HBAs, and the use of FC and SAS capabilities for discovery and management of the components of the respective fabric or domain. This proposed standard defines interfaces to the following capabilities:

a) Monitoring and Control of Attributes and Capabilities of HBAs and End Ports.

b) Monitoring of HBA, End port, and Storage access traffic statistics.

c) Timely and selective reporting of HBA and fabric or domain configuration, status, and statistical events.

d) Access to Fibre Channel Fabric Services (see FC-FS-3).

e) Access to the Fibre Channel Extended Link Services necessary to comply with the manageability profile for HBAs recommended in FC-DA-2 (see FC-DA-2).

f) Access to SAS Management Protocol (SMP) Services for Expander Management (see SPL).

g) Discovery and Enumeration of storage resources availablue using FCP-4 (see FCP-4), SSP (see SPL), and STP (see SPL).

The primary goal of this standard is to provide a successor to SM-HBA that adds support for new Fibre Channel architecture features, including

a) Fibre Channel Virtual Fabrics;

b) Fibre Channel N_Port Virtualization;

c) virtual I/O interfaces to HBAs (e.g., PCI I/O Virtualization, see SRIOV 1.1); and

d) Fibre Channel over Ethernet (see FC-BB-6).

This standard is derived from SM-HBA (see SM-HBA), carrying forward many SM-HBA functions unchanged, while removing obsolete features and replacing functions that are inconsistent with new Fibre Channel architecture features. Although this standard does not obsolete SM-HBA as a reference for existing implementations, it is intended to replace SM-HBA as the recommended basis for new implementations.

Features of SM-HBA omitted from this standard include:

a) reporting of support for Hunt Groups, Multicast, and Class 1 Service;

b) N_Port characteristics specific to Single-Byte Command Codes;

c) mapping FC-HBA to InfiniBand^tm; and

d) polled event notification.

Functions of SM-HBA removed or replaced in this standard include:

a) HBA_RegisterLibrary;

b) HBA_RegisterLibraryV2;

c) HBA_GetWrapperLibraryAttributes;

d) HBA_GetVendorLibraryAttributes;

e) HBA_ResetStatistics;

f) HBA_GetAdapterName;

g) HBA_OpenAdapter;

h) HBA_OpenAdapterByWWN;

i) HBA_CloseAdapter;

j) HBA_RefreshInformation;

k) HBA_RefreshAdapterConfiguration;

l) HBA_GetAdapterAttributes;

m) HBA_GetAdapterPortAttributes;

n) HBA_GetDiscoveredPortAttributes;

o) HBA_GetPortAttributesByWWN;

p) HBA_GetPortStatistics;

q) HBA_GetFC4Statistics;

r) HBA_GetBindingCapability;

s) HBA_GetBindingSupport;

t) HBA_Support;

u) HBA_GetFcpTargetMapping;

v) HBA_GetFcpTargetMappingV2;

w) HBA_GetFcpPersistentBinding;

x) HBA_GetPersistentBindingV2;

y) HBA_SetPersistentBindingV2;

z) HBA_RemovePersistentBinding;

aa) HBA_RemoveAllPersistentBindings;

ab) HBA_GetFCPStatistics;

ac) HBA_SendScsiInquiry;

ad) HBA_ScsiInquiryV2;

ae) HBA_SendReportLUNs;

af) HBA_ScsiReportLunsV2;

ag) HBA_SendReadCapacity;

ah) HBA_ScsiReadCapacityV2;

ai) HBA_GetSBTargetMapping;

aj) HBA_GetSBStatistics;

ak) HBA_SBDskGetCapacity;

al) HBA_SendRPL;

am)HBA_SendRPS;

an) HBA_SendCTPassThru;

ao) HBA_SendRNID;

ap) HBA_GetEventBuffer

aq) HBA_RegisterForAdapterAddEvents

ar) HBA_RegisterForAdapterEvents

as) HBA_RegisterForAdapterPortEvents

at) HBA_RegisterForAdapterPortStatEvents

au) HBA_RegisterForTargetEvents

This standard is to be used in conjunction with the Fibre Channel, Serial Attached SCSI and SCSI families of standards. At the time this standard was written its relationship to those standards was as shown in figure 1.

For standards in the Fibre Channel, Serial Attached SCSI and SCSI families of standards see the web sites of INCITS Technical Committees