IC SunsetThe developerWorks Connections platform will be sunset on December 31, 2019. On January 1, 2020, this blog will no longer be available. More details available on our FAQ.

Comments (4)
  • Add a Comment
  • Edit
  • More Actions v
  • Quarantine this Entry

Comments (4)

Jeff Schoby commented Feb 18 2014 Comment Permalink

Is there a way to pass the UDID of the backing device through the iscsi target lun so the iscsi client can see it?

zarnickmp commented Nov 12 2013 Comment Permalink

Chris, Helpful article. Do you know how changes to the autosecrets file are handled? Seems that an iSCSI Software Target doesn't pick up changes in this file. We tried to change a known chap secret for a target, or even comment it out (no chap secret), but the software target seems to stick with the previously known chap secret. Not sure what to refresh to get the software target to reread the autosecrets file. Thanks, Mike.

Rob_BCRS commented Sep 21 2013 Comment Permalink

Great Article, do you know of a way to setup AIX as a FC target ? i.e. have the AIX server serve local disk/tape or other devices over FC without using iscsi. Is this even a valid question ? thanks for you attention. Robert

grukrz1 commented Oct 16 2012 Comment Permalink

hello, lsdev -C -c tmiscsi -s tmtarget -t target | sort | uniq returns a few "iSCSI Target Mode Target" devices (iscsi software targets). there are several test LUNs served on those targets. when I go to: smitty tmlun -> Change / Show Characteristics of an iSCSI Target Logical Unit and delect a unit, I can see field "iSCSI Parent Target Name" with the name of configured iscsi target. is there any way to get the target device name for a logical unit using lsattr? alas, lsattr -El "iscsi_lun_dev" doesn't show this information...