WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] moving LV's devices to a SAN server.

To: Javier Guerra <javier@xxxxxxxxxxx>
Subject: Re: [Xen-users] moving LV's devices to a SAN server.
From: Israel Garcia <igalvarez@xxxxxxxxx>
Date: Mon, 2 Nov 2009 16:31:58 -0500
Cc: "Fajar A. Nugraha" <fajar@xxxxxxxxx>, Xen Users <Xen-users@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 02 Nov 2009 13:32:48 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=6cvKnMT/qzrhFs8IjW9mO6Q1RGCXcuGj/7SPOuk1T8I=; b=JDLGZQvi2E9HVXRV1Adoiscc1cJnNofIJIOm3SPTEeMtr8ZNNc6P2Fs8dAmU8tegVR yuwP5rhjBA2zZgPZymtLURilbwbg8Vran9BYRU1UN8TQpPHJ6/wFbGschvV4Fre3zZgH VdfPgBdxGCaxpk793Gx5cO6u41lHHllpzogfw=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=mtBTc02FIezuBDhNGuvcJqzwBMltg3DHkC5P+HB6JGcp1vyvQOjy3wo7VfT4MX2SuW 4GoFNWu5Iu82utEDFtVQl2oBJKJtc3R6LY+TFAhLGSZLZemek3gBDb+/IN9q1FbpQT95 0VLKU4g3r7a7Qt7NhFB7Oxaz614eFEmtqjX6Y=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <90eb1dc70911021157s2a3e9a18hb251cb1e560fde02@xxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <194a2c240910301000r499fabcatccb9e6e0f9349119@xxxxxxxxxxxxxx> <7207d96f0911012156na616f7ev5757da1f0a5969a6@xxxxxxxxxxxxxx> <194a2c240911020530u3b12a3cbv685dfc47d4da0773@xxxxxxxxxxxxxx> <90eb1dc70911020617r5c6733f0i5802d664d1a136f1@xxxxxxxxxxxxxx> <194a2c240911020839s2dc86baao973053f37a251945@xxxxxxxxxxxxxx> <90eb1dc70911021157s2a3e9a18hb251cb1e560fde02@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
On 11/2/09, Javier Guerra <javier@xxxxxxxxxxx> wrote:
> On Mon, Nov 2, 2009 at 11:39 AM, Israel Garcia <igalvarez@xxxxxxxxx> wrote:
>> Can you help me?
>
> not much, unfortunately.  even if there are some standards, compliance
> is spotty at best, so you'll have to test if your devices collaborate.
>
Hi Javier,

Very interesting your comment about link aggregation. thanks  :-)
I think this setup (using link aggregation in both sides) is the best
way to achieve higher (1GBE) bandwidth over a ethernet network serving
SAN boxes. I've searched the web a lot and I haven't found other best
setup. I'm going to test all LACP/bonding and  If it's possible I'll
send the list some  results.

thanks again.

regards,
Israel.

> in any case, this was my reasoning for mentioning port aggregation (or
> more precise, Link aggregation):
>
> - the 'usual' topology for all things ethernet (including iSCSI), is
> to simply put the switches at the middle and pull one cable to each
> host.
>
> - in a SAN, this creates a bottleneck since it's common to have just
> one or two storage boxes for several hosts (specially when just
> starting!).  The single Ethernet port going to the storage box limits
> the total access bandwidth to just 1Gb for all hosts.
>
> - most iSCSI devices currently include several (4-6) GbE ports.
>
> - the naïve way to use all these ports would be to ditch the Ethernet
> switch, and just connect one host on each port.  This gives you 1Gb
> dedicated for each host, and the total data bandwidth is limited to
> the platter and internal backbone speeds.
>
> - unfortunately, this strategy is too limiting for later growth.  Not
> only you have a limited number of ports, but it also makes nearly
> impossible to add a second storage box.
>
> - so, what you can do is to keep the central switch, plug each host on
> a single port of the switch; but for the storage box, use several
> ports connected to several ports in the switch.  if the link
> aggregation features of both the storage box and the switch match, now
> you have a single very fat link between the box and the switch.  From
> the point of view of the hosts, it's exactly the same as the 'usual'
> topology (one device on each switch port); but a single host won't be
> able to saturate the storage bandwith.
>
> - expandability also isn't impaired, you can add extra hosts without
> any change, and also extra storage just by creating extra link
> aggregation groups.
>
> hope it helps, at least in clarifying the general concepts.  for
> details you'll have to consult the docs of both your storage box and
> switches, and experiment a lot!
>
> --
> Javier
>


-- 
Regards;
Israel Garcia

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

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