Defining Chap Entries For Iscsi Device Authentication; Finalizing The Iscsi Configuration - HP A7990A - StorageWorks SAN Director 4/16 Blade Switch Hardware Reference Manual

Hp storageworks dc san backbone director hardware reference guide (5697-7346, september 2008)
Table of Contents

Advertisement

:
switch:admin> iscsicfg –-enable ddset –n myddset
Operation Succeeded

Defining CHAP entries for iSCSI device authentication

The modify command can be used only for changing the authentication method for a target from None to
CHAP or CHAP to None. If nothing is specified, no authentication method is enforced. If CHAP is
specified, then either one-way or mutual CHAP enforcement will be performed based on the login frame
from host.
iscsicfg < --create | --show | --modify | --delete | --clear > auth [-u
username] [–s CHAP_Secret] args
To modify the authentication method for a target, use the iscsicfg --modify command as follows:
:
switch:admin> iscsicfg --modify tgt –t iqn.2002-10.com.company.tgt1 –a CHAP -f
Operation Succeeded
To create CHAP users, use the iscsicfg --create command as follows:
:
switch:admin> iscsicfg –-create auth -u username -s CHAP_Secret
Operation Succeeded

Finalizing the iSCSI configuration

Use commit with the iscsiCfg command to commit the iSCSI changes to persistent memory. This option
triggers propagation of the database to all iSCSI-capable switches in the fabric and blade and commits the
changes to persistent memory.
NOTE:
Make all necessary changes to the database—virtual target creation, LUN additions, discovery
domain creation, discovery domain set creation, and so on—before using the command iscsicfg
--commit all.
iscsicfg < --commit > all
To commit the configurations that have been created and modified, use the iscsiCfg command as
follows:
:
switch:admin> iscsicfg --commit all
This will commit ALL database changes made to all iSCSI switches in fabric.
This could be a long-running operation. Continue [N]:
...
The operation completed successfully
The iscsicfg –commit all command commits local configuration changes and also pushes iSCSI
configuration from a local switch to remote switches in the fabric. However, during the commit process,
other configuration changes not yet commited on remote switches need to be aborted. When configuration
changes have been made on switches in the fabric and not yet commited, the iscsicfg –commit all
command is rejected. You need to manually abort the configuration changes on other switches in the fabric
before trying again to run the command.
To avoid this situation, use the –f option. When you do so, the iscsicfg –commit all command runs
and configuration changes not yet commited on remote switches in the fabric are aborted.
120 Intelligent blades

Advertisement

Table of Contents
loading

Table of Contents