McDATA Eclipse 2640 SAN, Administration And Configuration Manual

Page: 119 / 276

5
Configuring iSCSI Connections
5-11
Configuring iSCSI Ports
NOTE:
Digest and large PDU cannot both be enabled at the same
time.
•
Initial R2T
- (request to transfer). This skips the requirement
for an initial R2T in unidirectional and the output part of
bidirectional commands.
•
Store and Forward
- Enables the SAN Router to wait until all the
data is received from a drive before delivering it to the
initiator.
•
Target Read Padding
- Some earlier iSCSI initiators could not
handle true data underrun cases, where the target returns less
data than what the initiator requests. To accommodate those
initiators a target read padding option is provided in the SAN
Router. When enabled, the SAN Router (iSCSI target) will pad
the data, if needed, to meet the iSCSI initiator's expected data
length. The SCSI response indicates the actual data underrun
details.
•
Target Write Padding
- Some earlier iSCSI initiators did not pad
write data to 32-bit boundaries, as required by the iSCSI
specification. To accommodate these initiators, the target write
padding option is provided.
NOTE:
If target write padding is enabled on a port, all initiators that
login through that port must support it.
•
NOP packets
- This sends NOPs on idle connections to keep the
iSCSI session active. The default setting is
On
.
•
Immediate Data
- Data sent along with an iSCSI command. The
initiator and target negotiate support for immediate data. The
default setting is
On
.
•
Authentication method
- This determines whether or not this
intelligent port authenticates iSCSI initiators to determine
access permission to iSCSI targets. Choices are
None
,
CHAP
Preferred
(initiators are authenticated via CHAP, if the initiator
supports CHAP, but other logins that do not support
authentication are also accepted), and
CHAP Required
(initiators are always authenticated via CHAP).