Chelsio Communications Terminator Series Installation And User Manual page 171

Chapter X. iSCSI PDU Offload Target
For mutual CHAP, in addition to the initiator CHAP id and secret, the target CHAP id and secret
are required. They are configured and stored on a per target basis with Chelsio Entity parameter
"Auth_CHAP_Target".
Adding CHAP User ID and Secret
A single Auth_CHAP_Target
per target:
target:
TargetName=iqn.2006-
02.com.chelsio.diskarray.san1
PortalGroup=1@192.0.2.178:8000
Auth_CHAP_Initiator="remoteuser1":"remoteuser1_secret"
_Initiator="remoteuser2":"remoteuser2_secret"
id1":"target1_secret"
In the above example, target
authenticate two initiators, and its own id and secret are configured for use in the case of mutual
CHAP.
AuthMethod and Auth_CHAP_Policy Keys
By setting the iSCSI keys
enforce CHAP and if mutual CHAP needs to be performed.
AuthMethod
The key controls if an initiator needs to be authenticated or not. The default setting
AuthMethod None,CHAP
of is
The Auth_CHAP_Policy
be performed if CHAP is used. The default setting of
On an iSCSI node, with
•
Auth_CHAP_Policy=Oneway
a) no CHAP
b) CHAP Oneway or
c) CHAP Mutual
•
Auth_CHAP_Policy=Mutual
a) no CHAP or
b) CHAP Mutual
With AuthMethod=None
target will only accept a relevant initiator if it does no CHAP.
With AuthMethod=CHAP
Chelsio Unified Wire for Linux
key and multiple
iqn.2005-com.chelsio.diskarray.san1
AuthMethod Auth_CHAP_Policy
and
key controls which CHAP authentication (one-way or mutual) needs to
AuthMethod=None,CHAP
, Chelsio iSCSI target will accept a relevant initiator if it does
, the Chelsio iSCSI target will accept a relevant initiator if it does
, regardless the setting of the key Auth_CHAP_Policy, the Chelsio iSCSI
, CHAP is enforced on the target:
Auth_CHAP_Initiator
TargetDevice=/dev/sda
Auth_CHAP_Policy=Oneway
Auth_CHAP_Target="target
, a user can choose whether to
Auth_CHAP_Policy
keys could be configured
Auth_CHAP
has been configured to
Oneway
is
171