DragonFly On-Line Manual Pages

Search: Section:  


ISP(4)                DragonFly Kernel Interfaces Manual                ISP(4)

NAME

isp - Qlogic based SCSI and FibreChannel SCSI Host Adapters

SYNOPSIS

To compile this driver into the kernel, place the following lines in your kernel configuration file: device scbus device isp device ispfw Alternatively, to load the driver as a module at boot time, place the following lines in loader.conf(5): isp_load="YES" isp_1040_load="YES" isp_1040_it_load="YES" isp_1080_load="YES" isp_1080_it_load="YES" isp_12160_load="YES" isp_12160_it_load="YES" isp_2100_load="YES" isp_2200_load="YES" isp_2300_load="YES" isp_2322_load="YES" isp_2400_load="YES" isp_2400_multi_load="YES" isp_2500_load="YES" isp_2500_multi_load="YES"

DESCRIPTION

This driver provides access to SCSI or FibreChannel devices. SCSI features include support for Ultra SCSI and wide mode transactions for SCSI, Ultra2 LVD (for the ISP1080 and ISP1280), and Ultra3 LVD (for the ISP12160). Fibre Channel support uses FCP SCSI profile for FibreChannel. and utilizes Class 3 and Class 2 connections (Qlogic 2100 is Class 3 only, minor patches to the Qlogic 2200 to force Class 2 mode). Support is available for Public and Private loops, and for point-to-point connections (Qlogic 2200 only). The newer 2-Gigabit cards (2300, 2312, 2322) and 4-Gigabit (2422, 2432) are also supported. Command tagging is supported for all (in fact, FibreChannel requires tagging). Fabric support is enabled by default for other than 2100 cards. Fabric support for 2100 cards has been so problematic and these cards are so old now that it is just not worth your time to try it.

FIRMWARE

Firmware is available if the appropriate firmware module is loaded during bootstrap (see ispfw(4)). It is strongly recommended that you use the firmware supplied with DragonFly as it is the most likely to have been tested with this driver.

HARDWARE

Cards supported by the isp driver include: ISP1000 SBus Fast Wide, Ultra Fast Wide cards, Single Ended or Differential cards. ISP1020 Qlogic 1020 Fast Wide and Differential Fast Wide PCI cards. ISP1040 Qlogic 1040 Ultra Wide and Differential Ultra Wide PCI cards. Also known as the DEC KZPBA-CA (single ended) and KZPBA-CB (HVD differential). Qlogic 1240 Qlogic 1240 Dual Bus Ultra Wide and Differential Ultra Wide PCI cards. Qlogic 1020 Qlogic 1020 SCSI cards. Qlogic 1040 Qlogic 1040 Ultra SCSI cards. Qlogic 1080 Qlogic 1280 LVD Ultra2 Wide PCI cards. Qlogic 1280 Qlogic 1280 Dual Bus LVD Ultra2 Wide PCI cards. Qlogic 12160 Qlogic 12160 Dual Bus LVD Ultra3 Wide PCI cards. Qlogic 210X Qlogic 2100 and 2100A Copper and Optical Fibre Channel Arbitrated Loop (single, dual). Qlogic 220X Qlogic 2200 Copper and Optical Fibre Channel Arbitrated Loop PCI cards (single, dual, quad). Qlogic 2300 Qlogic 2300 Optical Fibre Channel PCI cards. Qlogic 2312 Qlogic 2312 Optical Fibre Channel PCI cards. Qlogic 234X Qlogic 234X Optical Fibre Channel PCI cards (2312 chipset, single and dual attach). Qlogic 2322 Qlogic 2322 Optical Fibre Channel PCIe cards. Qlogic 200 Dell Branded version of the QLogic 2312 Fibre Channel PCI cards. Qlogic 2422 Qlogic 2422 Optical Fibre Channel PCI cards (4 Gigabit) Qlogic 2432 Qlogic 2432 Optical Fibre Channel PCIe cards (4 Gigabit)

CONFIGURATION OPTIONS

Target mode support may be enabled with the options ISP_TARGET_MODE option.

BOOT OPTIONS

The following options are switchable by setting values in /boot/device.hints. They are: hint.isp.0.disable A hint value to disable driver in kernel. hint.isp.0.fwload_disable A hint value to disable loading of firmware ispfw(4). hint.isp.0.prefer_memmap A hint value to use PCI memory space instead of I/O space access for. hint.isp.0.prefer_iomap A hint value to use PCI I/O space instead of Memory space access for. hint.isp.0.ignore_nvram A hint value to ignore board NVRAM settings for. Otherwise use NVRAM settings. hint.isp.0.fullduplex A hint value to set full duplex mode. hint.isp.0.topology A hint value to select topology of connection. Supported values are: lport Prefer loopback and fallback to point to point. nport Prefer point to point and fallback to loopback. lport-only Loopback only. nport-only Point to point only. hint.isp.0.portwwn This should be the full 64 bit World Wide Port Name you would like to use, overriding the value in NVRAM for the card. hint.isp.0.nodewwn This should be the full 64 bit World Wide Node Name you would like to use, overriding the value in NVRAM for the card. hint.isp.0.iid A hint to override or set the Initiator ID or Loop ID. For Fibre Channel cards in Local Loop topologies it is strongly recommended that you set this value to non-zero. hint.isp.0.role A hint to define default role for isp instance (target, initiator, both). hint.isp.0.debug A hint value for a driver debug level (see the file /usr/src/sys/dev/isp/ispvar.h for the values. By default, the driver will use MSI if it is supported. This behavior can be turned off by setting the following tunable: hw.isp.msi.enable=0

SYSCTL OPTIONS

dev.isp.N.loop_down_limit This value says how long to wait in seconds after loop has gone down before giving up and expiring all of the devices that were visible. The default is 300 seconds (5 minutes). A separate (nonadjustable) timeout is used when booting to not stop booting on lack of FC connectivity. dev.isp.N.gone_device_time This value says how long to wait for devices to reappear if they (temporarily) disappear due to loop or fabric events. While this timeout is running, I/O to those devices will simply be held. dev.isp.N.wwnn This is the readonly World Wide Node Name value for this port. dev.isp.N.wwpn This is the readonly World Wide Port Name value for this port.

SEE ALSO

da(4), intro(4), ispfw(4), sa(4), scsi(4)

AUTHORS

The isp driver was written by Matthew Jacob originally for NetBSD at NASA/Ames Research Center.

BUGS

The driver currently ignores some NVRAM settings. Target mode support is not completely reliable yet. It works reasonably well for Fibre Channel, somewhat well for Qlogic 1040 cards, but does not yet work for the other cards (due to last minute unannounced changes in firmware interfaces). DragonFly 6.3-DEVELOPMENT June 28, 2017 DragonFly 6.3-DEVELOPMENT

Search: Section: