fp - Sun Fibre Channel port driver
The fp driver is a Sun fibre channel nexus driver that enables fibre channel topology discovery, device discovery, fibre channel adapter port management and other capabilities through well-defined fibre channel adapter driver interfaces.
The fp driver requires the presence of a fabric name server in fabric and public loop topologies to discover fibre channel devices. In private loop topologies, the driver discovers devices by performing PLOGI to all valid AL_PAs, provided that devices do not participate in LIRP and LILP stages of loop initialization. The fp driver also discovers devices in N_Port point-to-point topologies.
The fp driver is configured by defining properties in the fp.conf file. Note that you must reboot the system to have any changes you make to fp.conf take effect. The fp driver supports the following properties:
mpxio-disable
name="fp" parent="/pci@8,600000/SUNW,qlc@4" port=0 mpxio-disable="yes";
manual_configuration_only
pwwn-lun-blacklist
# # pwwn-lun-blacklist= # "target-port-wwn,lun-list" # # To prevent LUNs 1 and 2 from being configured for target # port 510000f010fd92a1 and target port 510000e012079df1, set: # # pwwn-lun-blacklist= # "510000f010fd92a1,1,2", # "510000e012079df1,1,2"; #
/kernel/drv/fp
/kernel/drv/amd64/fp
/kernel/drv/sparcv9/fp
/kernel/drv/fp.conf
See attributes(5) for descriptions of the following attributes:
|
cfgadm_fp(1M), prtconf(1M), stmsboot(1M), driver.conf(4), attributes(5), fcp(7D), fctl(7D), scsi_vhci(7D)
Writing Device Drivers
Fibre Channel Physical and Signaling Interface (FC-PH) ANSI X3.230: 1994
Fibre Channel Generic Services (FC-GS-2) Project 1134-D
Fibre Channel Arbitrated Loop (FC-AL) ANSI X3.272-1996
Fibre Channel Protocol for SCSI (FCP) ANSI X3.269-1996
SCSI-3 Architecture Model (SAM) Fibre Channel Private Loop SCSI Direct Attach (FC-PLDA) ANSI X3.270-1996
SCSI Direct Attach (FC-PLDA) ANSI X3.270-1996
SCSI Direct Attach (FC-PLDA) NCITS TR-19:1998
Fabric Loop Attachment (FC-FLA), NCITS TR-20:1998
In N_Port point-to-point topologies, FCP error recovery does not work across events such as link bounce/cable pull. I/O to devices with FCP-2/FCP-3 support (for example, FC tape drives) will be disrupted by such events.
Закладки на сайте Проследить за страницей |
Created 1996-2024 by Maxim Chirkov Добавить, Поддержать, Вебмастеру |