Difference between revisions of "GSP Virtualisation with Xen"
From PDP/Grid Wiki
Jump to navigationJump to searchLine 207: | Line 207: | ||
== Connecting with iSCSI == | == Connecting with iSCSI == | ||
− | The [[NDPF_System_Locations#Network_Connection_in_the_NDPF|iSCSI network is ve16]], in range 172.21.0.0/16. The Compellent "Sint" is at 172.21.0.34, 35 en | + | The [[NDPF_System_Locations#Network_Connection_in_the_NDPF|iSCSI network is ve16]], in range 172.21.0.0/16. The Compellent "Sint" is at 172.21.0.34, 35 en the Fault Domain 0 (the one to use) is at 172.21.0.36. |
+ | |||
+ | To attached an iSCSI SR is far less stable than using FC, so if you have an FC path available, use that! Otherwise: | ||
+ | * create a volume on the Compellent | ||
+ | * create a server group on the Compellent if not already there | ||
+ | * on the XenServer host, click "Add new storage" -> "Software iSCSI" and name the SR | ||
+ | * as the target host, ping 172.21.0.36 (sint.iscsi.ipmi.nikhef.nl), port 3260 | ||
+ | * click "Discover IQNs" | ||
+ | * now, on the compellent, create a server and try to identify the proper iSCSI initiator. It may not be there yet, in which case you can retry on a per-XenServer basis. | ||
+ | * click "Discover LUNs". If there are no LUNs, go back to the Compellent and try again. If needed, click on Discover IQNs again and retry | ||
+ | If you never find the target, you can login on to the VM host and try | ||
+ | iscsiadm -m node -l | ||
+ | to log in, but only if the iSCSI initiator name has been set in <tt>/etc/iscsi/initiatorname.iscsi</tt>. Sometime XCP does not do that, and you just need to try again. | ||
See also: | See also: |