<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: SAN / EMC: CX4 DAE (Drive Shelf) Information</title>
	<atom:link href="http://blog.colovirt.com/2009/05/29/san-emc-cx4-dae-drive-shelf-information/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.colovirt.com/2009/05/29/san-emc-cx4-dae-drive-shelf-information/</link>
	<description>and linux between</description>
	<lastBuildDate>Wed, 07 Dec 2011 20:31:07 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: SAN / EMC: Clariion CX4 Solid State DAEs (Shelves) &#171; Colocation to Virtualization</title>
		<link>http://blog.colovirt.com/2009/05/29/san-emc-cx4-dae-drive-shelf-information/#comment-177</link>
		<dc:creator><![CDATA[SAN / EMC: Clariion CX4 Solid State DAEs (Shelves) &#171; Colocation to Virtualization]]></dc:creator>
		<pubDate>Wed, 03 Jun 2009 08:01:28 +0000</pubDate>
		<guid isPermaLink="false">http://blog.colovirt.com/?p=554#comment-177</guid>
		<description><![CDATA[[...] CX4 DAE (general) information http://blog.colovirt.com/2009/05/29/san-emc-cx4-dae-drive-shelf-information/ [...]]]></description>
		<content:encoded><![CDATA[<p>[...] CX4 DAE (general) information <a href="http://blog.colovirt.com/2009/05/29/san-emc-cx4-dae-drive-shelf-information/" rel="nofollow">http://blog.colovirt.com/2009/05/29/san-emc-cx4-dae-drive-shelf-information/</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Storrs</title>
		<link>http://blog.colovirt.com/2009/05/29/san-emc-cx4-dae-drive-shelf-information/#comment-172</link>
		<dc:creator><![CDATA[Andrew Storrs]]></dc:creator>
		<pubDate>Sat, 30 May 2009 17:59:54 +0000</pubDate>
		<guid isPermaLink="false">http://blog.colovirt.com/?p=554#comment-172</guid>
		<description><![CDATA[&quot;The highest IO luns were vertically striped between 2 DAEs&quot; Did you create RAID groups and LUNs that spanned DAEs or did you use MetaLUNs?]]></description>
		<content:encoded><![CDATA[<p>&#8220;The highest IO luns were vertically striped between 2 DAEs&#8221; Did you create RAID groups and LUNs that spanned DAEs or did you use MetaLUNs?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: kcollo</title>
		<link>http://blog.colovirt.com/2009/05/29/san-emc-cx4-dae-drive-shelf-information/#comment-171</link>
		<dc:creator><![CDATA[kcollo]]></dc:creator>
		<pubDate>Sat, 30 May 2009 13:50:34 +0000</pubDate>
		<guid isPermaLink="false">http://blog.colovirt.com/?p=554#comment-171</guid>
		<description><![CDATA[It is a CX4-240.  performance is not an issue currently setup with 100 - 400g 10krpm  and 15-  300g 15krpm disks.  All raid groups setup with raid 10. The highest IO luns were vertically striped between 2 DAEs.  One at the end of the first bus and other at the start of the next.  I just wanted to make sure the logic was correct concerning the LCC links.]]></description>
		<content:encoded><![CDATA[<p>It is a CX4-240.  performance is not an issue currently setup with 100 &#8211; 400g 10krpm  and 15-  300g 15krpm disks.  All raid groups setup with raid 10. The highest IO luns were vertically striped between 2 DAEs.  One at the end of the first bus and other at the start of the next.  I just wanted to make sure the logic was correct concerning the LCC links.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Storrs</title>
		<link>http://blog.colovirt.com/2009/05/29/san-emc-cx4-dae-drive-shelf-information/#comment-169</link>
		<dc:creator><![CDATA[Andrew Storrs]]></dc:creator>
		<pubDate>Sat, 30 May 2009 03:49:17 +0000</pubDate>
		<guid isPermaLink="false">http://blog.colovirt.com/?p=554#comment-169</guid>
		<description><![CDATA[Yes you have the right idea. The CLARiiON CX4 series has 4 Gb/s throughput end-to-end. What model CX4 are you working with? Also what is the configuration (# of DAE&#039;s, types of disks, etc). And finally what are you trying to do that needs more bandwidth, we can probably help you come up with an alternative disk/LUN layout that gets what you need. 

Also don&#039;t forget unless you have the new 8 Gb FC or 10 Gb iSCSI (are those even out yet?) UltraFlex I/O modules you are going to be limited to 4 Gb ports anyway (yes I realize you could have anywhere between 2 and 12 per storage processor depending on the array type and how you&#039;ve populated things) - but don&#039;t forget ALL the traffic on the array is flowing through those.

Give me a better idea of what you have and what you want and I&#039;m sure we can figure something out. :)]]></description>
		<content:encoded><![CDATA[<p>Yes you have the right idea. The CLARiiON CX4 series has 4 Gb/s throughput end-to-end. What model CX4 are you working with? Also what is the configuration (# of DAE&#8217;s, types of disks, etc). And finally what are you trying to do that needs more bandwidth, we can probably help you come up with an alternative disk/LUN layout that gets what you need. </p>
<p>Also don&#8217;t forget unless you have the new 8 Gb FC or 10 Gb iSCSI (are those even out yet?) UltraFlex I/O modules you are going to be limited to 4 Gb ports anyway (yes I realize you could have anywhere between 2 and 12 per storage processor depending on the array type and how you&#8217;ve populated things) &#8211; but don&#8217;t forget ALL the traffic on the array is flowing through those.</p>
<p>Give me a better idea of what you have and what you want and I&#8217;m sure we can figure something out. :)</p>
]]></content:encoded>
	</item>
</channel>
</rss>

