/iscsi/iscsid.conf

  1#
  2# Open-iSCSI default configuration.
  3# Could be located at /etc/iscsi/iscsid.conf or ~/.iscsid.conf
  4#
  5# Note: To set any of these values for a specific node/session run
  6# the iscsiadm --mode node --op command for the value. See the README
  7# and man page for iscsiadm for details on the --op command.
  8#
  9
 10################
 11# iSNS settings
 12################
 13# Address of iSNS server
 14#isns.address = 192.168.0.1
 15#isns.port = 3205
 16
 17#############################
 18# NIC/HBA and driver settings
 19#############################
 20# open-iscsi can create a session and bind it to a NIC/HBA.
 21# To set this up see the example iface config file.
 22
 23#*****************
 24# Startup settings
 25#*****************
 26
 27# To request that the iscsi initd scripts startup a session set to "automatic".
 28# node.startup = automatic
 29#
 30# To manually startup the session set to "manual". The default is manual.
 31node.startup = manual
 32
 33# *************
 34# CHAP Settings
 35# *************
 36
 37# To enable CHAP authentication set node.session.auth.authmethod
 38# to CHAP. The default is None.
 39#node.session.auth.authmethod = CHAP
 40
 41# To set a CHAP username and password for initiator
 42# authentication by the target(s), uncomment the following lines:
 43#node.session.auth.username = username
 44#node.session.auth.password = password
 45
 46# To set a CHAP username and password for target(s)
 47# authentication by the initiator, uncomment the following lines:
 48#node.session.auth.username_in = username_in
 49#node.session.auth.password_in = password_in
 50
 51# To enable CHAP authentication for a discovery session to the target
 52# set discovery.sendtargets.auth.authmethod to CHAP. The default is None.
 53#discovery.sendtargets.auth.authmethod = CHAP
 54
 55# To set a discovery session CHAP username and password for the initiator
 56# authentication by the target(s), uncomment the following lines:
 57#discovery.sendtargets.auth.username = username
 58#discovery.sendtargets.auth.password = password
 59
 60# To set a discovery session CHAP username and password for target(s)
 61# authentication by the initiator, uncomment the following lines:
 62#discovery.sendtargets.auth.username_in = username_in
 63#discovery.sendtargets.auth.password_in = password_in
 64
 65# ********
 66# Timeouts
 67# ********
 68#
 69# See the iSCSI REAME's Advanced Configuration section for tips
 70# on setting timeouts when using multipath or doing root over iSCSI.
 71#
 72# To specify the length of time to wait for session re-establishment
 73# before failing SCSI commands back to the application when running
 74# the Linux SCSI Layer error handler, edit the line.
 75# The value is in seconds and the default is 120 seconds.
 76node.session.timeo.replacement_timeout = 120
 77
 78# To specify the time to wait for login to complete, edit the line.
 79# The value is in seconds and the default is 15 seconds.
 80node.conn[0].timeo.login_timeout = 15
 81
 82# To specify the time to wait for logout to complete, edit the line.
 83# The value is in seconds and the default is 15 seconds.
 84node.conn[0].timeo.logout_timeout = 15
 85
 86# Time interval to wait for on connection before sending a ping.
 87node.conn[0].timeo.noop_out_interval = 5
 88
 89# To specify the time to wait for a Nop-out response before failing
 90# the connection, edit this line. Failing the connection will
 91# cause IO to be failed back to the SCSI layer. If using dm-multipath
 92# this will cause the IO to be failed to the multipath layer.
 93node.conn[0].timeo.noop_out_timeout = 5
 94
 95# To specify the time to wait for abort response before
 96# failing the operation and trying a logical unit reset edit the line.
 97# The value is in seconds and the default is 15 seconds.
 98node.session.err_timeo.abort_timeout = 15
 99
100# To specify the time to wait for a logical unit response
101# before failing the operation and trying session re-establishment
102# edit the line.
103# The value is in seconds and the default is 30 seconds.
104node.session.err_timeo.lu_reset_timeout = 20
105
106#******
107# Retry
108#******
109
110# To specify the number of times iscsid should retry a login
111# if the login attempt fails due to the node.conn[0].timeo.login_timeout
112# expiring modify the following line. Note that if the login fails
113# quickly (before node.conn[0].timeo.login_timeout fires) because the network
114# layer or the target returns an error, iscsid may retry the login more than
115# node.session.initial_login_retry_max times.
116#
117# This retry count along with node.conn[0].timeo.login_timeout
118# determines the maximum amount of time iscsid will try to
119# establish the initial login. node.session.initial_login_retry_max is
120# multiplied by the node.conn[0].timeo.login_timeout to determine the
121# maximum amount.
122#
123# The default node.session.initial_login_retry_max is 8 and
124# node.conn[0].timeo.login_timeout is 15 so we have:
125#
126# node.conn[0].timeo.login_timeout * node.session.initial_login_retry_max =
127#								120 seconds
128#
129# Valid values are any integer value. This only
130# affects the initial login. Setting it to a high value can slow
131# down the iscsi service startup. Setting it to a low value can
132# cause a session to not get logged into, if there are distuptions
133# during startup or if the network is not ready at that time.
134node.session.initial_login_retry_max = 8
135
136################################
137# session and device queue depth
138################################
139
140# To control how many commands the session will queue set
141# node.session.cmds_max to an integer between 2 and 2048 that is also
142# a power of 2. The default is 128.
143node.session.cmds_max = 128
144
145# To control the device's queue depth set node.session.queue_depth
146# to a value between 1 and 1024. The default is 32.
147node.session.queue_depth = 32
148
149##################################
150# MISC SYSTEM PERFORMANCE SETTINGS
151##################################
152
153# For software iscsi (iscsi_tcp) and iser (ib_iser) each session
154# has a thread used to transmit or queue data to the hardware. For
155# cxgb3i you will get a thread per host.
156#
157# Setting the thread's priority to a lower value can lead to higher throughput
158# and lower latencies. The lowest value is -20. Setting the priority to
159# a higher value, can lead to reduced IO performance, but if you are seeing
160# the iscsi or scsi threads dominate the use of the CPU then you may want
161# to set this value higher.
162#
163# Note: For cxgb3i you must set all sessions to the same value, or the
164# behavior is not defined.
165#
166# The default value is -20. The setting must be between -20 and 20.
167node.session.xmit_thread_priority = -20
168
169
170#***************
171# iSCSI settings
172#***************
173
174# To enable R2T flow control (i.e., the initiator must wait for an R2T
175# command before sending any data), uncomment the following line:
176#
177#node.session.iscsi.InitialR2T = Yes
178#
179# To disable R2T flow control (i.e., the initiator has an implied
180# initial R2T of "FirstBurstLength" at offset 0), uncomment the following line:
181#
182# The defaults is No.
183node.session.iscsi.InitialR2T = No
184
185#
186# To disable immediate data (i.e., the initiator does not send
187# unsolicited data with the iSCSI command PDU), uncomment the following line:
188#
189#node.session.iscsi.ImmediateData = No
190#
191# To enable immediate data (i.e., the initiator sends unsolicited data
192# with the iSCSI command packet), uncomment the following line:
193#
194# The default is Yes
195node.session.iscsi.ImmediateData = Yes
196
197# To specify the maximum number of unsolicited data bytes the initiator
198# can send in an iSCSI PDU to a target, edit the following line.
199#
200# The value is the number of bytes in the range of 512 to (2^24-1) and
201# the default is 262144
202node.session.iscsi.FirstBurstLength = 262144
203
204# To specify the maximum SCSI payload that the initiator will negotiate
205# with the target for, edit the following line.
206#
207# The value is the number of bytes in the range of 512 to (2^24-1) and
208# the defauls it 16776192
209node.session.iscsi.MaxBurstLength = 16776192
210
211# To specify the maximum number of data bytes the initiator can receive
212# in an iSCSI PDU from a target, edit the following line.
213#
214# The value is the number of bytes in the range of 512 to (2^24-1) and
215# the default is 262144
216node.conn[0].iscsi.MaxRecvDataSegmentLength = 262144
217
218# To specify the maximum number of data bytes the initiator can receive
219# in an iSCSI PDU from a target during a discovery session, edit the
220# following line.
221#
222# The value is the number of bytes in the range of 512 to (2^24-1) and
223# the default is 32768
224# 
225discovery.sendtargets.iscsi.MaxRecvDataSegmentLength = 32768
226
227# To allow the targets to control the setting of the digest checking,
228# with the initiator requesting a preference of enabling the checking, uncomment# one or both of the following lines:
229#node.conn[0].iscsi.HeaderDigest = CRC32C,None
230#node.conn[0].iscsi.DataDigest = CRC32C,None
231#
232# To allow the targets to control the setting of the digest checking,
233# with the initiator requesting a preference of disabling the checking,
234# uncomment one or both of the following lines:
235#node.conn[0].iscsi.HeaderDigest = None,CRC32C
236#node.conn[0].iscsi.DataDigest = None,CRC32C
237#
238# To enable CRC32C digest checking for the header and/or data part of
239# iSCSI PDUs, uncomment one or both of the following lines:
240#node.conn[0].iscsi.HeaderDigest = CRC32C
241#node.conn[0].iscsi.DataDigest = CRC32C
242#
243# To disable digest checking for the header and/or data part of
244# iSCSI PDUs, uncomment one or both of the following lines:
245#node.conn[0].iscsi.HeaderDigest = None
246#node.conn[0].iscsi.DataDigest = None
247#
248# The default is to never use DataDigests or HeaderDigests.
249#
250
251
252#************
253# Workarounds
254#************
255
256# Some targets like IET prefer after an initiator has sent a task
257# management function like an ABORT TASK or LOGICAL UNIT RESET, that
258# it does not respond to PDUs like R2Ts. To enable this behavior uncomment
259# the following line (The default behavior is Yes):
260node.session.iscsi.FastAbort = Yes
261
262# Some targets like Equalogic prefer that after an initiator has sent
263# a task management function like an ABORT TASK or LOGICAL UNIT RESET, that
264# it continue to respond to R2Ts. To enable this uncomment this line
265# node.session.iscsi.FastAbort = No