Note: this is a user-contributed document. While this howto contains some very useful information, it is not necessarily updated for new versions of xCAT and therefore may be inaccurate in some cases. Use it with this in mind. We welcome corrections and contributions - see Editing xCAT Documentation. And see the [XCAT_Documentation] page for documentation that is tested and updated with each xCAT release (to the best of our ability).
as usual with these howtos you should have at least a basic xCAT install done. We're going to take a diskless node and boot it into iSCSI. As a sanity check, make sure that you can do a diskful install and/or a diskless install on the node you're going to do iSCSI with. If this works then you should be able to boot iSCSI
yum -y install gpxe-xcat # on the management server
yum -y install scsi-target-utils-0.9.1-1 # on the tgt server (this has to be a service node or the xCAT management server)
service tgtd start
chkconfig tgtd on
If you need to create an iSCSI target on the machine you
You'll need to install scsi-target-utils on the machine that you wish to be the iSCSI target and gpxe-xcat on the management node.
chtab node=node01 nodetype.os=rhels5.3 nodetype.arch=x86_64 nodetype.profile=iscsi
You'll also need to set the iscsi table:
tabdump iscsi
#node,server,target,lun,iname,file,userid,passwd,kernel,kcmdline,initrd,comments,disable
"node01","redhouse",
Notice that the first two arguments: The node and the server are all you need. xCAT will populate the other fields automatically.
You'll also need to know where you're iscsi targets are going to live. We made a directory called iscsi to put ours in. Do this by modifying the site table. And finally, you'll need the password for your Windows machine:
chtab key=iscsidir site.value=/iscsi
If you are using a machine as an iSCSI target like we are then you'll need to create the iSCSI target:
setupscsidev node01 -s 10240 # 10GB of disk
if you now look at your iscsi table you'll see the new settings that xCAT configured for you.
Note that if the system hosting the iSCSI targets is rebooted, the "setupiscsidev" command (with no arguments) will have to be re-run to export the iSCSI targets again (be careful not to re-create/overwrite the iSCSI targets).
rinstall node01
nodeset node01 iscsiboot
tgtadm --mode target --op show
To remotely access the node from linux, use rdesktop version 1.60 or later