This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-API] multipath on 'dual-head' configuration

To: George Shuklin <george.shuklin@xxxxxxxxx>
Subject: Re: [Xen-API] multipath on 'dual-head' configuration
From: Julian Chesterfield <julian.chesterfield@xxxxxxxxxxxxx>
Date: Mon, 16 May 2011 17:15:07 +0100
Cc: "xen-api@xxxxxxxxxxxxxxxxxxx" <xen-api@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 16 May 2011 09:13:40 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1305561939.18562.15.camel@mabase>
List-help: <mailto:xen-api-request@lists.xensource.com?subject=help>
List-id: Discussion of API issues surrounding Xen <xen-api.lists.xensource.com>
List-post: <mailto:xen-api@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=unsubscribe>
References: <1305561939.18562.15.camel@mabase>
Sender: xen-api-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv: Gecko/20100527 Thunderbird/3.0.5
Hi George,

You can specify a comma separated list for the iSCSI target in XCP. If both targets advertise the same IQN then you can specify that IQN explicitly as the targetIQN parameter. Alternatively you can select the wildcard entry '*' which will connect to all advertised sessions on every IP address specified in the comma separated list.


On 16/05/11 17:05, George Shuklin wrote:
Good day.

Found I unable to setup multipath (XCP 0.5) with two separate hosts
connecting to same storage device.

Every iscsi target has been sent only it own ip-addresses for target.

> From generic linux machine it looks like:,1 iqn.2011-04.test:test.test,1 iqn.2011-04.test:test.test

Those IP actually belongs to different machines but allow to access the
same block device.

In usual linux I simply add iscsi login process to startup, multipath
script and it joins paths just by identical serial number and IQN.

In XCP I found I need to serve single portal address with all available
paths (IPs) to target.

Using ISNS is not very good (i do need to build a HA-cluster for that,
and it seems be little overkill).

That's kinda stuck for me.

Here questions:

Can I somehow say XCP 'do discovery targets (paths) from two portals for
single SR?

If I add multipathed device 'by hand' (f.e. by adding iscsi and
multipath processing to startup scripts), can I add it to XCP as
'shared' resource (regardless it seems be 'local' for xapi)?


xen-api mailing list

xen-api mailing list

<Prev in Thread] Current Thread [Next in Thread>