iscsi.conf.sample

iscsi-init LINUX boot

# iSCSI configuration file - see iscsi.conf(5) of linux-iscsi initiator

# Authentication Settings
# -----------------------
# You may configure a default Username and Password to use for CHAP
# authentication by specifying the Global username and password parameters
# in the format as mentioned below.
#
# Example:
#
#Username=alice
#Password=nty57nbe
#      or
#OutgoingUsername=alice
#OutgoingPassword=nty57nbe  
#
# The "OutgoingUsername" will specify the username to be sent to the target
# for login authentication. The "OutgoingPassword" is the CHAP secret password
# to be used when sending challenge responses to the target.
# 
# You can configure 2 WAY authentication to enable the authentication of the
# initiator by the target and vice-versa. The "OutgoingUsername" and "Outgoing
# Password" fields specify the initiator authentication and "IncomingUsername"
# and "IncomingPassword" can be used for target authentication.
#
# The "IncomingUsername" will specify the username that must be received from
# target if login authentication occurs. The "IncomingPassword" is the CHAP
# secret to be used when verifying challenge responses from the target.
# The "OutgoingPassword" and "IncomingPassword"  fields should be unique.
#
# Example:
#
#OutgoingUsername=alice
#OutgoingPassword=nty57nbe
#
#IncomingUsername=alice3
#IncomingPassword=nty57nbe3

# CRC Settings
# ------------
# You may configure CRC32C digest checking for Header and Data part of
# iSCSI PDUs. To enable the CRC32C checking you can specify 
# "HeaderDigest=Always". "HeaderDigest=Never" will disable the CRC32C digest
# checking for the ISCSI Headers. You can specify the preference for the 
# HeaderDigest values by putting "HeaderDigest=Prefer-On" or 
# "HeaderDigest=Prefer-Off". In these cases the driver will take the values 
# offered by the target during the text key negotiation. The same logic holds 
# for DataDigest key.
#
#HeaderDigest=Always
#HeaderDigest=Never
#HeaderDigest=Prefer-on
#HeaderDigest=Prefer-off
#
#DataDigest=Always
#DataDigest=Never
#DataDigest=Prefer-on
#DataDigest=Prefer-off
#

# Connection Timeout Settings
# --------------------------- 
# All the timeout parameters take the value in seconds.
#
# LoginTimeout can be configured to specify the time to wait for a login
# PDU to be sent or received before failing the login on a particular
# connection due to a login failure. 
#
#LoginTimeout=15
#
# AuthTimeout can be configured to specify the time to wait for a login
# PDU carrying Authentication info to be sent or received before failing the
# login on a particular connection due to authentication failure.
#
#AuthTimeout=45
#
# IdleTimeout setting can be used to specify the length of time a connection
# may remain idle not expecting a response from the target and before checking
# the connection with a ping.
#
#IdleTimeout=60
#
# PingTimeout is the length of time to wait for a ping response before assuming
# the connection is dead and replacing it with a new one.
#
#PingTimeout=5

# SESSION TIMEOUT SETTINGS
# ------------------------
# To globally specify the length of time to wait for session re-establishment
# before failing SCSI commands back to the application, uncomment the
# following line:
# 
#ConnFailTimeout=<number>
#
# where <number> is in seconds. A setting of "0" will result in commands never
# being failed back due to connection failure.
#
# The global session timeout settings can be overridden on a per target name
# basis. An example of setting the "ConnFailTimeout" value to 5 seconds for
# just target iqn.1987-05.com.cisco:00.0d1d898e8d66.t0 would be:

# iSCSI Operational Parameter settings
# ------------------------------------
# InitialR2T takes a boolean value. When negotiated to "no", the initiator has
# an implied initial R2T for FirstBurstLength at offset 0. When set to "yes"
# the initiator must wait for an R2T before sending any data.
#
#InitialR2T=yes
#InitialR2T=no
#
# ImmediateData takes a boolean value. When negotiated to "no", the initiator
# does not send unsolicited data along with the iSCSI command PDU. When set to
# "yes" the initiator sends unsolicited data with the iSCSI command packet.
#
#ImmediateData=yes
#ImmediateData=no
#
# MaxRecvDataSegmentLength specifies the maximum number of bytes of data the
# initiator or target can receive in a iSCSI PDU. The value can be specified
# between the range 512-(2^24-1).
#
#MaxRecvDataSegmentLength=128 * 1024
#
# FirstBurstLength specifies the number of bytes of unsolicited data the
# initiator is allowed to send. The value can range between 512-( 2^24-1) bytes.
#
#FirstBurstLength=262144
#
# MaxBurstLength specifies the maximum SCSI payload that an initiator and
# target can negotiate for. The value can range between 512-(2^24-1) bytes. 
#
#MaxBurstLength=(16 * 1024 * 1024) - 1024
#
# TCPWindowSize specifies the maximum amount of data that can be sent or
# received on the TCP connection before receiving an acknowledgement.
# This parameter can also be specified for TargetName and Subnet Configutaion.
#
#TCPWindowSize=262144
#