Scan for new SAN with FC on suse 9 (SLES9) Post: 302933300

3 More Discussions You Might Find Interesting

1. Solaris

Thoughts/experiences of SAN attaching V880 to EMC SAN

Hi everyone, I wonder if I can canvas any opinions or thoughts (good or bad) on SAN attaching a SUN V880/490 to an EMC Clarion SAN? At the moment the 880 is using 12 internal FC-AL disks as a db server and seems to be doing a pretty good job. It is not I/O, CPU or Memory constrained and the...

2. AIX

IBM SAN TO SAN Mirroring

Has anyone tried SAN to SAN mirroring on IBM DS SAN Storage. DS5020 mentions Enhanced Remote Mirror to multi-LUN applications I wonder if Oracle High availibility can be setup using Remote Mirror option of SAN ?

3. Filesystems, Disks and Memory

Faster way: SAN hd to SAN hd copying

hi! i got a rhel 6.3 host that already have an xfs filesystem mounted from a SAN (let's call it SAN-1) whose size is 9TB. i will be receiving another SAN (let's call it SAN-2) storage of 15TB size. this new addition is physically on another SAN storage. SAN-1 is on a Pillar storage while the new...

LEARN ABOUT HPUX

hbaapi

hbaapi(3C)																hbaapi(3C)

NAME

       hbaapi - Fibre Channel Storage Network Industry Association Host Bus Adapter Application Programming Interface (FC SNIA HBA API)

DESCRIPTION

       The  Common  HBA  API  provides a consistent HBA standard interface for accessing information in a Fibre Channel Storage Area Network (SAN)
       that would be implemented across vendors as a standard 'C' API supported by vendor specific library instances.

       This API library is thread-safe, but threads should not be cancelled when execution is in the API.

       The following functions are available in the API for managing a Fibre Channel HBA.  This API would be exposed to upper  level  applications
       to control SAN functionality.

       Please refer to for details on structures used.

	    01.
	    02.
	    03.
	    04.
	    05.
	    06.
	    07.

	    08.
	    09.
	    10.
	    11.
	    12.

	    13.
	    14.
	    15.
	    16.
	    17.

	    18.
	    19.

	    FCP Information Functions require that the applications calling them
		  have an effective user id as that of the root user (euid = 0).

	    20.
	    21.
	    22.

	    SCSI Information Functions require that the applications calling them have an effective user id as that of the root user (euid = 0).

	    23.
	    24.

FILES

       Contains the related data structures and definitions as in

AUTHOR

       These APIs were developed by Hewlett-Packard Company.

SEE ALSO

       HBA_GetVersion(3C),  HBA_LoadLibrary(3C),  HBA_FreeLibrary(3C),	HBA_GetNumberOfAdapters(3C),  HBA_GetAdapterName(3C), HBA_OpenAdapter(3C),
       HBA_CloseAdapter(3C), HBA_GetAdapterAttributes(3C), HBA_GetAdapterPortAttributes(3C),  HBA_GetPortStatistics(3C),  HBA_GetDiscoveredPortAt-
       tributes(3C),  HBA_GetPortAttributesByWWN(3C),  HBA_SendCTPassThru(3C),	HBA_GetEventBuffer(3C),  HBA_SetRNIDMgmtInfo(3C), HBA_GetRNIDMgmt-
       Info(3C), HBA_SendRNID(3C), HBA_GetFcpTargetMapping(3C), HBA_GetFcpPersistentBinding(3C), HBA_SendScsiInquiry(3C),  HBA_SendReportLUNs(3C),
       HBA_SendReadCapacity(3C), HBA_RefreshInformation(3C), HBA_ResetStatistics(3C).

																	hbaapi(3C)