{"id":65,"date":"2008-06-10T19:00:49","date_gmt":"2008-06-10T06:00:49","guid":{"rendered":"http:\/\/www.meta.net.nz\/~daniel\/blog\/?p=65"},"modified":"2008-06-10T19:05:02","modified_gmt":"2008-06-10T06:05:02","slug":"65","status":"publish","type":"post","link":"https:\/\/www.meta.net.nz\/~daniel\/blog\/2008\/06\/10\/65\/","title":{"rendered":"HP AiO iSCSI and Citrix Xenserver"},"content":{"rendered":"<p>A couple of our clients have <a href=\"http:\/\/h18006.www1.hp.com\/products\/storageworks\/aio1200\/index.html\">HP AiO1200<\/a> iSCSI systems. These are nice enough units, especially for entry level iSCSI SANs. They&#8217;re in a slightly modified HP DL320s chassis, and run Windows 2003 Storage Server, as well as some custom built HP management tools.<\/p>\n<p>I&#8217;ve never had an easy run when dealing with their iSCSI target and the open-scsi stack used by Citrix Xenserver. The first problem I had was that the management tools don&#8217;t support multiple initiators connecting to the same target LUN. They don&#8217;t actually stop you, but it seems that you need to hold your tongue <a href=\"http:\/\/activeanswers.compaq.com\/ERC\/downloads\/4AA1-5829ENW.pdf\">just right<\/a> to allow multiple initiators connecting to the one target. If you don&#8217;t hold it just right, the admin tools will let you do it, but it won&#8217;t actually work.[1]<\/p>\n<p>The second problem I had is that Xenserver just refuses to connect, saying &#8220;Your Target is probably misconfigured&#8221;. There&#8217;s not really a lot of configuration you can do with an iSCSI target, so I&#8217;m perplexed here. Digging deeper:<\/p>\n<p>[code]<\/p>\n<p>\n# iscsiadm  -m discovery -t st -p 1.2.3.4<br \/>\n1.2.3.4:3260,1 iqn.1991-05.com.microsoft:storage-iqn.xen-osdata-target<br \/>\n[\/code]\n<\/p>\n<p>It seems that iscsiadm can see everything fine!. I tried adding the target via the cli:<\/p>\n<p>[code]<br \/>\n# xe sr-create host-uuid=f3b260ab-f8b9-4b52-980d-7b7e93ab8dcf content-type=user name-label=AIO_OSDATA shared=true type=lvmoiscsi device-config-targetIQN=iqn.1991-05.com.microsoft:storage-iqn.xen-osdata-target device-config-target=1.2.3.4<\/p>\n<p>Error code: SR_BACKEND_FAILURE_107<br \/>\nError parameters: , The SCSIid parameter is missing or incorrect, \\<br \/>\n< ?xml version=\"1.0\" ?><br \/>\niscsi-target<br \/>\n    LUN<br \/>\n        vendor<br \/>\n\t    HP<br \/>\n        \/vendor<br \/>\n        LUNid<br \/>\n            0<br \/>\n        \/LUNid<br \/>\n        size<br \/>\n            42949672960<br \/>\n        \/size<br \/>\n        SCSIid<br \/>\n            360003ff646c289389ea2e31c1d419930<br \/>\n       \/SCSIid<br \/>\n    \/LUN<br \/>\n\/iscsi-target<br \/>\n[\/code]<\/p>\n<p>Unlike the error messages you get in the GUI, that one is quite helpful[2] It tells us we&#8217;re missing a SCSIid parameter, and then lists a SCSIid parameter to try:<\/p>\n<p>[code]<br \/>\nxe sr-create host-uuid=f3b260ab-f8b9-4b52-980d-7b7e93ab8dcf content-type=user name-label=AIO_OSDATA shared=true type=lvmoiscsi device-config-targetIQN=iqn.1991-05.com.microsoft:storage-iqn.xen-osdata-target device-config-target=1.2.3.4  device-config-LUNid=1 device-config-SCSIid=360003ff646c289389ea2e31c1d419930<br \/>\n[\/code]<\/p>\n<p>And our iSCSI target was happily added. I&#8217;m not entirely sure the LUNid parameter is required, <a href=\"http:\/\/forums.xensource.com\/thread.jspa?messageID=14001\">this post<\/a> suggests it isn&#8217;t. I found a couple of other posts on the forums which suggest that using the CLI for these tasks should be your first attempt.<\/p>\n<p>[1] Where &#8220;work&#8221; means &#8220;actually let you connect more than one initiator at a time&#8221;<br \/>\n[2] Although, being full of less than and greater than signs, doesn&#8217;t want to display nicely in wordpress. So it&#8217;s a bit sanitised<\/p>\n","protected":false},"excerpt":{"rendered":"<p>A couple of our clients have HP AiO1200 iSCSI systems. These are nice enough units, especially for entry level iSCSI SANs. They&#8217;re in a slightly modified HP DL320s chassis, and run Windows 2003 Storage Server, as well as some custom built HP management tools. I&#8217;ve never had an easy run when dealing with their iSCSI [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[12,8,10],"tags":[],"_links":{"self":[{"href":"https:\/\/www.meta.net.nz\/~daniel\/blog\/wp-json\/wp\/v2\/posts\/65"}],"collection":[{"href":"https:\/\/www.meta.net.nz\/~daniel\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.meta.net.nz\/~daniel\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.meta.net.nz\/~daniel\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.meta.net.nz\/~daniel\/blog\/wp-json\/wp\/v2\/comments?post=65"}],"version-history":[{"count":0,"href":"https:\/\/www.meta.net.nz\/~daniel\/blog\/wp-json\/wp\/v2\/posts\/65\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.meta.net.nz\/~daniel\/blog\/wp-json\/wp\/v2\/media?parent=65"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.meta.net.nz\/~daniel\/blog\/wp-json\/wp\/v2\/categories?post=65"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.meta.net.nz\/~daniel\/blog\/wp-json\/wp\/v2\/tags?post=65"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}