Chelsio Communications Terminator 6, Инструкция по установке и эксплуатации, Страница: 163 / 432

Chapter X. iSCSI PDU Offload Target
Chelsio Unified Wire for Linux 163
DataPDUInOrder “Yes”
“No”
“Yes”
No To indicate the data PDUs with
sequence must be at continuously
increasing order or can be in any
order.
Chelsio only supports “Yes”.
DataSequenceInOrder “Yes”
“No”
“Yes”
No To indicate the Data PDU sequences
must be transferred in continuously
non-decreasing sequence offsets or
can be transferred in any order.
Chelsio only supports “Yes”.
ErrorRecoveryLevel
0 to 2 0 No To negotiate the recovery level
supported by the node.
Chelsio only supports 0.
HeaderDigest “None”
“CRC32C”
“None”
Yes To enable or disable iSCSI header
Cyclic integrity checksums.
DataDigest “None”
“CRC32C”
“None”
Yes To enable or disable iSCSI data Cyclic
integrity checksums.
AuthMethod “CHAP”
and
“None”
“None,
CHAP”
Yes To choose an authentication method
during login phase.
TargetName “<target
name>”
No A worldwide unique iSCSI target
name.
Target only.
TargetAlias “<target
alias>”
No A human-readable name or
description of a target. It is not used as
an identifier, nor is it for authentication.
Target only.
MaxRecvDataSegmentLengt
h
512 to
16777215
(2
24
- 1)
8192 No To declare the maximum data
segment length in bytes it can receive
in an iSCSI PDU.
OFMarker “Yes”
“No”
“No”
No To turn on or off the initiator to target
markers on the connection.
Chelsio only
supports “No”.
IFMarker “Yes”
“No”
“No”
No To turn on or off the target to initiator
markers on the connection.
Chelsio only supports “No”.
OFMarkInt
1 to 65535 2048 No To set the interval for the initiator to
target markers on a connection.
IFMarkInt
1 to 65535 2048 No To set the interval for the target to
initiator markers on a connection.
Chelsio Entity Settings
Description
Chelsio entity parameters pass control information to the Chelsio iSCSI module. The parameters
are specific to Chelsio’s implementation of the iSCSI node (target or initiator) and are unique for
each entity block. The parameters consist of information that can be put into three categories:
1. Challenge Handshake Authentication Protocol (CHAP).
2. Target specific settings. All of the following parameters can have multiple instances in one
target entity block (i.e., they can be declared multiple times for one particular target):
•
Portal Group
•
Storage Device