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

Chapter X. iSCSI PDU Offload Target
Chelsio Unified Wire for Linux 171
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
key and multiple
Auth_CHAP_Initiator
keys could be configured
per target:
target:
TargetName=iqn.2006-
02.com.chelsio.diskarray.san1 TargetDevice=/dev/sda
PortalGroup=1@192.0.2.178:8000 Auth_CHAP_Policy=Oneway
Auth_CHAP_Initiator=”remoteuser1”:”remoteuser1_secret” Auth_CHAP
_Initiator=” r emoteuser2”:”remoteuser2_secret” Auth_CHAP_Target=“target
id1”:”target1_secret”
In the above example, target
iqn.2005-com.chelsio.diskarray.san1
has been configured to
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 AuthMethod and Auth_CHAP_Policy , a user can choose whether to
enforce CHAP and if mutual CHAP needs to be performed.
The
AuthMethod
key controls if an initiator needs to be authenticated or not. The default setting
of
AuthMethod
is
None,CHAP
The
Auth_CHAP_Policy
key controls which CHAP authentication (one-way or mutual) needs to
be performed if CHAP is used. The default setting of Auth_CHAP_Policy is Oneway
On an iSCSI node, with AuthMethod=None,CHAP
•
Auth_CHAP_Policy=Oneway , Chelsio iSCSI target will accept a relevant initiator if it does
a) no CHAP
b) CHAP Oneway or
c) CHAP Mutual
•
Auth_CHAP_Policy=Mutual , the Chelsio iSCSI target will accept a relevant initiator if it does
a) no CHAP or
b) CHAP Mutual
With
AuthMethod=None
, regardless the setting of the key Auth_CHAP_Policy, the Chelsio iSCSI
target will only accept a relevant initiator if it does no CHAP.
With
AuthMethod=CHAP
, CHAP is enforced on the target: