# The SCSI ID to bind to consists of two parts, the lpfc interface
# to bind to, and the target number for that interface.
# Thus lpfc0t2 specifies target 2 on interface lpfc0.
# NOTE: Target ids, with all luns supported, must also be in sd.conf.
# Here are some examples:
# WWNN SCSI ID
# fcp-bind-WWNN="2000123456789abc:lpfc1t0",
# "20000020370c27f7:lpfc0t2";
#
# WWPN SCSI ID
# fcp-bind-WWPN="2100123456789abc:lpfc0t0",
# "21000020370c2855:lpfc0t1",
# "2100122222222222:lpfc2t2nd-WWPN="2100123456789abc:lpfc0t0",
# "21000020370c2855:lpfc0t1",";
#
fcp-bind-WWPN="500000e0d0100386:lpfc0t16",
"500000e0d0100306:lpfc1t16";
# DID SCSI ID
# fcp-bind-DID="0000ef:lpfc0t3";
# BEGIN: LPUTIL-managed Persistent Bindings
# If automap is set, SCSI IDs for all FCP nodes without
# persistent bindings will be automatically generated.
# If new FCP devices are added to the network when the system is down,
# there is no guarantee that these SCSI IDs will remain the same
# when the system is booted again.
# The bind method of the port is used as the binding method of
# automap devices to preserve SCSI IDs between link down and link up.
# If automap is 0, only devices with persistent bindings will be
# recognized by the system.
#automap=1;
#automap=0;
lpfc0-automap=0;
lpfc1-automap=0;
# lun-queue-depth [1 to 128] - The default value lpfc will use to
# limit the number of outstanding commands per FCP LUN. This value
# is global, affecting each LUN recognized by the driver, but may be
# overridden on a per-LUN basis (see below). RAID arrays may want
# to be configured using the per-LUN tunable throttles.
lun-queue-depth=20;
# tgt-queue-depth [0 to 10240] - The default value lpfc will use to
# limit the number of outstanding commands per FCP target. This value
# is global, affecting each target recognized by the driver, but may be
# overridden on a per-target basis (see below). RAID arrays may want
# to be configured using the per-target tunable throttles. A value
# of 0 means don't throttle the target.
tgt-queue-depth=512;
# lpfcNtM-lun-throttle: the maximum number of outstanding commands to
# permit for each LUN of an FCP target that supports multiple LUNs.
# The default throttle for the number of commands outstanding to a single
# LUN of a multiple-LUN target is lun-queue-depth. For a target that
For direct connections, lpfc0-automap=1;
For both direct connections and switch connections, add this setting.
For an ETERNUS DX60 S2/DX80 S2/DX90 S2, this setting is not required.
For direct connections, this setting is not required.
# can support multiple LUNs, it may be useful to specify a LUN throttle
# that differs from the default.
# Example: lpfc0t17-lun-throttle=48;
# says that each LUN on target 17, interface lpfc0 should be allowed
# up to 48 simultaneously outstanding commands.
#lpfc1t39-lun-throttle=10;
#lpfc0t40-lun-throttle=30;
# lpfcNtM-tgt-throttle: the maximum number of outstanding commands to
# permit for a FCP target.
# By default, target throttle is disabled.
# Example: lpfc0t17-tgt-throttle=48;
# says that target 17, interface lpfc0 should be allowed
# up to 48 simultaneously outstanding commands.
#lpfc1t39-tgt-throttle=10;
#lpfc0t40-tgt-throttle=30;
lpfc0t16-tgt-throttle=40;
lpfc1t16-tgt-throttle=40;
# no-device-delay [0 to 30] - determines the length of
# the interval between deciding to fail back an I/O because there is no way
# to communicate with its particular FCP device (e.g., due to device failure)
# and the actual fail back. A value of zero implies no delay whatsoever.
# Cautions: (1) This value is in seconds.
For an ETERNUS DX60 S2/DX80 S2/DX90 S2, this setting is required.
For both direct connections and switch connections, add this setting.
For models shown below, confirm that the value is set to "512".
࣭
ETERNUS DX400 S2 series
࣭
ETERNUS DX8000 S2 series
For models shown below, this setting is not required.
࣭
ETERNUS DX60 S2/DX80 S2/DX90 S2
FUJITSU Storage ETERNUS DX, ETERNUS AF Configuration Guide -Server Connection- (Fibre Channel) for Oracle Solaris
To Next Page
Loading...
